Becoming a committer in Apache DataFu is a responsibility we would like to encourage.  This page outlines the process of becoming one.

Anyone can contribute to Apache DataFu.  If you become a valuable contributor to the project you may be invited to become a committer, which brings with it certain privileges and responsibilities.  For general guidance on being a good contributor, Apache explains what values underlie good Apache community work here: https://community.apache.org/contributors/.

Apache DataFu will designate contributors to committers via the following process.

  1. A current committer will decide to sponsor a contributor.
  2. The sponsor will initiate a vote in the private mailing list regarding the contributor becoming 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 vote fails to lead to the contributor becoming a committer.
  3. The vote will take place over 72 hours.  This vote is considered a procedural vote, as explained in https://www.apache.org/foundation/voting.html.  The majority of the votes must be positive for the vote to pass.  There are no vetoes.  At least three votes are required.
  4. If the vote passes, the sponsor will ask the contributor if he or she wishes to become a committer.
  5. If the contributor so desires, the sponsor will set in motion the processes necessary to add a new committer to Apache DataFu.

If the vote does not pass there is no need to inform him or her that a vote occurred.  Depending on the reasons for it not passing, the vote may be raised again at a later date.

A current committer may also choose to start a discussion in the private mailing list prior to initiating a vote in order to gather feedback on the proposal.

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 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.  

Developer committer qualities

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.

Community Liaison Committer qualities

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, scalability, 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.

Developer committer rights and responsibilities

Community Liaison Committer rights and responsibilities

  • Everything listed in http://www.apache.org/dev/new-committers-guide.html
  • Prioritizing and refining tickets in JIRA. 
  • Moderating and maintaining documentation on Apache DataFu.
  • Taking part in conversations on the dev mailing list when he or she has something to contribute.

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 DataFu to the ASF Board.

Thanks to the authors of Apache Fineract's Becoming a Committer for serving as the basis of this guide. 

 

  • No labels