FGAddon: Difference between revisions

Jump to navigation Jump to search

FGAddon (view source)

Revision as of 17:31, 1 May 2016

668 bytes removed ,  1 May 2016
→‎Commit access: Rewrote and removed the patch submission instructions to be deliberately more vague, and to account for the different development scenarios.
(→‎Commit access: Rewrote and removed the patch submission instructions to be deliberately more vague, and to account for the different development scenarios.)
Line 125: Line 125:
# To earn the trust of the FlightGear community.
# To earn the trust of the FlightGear community.


These easy to jump over hurdles are simply designed to protect against repository corruption or pollution of the repository with illegal content.  To start along the path to commit access, changes should first be provided as patches.  If these are not too large they can be sent as attachments to the mailing list.  But note that large attachments cause strain on the open source infrastructure so, instead, 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.
These easy to jump over hurdles are simply designed to protect against repository corruption or pollution of the repository with illegal content.


If using a subversion command line client, a patch can be created by typing:
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 precede.  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.
<syntaxhighlight lang="bash">
svn diff > my_change.patch
</syntaxhighlight>
 
<code>my_change.patch</code> can be any file name.  If using a git-svn command line client, type:
<syntaxhighlight lang="bash">
git format-patch
</syntaxhighlight>
 
For more information, run one of:
<syntaxhighlight lang="bash">
svn help diff
git help format-patch
</syntaxhighlight>
 
Note that patches should be small in size, and that each patch should correspond to a single purpose.  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 ===
Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/97620"

Navigation menu