159
edits
FlightGear Git: splitting FGData: Difference between revisions
Jump to navigation
Jump to search
m
FlightGear Git: splitting FGData (view source)
Revision as of 22:35, 9 December 2011
, 9 December 2011→A new plan for splitting fgdata
| Line 83: | Line 83: | ||
# The FlightGear fgaircraft repository maintainers reserve the right to revoke commit access of an individual committer. They can only exercise their right after consensus has been reached among the maintainers, and only in cases of | # The FlightGear fgaircraft repository maintainers reserve the right to revoke commit access of an individual committer. They can only exercise their right after consensus has been reached among the maintainers, and only in cases of | ||
## misuse of commit rights by the offending developer, or | ## misuse of commit rights by the offending developer, or | ||
## prolonged inactivity of the committer ( | ## prolonged inactivity of the committer (more than a year of inactivity) | ||
# Aircraft that have not been maintained by the prime committer for a prolonged period of time are considered to have been abandoned and may be assigned to a different committer. The obvious exception to this rule is formed by aircraft that have a high level of completeness that are maintained by committers who are still very active in other areas of FlightGear's development. | # Aircraft that have not been maintained by the prime committer for a prolonged period of time are considered to have been abandoned and may be assigned to a different committer. The obvious exception to this rule is formed by aircraft that have a high level of completeness that are maintained by committers who are still very active in other areas of FlightGear's development. | ||
# Commit rights will be given after the authors have shown a reasonable level of competence in both aircraft development and GIT usage. While the aircraft developer is still in the process of obtaining the required skills, he or she can seek a mentor who will handle any merge requests. | # Commit rights will be given after the authors have shown a reasonable level of competence in both aircraft development and GIT usage. While the aircraft developer is still in the process of obtaining the required skills, he or she can seek a mentor who will handle any merge requests. | ||