Becoming a Committer
Technically, committers are people who have write access to the Arches Git repository. Committers can submit their own patches or patches from others.
This privilege is granted with some expectation of responsibility: committers are people who care about the Arches project and want to help meet its goals. Committers are not just people who can make changes, but people who have demonstrated their ability to collaborate with the team, get the most knowledgeable people to review code, contribute high-quality code, and follow through to fix issues (in code or tests).
A committer is a contributor to the Arches projects' success and a citizen helping the project succeed. See Committer's Responsibility.
In a nutshell, contribute 5 non-trivial patches and get at least two different people to review them (you'll need two people to support you). Then ask someone to nominate you. You're demonstrating your:
- commitment to the project (5 good patches requires a lot of your valuable time),
- ability to collaborate with the team,
- understanding of how the team works (policies, processes for testing and code review, etc),
- understanding of the projects' code base and coding style, and
- ability to write good code (last but certainly not least)
A current committer nominates you by slacking the team on the Archesproject development channel
- your first and last name
- a link to your Git profile
- an explanation of why you should be a committer,
- embedded list of links to revisions (about top 3) containing your patches
One other committer needs to second your nomination. If no one objects in 5 working days (U.S.), you're a committer. If anyone objects or wants more information, the committers discuss and usually come to a consensus (within the 5 working days). If issues cannot be resolved, there's a vote among current committers.
Once you get approval from the existing committers, we'll send you instructions for write access to Git. You'll also be added to the Archesproject development channel
In the worst case, this can drag out for two weeks. Keep writing patches! Even in the rare cases where a nomination fails, the objection is usually something easy to address like "more patches" or "not enough people are familiar with this person's work."
You don't really need to do much to maintain committer status: just keep being awesome and helping the Arches project!
In the unhappy event that a committer continues to disregard good citizenship (or actively disrupts the project), we may need to revoke that person's status. The process is the same as for nominating a new committer: someone suggests the revocation with a good reason, one other person seconds the motion, and a vote may be called if consensus cannot be reached. I hope that's simple enough, and that we never have to test it in practice.
(Source: inspired by https://github.com/v8/v8/wiki/Becoming-a-committer )
