FlightGear Git: splitting FGData: Difference between revisions

FlightGear Git: splitting FGData (view source)

1,116 bytes added , 19 October 2011

m

no edit summary

8,567

edits

@@ Line 13: / Line 13: @@
 ** How to deal with licences? Until now there was a COPYING file in fgdata. When aircraft are split in seperate repositories, they'll likely need to include a license reference themselves.
 ** Need a concept for release management, maintaining version numbers, release branches, release tags et. al.
+=== Reasons to put aircraft under a single project ===
+* '''Advantages'''
+** The current fgdata-developers team can access any single aircraft, for easy/quick fixes. For example when something is found to be wrong and copied among several aircraft (which happens due to copy&paste). Or when something about the sim itself changes and aircraft msut be adapted to run on an upcoming release.
+** When an aircraft developers decides to leave, the repo can easily be taken over by other developers. If the author set up his own repository, we'd have to create a new repository (and thus change all references/links).
+** It allows us to use [http://flightgear-bugs.googlecode.com the bug tracker] for aircraft. Most developers won't clone aircraft repos from all kind of places, just to help fixing bugs.
+* '''Disadvantages'''
+** Authors won't be able to choose their own license.
+*** The FlightGear Aircraft project has been set to "License: Other/Multiple". This allows (in theory, we first need to agree on this) any aircraft author to add whatever license file to his/her aircraft and still put it under the project.
 == Starting new aircraft ==