Hi Team,

As we recently vote two committers, someone came to me ask about the what's
the criterial to become a committer.  It's really a good question.

>From what I learned by participating bunch of Apache projects, the first
criterial is you need to do enough contribution to earn enough credit for
the project. For most case, it's means you submit enough patches which
makes other committer tired to apply patch for you.  But it's don't means
you have to write lots of code to be the committer.

The key value of the committer is* you are committed to the project and are
productively contributing to its success.*

Here is a great explanation about the community contribution[1] and anyone
can become a committer in the Apache[2].
I'd like to quote some of the content and share with everyone here.

The foundations of an Apache project and how the community contributes to
it is sometimes referred to by the acronym CoPDoC:

   - (Co)mmunity - one must interact with others, and share vision and
   knowledge
   - (P)roject - a clear vision and consensus are needed
   - (Do)cumentation - without it, the stuff remains only in the minds of
   the authors
   - (C)ode - discussion goes nowhere without code


There is nothing at The Apache Software Foundation that says you must write
code in order to be a committer. Anyone who is supportive of the community
and works in any of the CoPDoC areas is a likely candidate for committer
ship.

Apache is a meritocracy. That is, once someone has contributed sufficiently
to any area of CoPDoC they can be voted in as a committer. Being a
committer does not necessarily mean you commit code, it means you are
committed to the project and are productively contributing to its success.

One of the key contributions people can make to the community is through
the support of a wide user base by assisting users on the user list,
writing user oriented docs and ensuring the user viewpoint is understood by
all developers. A main idea behind being a committer is the ability to be a
mentor and to work cooperatively with your peers.

Some of those users become committers in their own right. Some will test
code, some will write documentation, some will do bug triage and some will
write code.

[1]https://community.apache.org/contributors/#contributing-a-project-copdoc
[2]https://community.apache.org/contributors/#anyone-can-become-a-committer


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

Reply via email to