stratos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sanjiva Weerawarana <>
Subject Re: [DISCUSS] PPMC = or != Committter
Date Tue, 30 Jul 2013 14:22:08 GMT
After many years of thinking that (P)PMC != {commiitters} , one of many
mails from Roy on this topic convinced me some years ago that that's the
right thing to do and as the way ASF was meant to be. So I'm very much for
making every committer a PMC member.

I understand your point Ant that in early stages of a project's life
committership is easier to get. However I'm not for giving committership on
"potential" to contribute .. that's only during start of incubation. After
that everyone has to do *something* real to earn it. I'd rather teach them
the Apache Way rather than make them second class by not making them PMC


On Tue, Jul 30, 2013 at 7:38 PM, ant elder <> wrote:

> Just about all podlings start off with all the initial commiters being on
> the PPMC (I only know of one case where that didn't happen).
> One of the reasons put forward for not automatically making all new
> committers also PMC members is that it can lead to it being harder to make
> people committers. Some projects make it very easy to be a committer and
> grant it to just about anyone who seems like they are willing to do some
> work on the project without requiring any history of contributions.
> Examples of that are Apache Subversion's partial committers or many
> projects give GSoC students commit access when their GSoC project is
> accepted so they don't have the burden of submitting patches. Those sort of
> new committers probably don't have much knowledge of things like ASF
> release requirements and that can be a put off from making them a PMC
> member with a binding vote.
>    ...ant

Sanjiva Weerawarana, Ph.D.
Founder, Chairman & CEO; WSO2, Inc.;
email:; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1
650 265 8311

Lean . Enterprise . Middleware

View raw message