...
FINERACT will designate contributors to committers via the following process.
- A current committer PMC member will decide to sponsor a contributor.
- 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.
- If within 72 hours of the proposal, no committers have vetoed the proposal, the proposal is accepted.
- 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.
...
To be made a developer committer, a contributor should have developed experience with FINERACT by
- creating bug fixes AND or 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.
...
- helping other users learn to use FINERACT, or
- helping programmers learn what users need by providing detailed business requirements and use cases required for functional specifications, or
- testing FINERACT for correctness, robustness, scaleability, security, or usability, and reporting bugs and issues found, or
- connecting users with complementary needs with each other on the list, or
- supporting implementers and users of FINERACT with best practices and lessons learned from practical implementation, or
- writing documentation and tutorials for usage of FINERACT and design of financial services,
...
- Everything listed in http://www.apache.org/dev/new-committers-guide.html
- Reviewing code before it is committed using the Code Review Guide.
- Reviewing code for other committers after it is committed.
- Taking part in conversations on the dev mailing list when he or she has something to contribute.
- Keeping all decision-making processes transparent for all project participants.
Community Liaison Committer rights and responsibilities
- Everything listed in http://www.apache.org/dev/new-committers-guide.html
- Prioritizing and refining user stories and tickets on JIRA.
- Moderating and maintaining functional documentation on FINERACT.
- Taking part in conversations on the dev mailing list when he or she has something to contribute.
- Keeping all decision-making processes transparent for all project participants.
PMC member rights and responsibilities
- Taking part in conversations on the private mailing list and keeping those conversations private.
- Proposing new committers and new PMC members.
- Representing Apache Fineract to the ASF Board.
- Occasionally cleaning up the committer list.
How to clean up the committer list
- Protecting the Apache Fineract brand from misuse
- Keeping all decision-making processes transparent for all project participants
- Look for committers who have not performed any visible public action listed above for at least 6 months.
- Write to each such committer to ask them if they still wish to be a committer.
- Anyone who responds that they no longer wish to be a committer can be removed from the committer list, thus loosing all rights and responsibilities associated with being a committer.
- Anyone who does not respond in four weeks can be removed from the committer list, thus loosing all rights and responsibilities associated with being a committer.
- Any committer can at any time request removal from the committer list.