...
Because committers determine who will become committers, they need to be able to recognize good committers. A good committer has several qualities. These are outlined below. Note that committers do not necessarily need to write code. Simply : simply supporting the community in a way considered valuable can be enough to become a committer. See https://community.apache.org/contributors/ for more information about this.
...
To be made a developer committer, a contributor should have developed experience with Apache DataFu by:
- creating bug fixes AND programming features,;
- producing multiple high quality code changes as determined by an existing committer;
- owning and fixing their own mistakes, ; and
- mentoring other contributors.
...
To be made a community liaison committer, a contributor should have developed experience with Apache DataFu by:
- helping other users learn to use Apache DataFu,;
- testing Apache DataFu for correctness, robustness, scaleabilityscalability, security, or usability, and reporting bugs and issues found,;
- writing documentation and tutorials for usage of Apache DataFu;
- owning and fixing their mistakes, ; and
- mentoring other contributors.
...
- Look for committers who have not performed any visible public action listed above for at least 12 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 losing all rights and responsibilities associated with being a committer.
- Any committer can, at any time, request removal from the committer list.
...