Page History

...

Being a committer in FINERACT is a responsibility that we wish to encourage as many good contributors as possible to share with us.  It is also an honor which is earned by good behavior.

Apache explains what values underlie Apache community work here: https://community.apache.org/contributors/

FINERACT will designate contributors to committers via the following process.

1. A current committer will decide to sponsor 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 If within 72 hours of the proposal, no committers have vetoed the proposal, the proposal is accepted.
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 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.

Because committers determine who will become committers, they need to be able to recognize good committers.  A good committer also has other qualities.

Developer committer qualities

...

• 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, and
• mentoring other contributors, andbe a good judge of whether another contributor would make a good committer.

Community Liaison Committer qualities

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

• helping other users learn to use FINERACT,
• helping programmers learn what users need,
• testing FINERACT for correctness, robustness, scaleability, security, or useability,
• connecting users with complementary needs with each other,
• owning and fixing their mistakes, and
• mentoring other contributors, andbe a good judge of whether another contributor would make a good committer.

Developer committer rights and responsibilities

...