FlightGear Git: splitting FGData: Difference between revisions

FlightGear Git: splitting FGData (view source)

950 bytes added , 10 December 2011

Comments about the new plan.

884

edits

@@ Line 88: / Line 88: @@
 # If the aircraft developer is uncomfortable in working with GIT he or she can also opt to choose a "mentor" who will handle the merge requests for them.
 # In addition to these rules, anybody contributing to the FlightGear project is encouraged to work with personal clones and submit merge requests.
+=Comments on the new plan=
+That sounds like the situation we already have - the only difference: the aircraft are just splitted from FGData, and the maintainer of an Aircraft-project can get the rights to commit without any magic.
+But with that there are lot of rules with exceptions. From my daily real life job I do know, that many rules with exceptions may things more complicated and provoke discussions and conflicts.
+So my question is: How can we see that "a reasonable level of competence in both aircraft development and GIT usage" is there? Does he has to be checked? Which level of competence is needed for making an aircraft?
+It is good to see that the existing rules are finally formalized, so we get a clear guideline.
+It is also good to see that people should be more encouraged to submit merge requests. But this also means that those with commit rights should be more encouraged to review those merge requests and commit them!
 {{Appendix}}