FGAddon: Difference between revisions

Jump to navigation Jump to search
267 bytes added ,  19 September 2015
→‎Team development: Expansion of this subsection.
(→‎Development scenarios: Added a new subsection about team development directly on FGAddon.)
(→‎Team development: Expansion of this subsection.)
Line 315: Line 315:
=== Team development ===
=== Team development ===


This simplest way to work as a team is for each developer to either have a [[#Individual developer|svn copy of FGAddon]] or a [[#Individual developer (git-svn)|git-svn copy of FGAddon]], and everyone commits directly to FGAddon.  Communication and coordination between the team members may be best on the [http://forum.flightgear.org/ FlightGear forum].
{{Note|Development scenario:  All members of the team are acting as gatekeepers, and all commits are made directly to FGAddon, either using svn or git-svn.}}


This simplest way to work as a team is for each developer to either have a [[#Individual developer|svn copy of FGAddon]] or a [[#Individual developer (git-svn)|git-svn copy of FGAddon]], and everyone commits directly to FGAddon.  Communication and coordination between the team members may be best on the [http://forum.flightgear.org/ FlightGear forum].  In this scenario, the team needs to take the initiative and apply for everyone to be granted commit access.


=== Private team development (git-svn) ===
=== Private team development (git-svn) ===

Navigation menu