Draft: Work in Progress
This document is subject to change without notice.
Being a committer in FINERACT is a responsibility that we wish to encourage as many good developers as possible to share with us. It is also an honor which is earned by good behavior.
FINERACT will designate contributors to committers via the following process.
- A current committer will decide to sponsor an existing contributor
- The sponsor will propose via the private mailing list, that a contributor be made a committer. At this point it would be unkind to inform the contributor in case the proposal fails the vote.
- Within 72 hours of the proposal, at least 20% of the current committers have voted +1, and none have vetoed.
- The sponsor will ask the contributor if he or she wishes to become a committer.
- If contributor so desires, the sponsor will set in motion the processes necessary to add a new committer to FINERACT.
If a contributor does not get sufficient votes, or is vetoed there is no need to inform him or her that a vote occurred. Depending on the reason for a veto, the question may be raised again at a later date.
What qualities should a committer possess? To be made a committer, a contributor should have developed experience with FINERACT by
- creating bug fixes AND programming features,
- producing multiple high quality code changes as determined by an existing committer using the Code Review Guide,
- owning and fixing their own mistakes,
- mentoring other contributors, and
- be a good judge of whether another contributor would make a good committer.