Esteve Fernandez wrote:
On Wednesday 24 December 2008 23:31:30 David Reiss wrote:
Erlang - ?
Todd Lipcon (Toad on IRC) is really responsive to questions about the
Erlang mapping. Chris Piro or I can also look at these issues.
Then, I think it would make sense to give Todd committer access.
I don't think that is necessary. As long as a committer can check in
patches that are approved, I don't know of any reason that the primary
reviewer needs to be a committer.
The problem is, who approves and applies them? There's still a bunch of
tickets with patches that have been voted up and that nobody committed.
Someone (I think it was Doug) said that giving reviewers committer status
motivates people to keep reviewing and to get more involved. I can't agree
more with that statement and I think it's important to build a healthy
community (one of the goals of the Apache brand).
I won't discuss the merits the of the individual, just the process. I'm
not subscribed to the private thrift list, so don't know what has been
discussed (if anything).
In general in an apache project, the process for getting people commit
access is for an existing 'PMC' member to recognize the merits of an
individual and raise it on the private list, where it is discussed. It
is discussed in private as some people may feel that the person is not
ready yet, and saying that in public could discourage the individual.
"nominating" the person on a public list is generally seen as poor form,
as it might preempt the discussion, and lead to no response from the
project.
and correct, it's not just developers who can get committer status in
apache projects. Anyone who actively contributes to the project is
eligible. The same goes for ASF membership. We have several ASF members
who have never written a line of code in their life, but their
contributions in other ways are seen as useful.
Regards
Ian
