159
edits
FlightGear Git: splitting FGData: Difference between revisions
Jump to navigation
Jump to search
FlightGear Git: splitting FGData (view source)
Revision as of 15:14, 23 September 2012
, 23 September 2012→Keeping all aircraft under a single project
m (Robot: Automated text replacement (-aircaft +aircraft)) |
|||
| Line 43: | Line 43: | ||
* '''Disadvantages''' | * '''Disadvantages''' | ||
** Authors won't be able to choose their own license. | ** 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. | *** 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. However, the use of a ''common'' license for all ''community aircraft'' has many advantages and has also contributed to the success of the FG project (new aircraft can be easily based on existing aircraft, can copy elements from other aircraft without triggering a complicated mixed license situation), and specifically the GPL has many advantages for the FG project (see [[Changing the FlightGear License]] for details why FG wants to stick to the GPL). Authors preferring an other license can of course already (and continue to) do so - except that their aircraft is not in the community repository. | ||
=== Organizing Aircraft by Logical units === | === Organizing Aircraft by Logical units === | ||