incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Garrett Rooney" <>
Subject Re: piling on
Date Wed, 19 Jul 2006 22:13:14 GMT
On 7/19/06, Roy T. Fielding <> wrote:
> I believe that it is a bad idea to allow people to add themselves
> to a proposal as committers without first obtaining the consent of
> the person(s) making the proposal.  Being a committer in the incubator
> is giving a person the right to veto code changes based on whatever
> technical reason they deem significant.  We should not hand out that
> right like candy to anyone who happens to edit a wiki page.
> Podlings must be open to new contributors and should add contributors
> to the list of committers fairly quickly, at least when compared to
> more established Apache projects.  However, the core team must be
> allowed to select other core members based on mutual consensus,
> since consensus is how code changes are approved.  How a community
> exercises that consensus is one of the primary determinants for
> graduation.
> In contrast, letting anyone "pile on" to a podling while it is at
> the proposal stage is placing an unequal burden on a new podling
> that we would never place on a full project.  If the community is
> not cohesive, no consensus will be possible and we effectively
> hamstring the podling before it is even started.

+1, I would much prefer to see interested parties starting to
contribute in the usual way (patches sent to a development mailing
list) and get their commit access once the project has decided they
are ready for it.

Of course, this assumes that the project members are on the lookout
for new blood and are actively noticing worthy new contributors and
voting them in as committers, but a new podling should be doing that


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message