6,566
edits
FGAddon: Difference between revisions
m
→Commit Access
(Shifted the 'Commit access' section under the development section and added some text.) |
m (→Commit Access) |
||
| Line 203: | Line 203: | ||
Before obtaining commit access, you should contact the original authors to determine if the aircraft is actively being developed. If so, the aircraft author will direct you as to how to proceed with development. Otherwise you will need to obtain FGAddon commit access to make the changes. | Before obtaining commit access, you should contact the original authors to determine if the aircraft is actively being developed. If so, the aircraft author will direct you as to how to proceed with development. Otherwise you will need to obtain FGAddon commit access to make the changes. | ||
To obtain commit access, you should first demonstrate | To obtain commit access, you should first demonstrate your capabilities. You should sign up for the [https://lists.sourceforge.net/lists/listinfo/flightgear-devel FlightGear development mailing list] and ask for help there. You should first provide your changes as patches. If these are not too large, they can be sent as attachments to the mailing list. For large patches, a [https://sourceforge.net/p/flightgear/codetickets/ code ticket] can be created and the patch attached there, or the patch uploaded to a public server and a link sent in a development mailing list message. | ||
If you are using a subversion command line client, you can create a patch by typing: | If you are using a subversion command line client, you can create a patch by typing: | ||