6,566
edits
FGAddon: Difference between revisions
Jump to navigation
Jump to search
m
→Commit access: Spelling fix.
(→Commit access: Rewrote and removed the patch submission instructions to be deliberately more vague, and to account for the different development scenarios.) |
m (→Commit access: Spelling fix.) |
||
| Line 127: | Line 127: | ||
These easy to jump over hurdles are simply designed to protect against repository corruption or pollution of the repository with illegal content. | These easy to jump over hurdles are simply designed to protect against repository corruption or pollution of the repository with illegal content. | ||
To have your changes committed into the FGAddon repository, you should discuss and coordinate with the original aircraft author, or your mentor, for the best way to | To have your changes committed into the FGAddon repository, you should discuss and coordinate with the original aircraft author, or your mentor, for the best way to proceed. Depending on the [[#Development_scenarios|development scenario]], this maybe by merge request, file transfer, the primitive patch system, or any other convenient way. Once you believe you have proven your capabilities and you are knowledgeable about GPL licensing issues, you should write a mail to the development mailing list asking if you can be granted commit access, providing your SourceForge username. | ||
=== FGAddon commitlog mailing list === | === FGAddon commitlog mailing list === | ||