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 09:44, 19 October 2011
, 19 October 2011→Questions
mNo edit summary |
m (→Questions) |
||
| Line 83: | Line 83: | ||
** An flightgear-aircraft/UIUC repo has been created, we can delete it if needed later on. | ** An flightgear-aircraft/UIUC repo has been created, we can delete it if needed later on. | ||
* Gitorious does not support dots in repository names. | * Gitorious does not support dots in repository names. | ||
** 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. This does not seem to be a problem though, since git clone uses the original directory name). | ||
* 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 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. | ** 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}} | ||