8,564
edits
Martin.spott (talk | contribs) (starter package) |
mNo edit summary |
||
Line 30: | Line 30: | ||
The current fgdata developers will have access to every single aircraft repository. In order to maintain aircraft that no longer have an active author, fix global bugs etc. Other users can create merge requests to get their fixes/improvements commited. | The current fgdata developers will have access to every single aircraft repository. In order to maintain aircraft that no longer have an active author, fix global bugs etc. Other users can create merge requests to get their fixes/improvements commited. | ||
== Step 1: Split aircraft into separate repositories == | == Step 1: Split aircraft into separate repositories (DONE) == | ||
Aircraft are split into "private" repositories, under the [https://gitorious.org/flightgear-aircraft FlightGear Aircraft project]. Repositories for all aircraft in current fgdata have been created as of 17 October. Repository names equal directory-names (with the exceptions of dots (.) and capitals (ABC), as those are not supported by Gitorious. | Aircraft are split into "private" repositories, under the [https://gitorious.org/flightgear-aircraft FlightGear Aircraft project]. Repositories for all aircraft in current fgdata have been created as of 17 October. Repository names equal directory-names (with the exceptions of dots (.) and capitals (ABC), as those are not supported by Gitorious. | ||
Line 60: | Line 60: | ||
== Step 2: Remove all aircraft from fgdata == | == Step 2: Remove all aircraft from fgdata == | ||
A new fgdata repository without any aircraft is created, pushed to gitorious and tested. | |||
== Step 3: Write/update manuals == | == Step 3: Write/update manuals == |