8,567
edits
FlightGear Git: splitting FGData: Difference between revisions
Jump to navigation
Jump to search
m
FlightGear Git: splitting FGData (view source)
Revision as of 19:15, 18 October 2011
, 18 October 2011no edit summary
mNo edit summary |
mNo edit summary |
||
| Line 15: | Line 15: | ||
== Starting new aircraft == | == Starting new aircraft == | ||
New aircraft should not be commited to fgdata. A seperate repository should be created instead. Contact a FlightGear Aircraft admin to get your repository included in the FlightGear Aircraft project. You, as author, will get | New aircraft should not be commited to fgdata. A seperate repository should be created instead. Contact a FlightGear Aircraft admin to get your repository included in the FlightGear Aircraft project. You, as author, will get commit rights for that repository. | ||
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. | ||
| Line 73: | Line 73: | ||
** For now we just skipped dots, so Supermarine-S.6B has a repo called <tt>supermarine-s6b</tt> (note that Gitorious also does not distinct capitals). | ** For now we just skipped dots, so Supermarine-S.6B has a repo called <tt>supermarine-s6b</tt> (note that Gitorious also does not distinct capitals). | ||
* What rights should aircraft authors get? | * What rights should aircraft authors get? | ||
** Commit/review might be best. If they are granted admin rights, they can delete the repo and | ** Commit/review might be best. If they are granted admin rights, they can delete the repo and remove the fgdata-developers as collaborators. When they do the later, there's no way we can regain control over the repo. We won't even be able to delete it from the FlightGear Aircraft project. | ||
{{Appendix}} | {{Appendix}} | ||