community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bertrand Delacretaz <bdelacre...@apache.org>
Subject Re: Project Culture and Commit Rights
Date Fri, 11 Jan 2013 08:43:00 GMT
On Sat, Jan 5, 2013 at 4:35 PM, Benson Margulies <bimargulies@gmail.com> wrote:
> ...There's a weaker form of this idea that looks at two populations of
> potential contributors: the members of the Apache Software Foundation
> (members@) and all of the people who have been granted commit rights on all
> of the projects (committers@). Projects that don't feel prepared to offer
> commit-on-demand to the world at large might feel inclined to do so for
> (one or both of) these groups...

As the ASF aims to give PMCs as much freedom as possible, I'd favor a
solution where PMCs can decide themselves who they give write
permission to their code repositories.

Basing this on groups, project A could say that it's friends with
projects B and C, and as such allow all people who can write to B and
C to write to A as well, based on group authorizations.

We used to do that with Cocoon, where B and C were Lenya and Forrest -
as sibling projects, we felt that those folks should be able to commit
small fixes directly without asking, but they were expected to ask
before making any substantial changes to our code.

A PMC could then decide to give write access to all ASF members, all
committers, etc. Letting PMCs make this decision avoids requiring the
whole ASF (that's 150 projects today) to agree on this, which is in
line with how we usually handle things - modularization vs. requiring
everybody to agree.

-Bertrand

Mime
View raw message