Page History

...

1. A current committer will decide to sponsor an existing a contributor.
2. The sponsor will propose via the private mailing list, that a contributor be made a committer. The sponsor should explain why he or she believes the contributor should be made a committer.  At this point it would be unkind to inform the contributor in case the proposal fails the vote.
3. Within 72 hours of the proposal, at least 20% of the current no committers have voted +1, and none have vetoedvetoed the proposal.
4. The sponsor will ask the contributor if he or she wishes to become a committer.
5. 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.

Developer committer qualities

To be made a developer committer, a contributor should have developed experience with FINERACT by

...

Community Liaison Committer qualities

...

To be made a community liaison commiter, a contributor should have developed experience with FINERACT by

• helping other users learn to use FINERACT
• helping programmers learn what users need
• connecting users with complementary needs with each other
• owning and fixing their mistakes
• mentoring other contributors, and
• be a good judge of whether another contributor would make a good committer.

Developer committer rights and responsibilities

...