> From: Peter Donald [mailto:peter@;apache.org] 
<snip/>


> 
> The problem occured when commits were made to 
> phoenix/cornerstone codebase by 
> someone who had not participated in phoenix/cornerstones 
> development and were 
> made in violation of vetos. Especially given that the person 
> had stated that 
> they didn't mind if phoenix died. Then combine this with 
> other problem 
> behaviour (interaction with james group, licensing stuff, 
> personal attacks, 
> so and so forth) and you have the problems. Conflict is not a 
> problem - the 
> reaction to conflict is.

And this is reason for a Pheonix PMC and/or a Cornerstone PMC.
Or at least making commit privs not a blanket thing across CVS
repositories in the Avalon umbrella.

I.e. Just because you were given commit privs to the LogKit
project does not mean you should have commit privs for Framework.

As it stands now, we have a *very* liberal commit granting policy.
Some of it stemmed from when Avalon was much smaller.  It has obviously
grown.

Am I saying we should revoke all commit privs if a committer goes
bezerk?  No.  I for one don't want to be on the receiving end of that.
However it begs the question, should we separate the Avalon
communities?  We have the same basic core of developers, and we do
work on things that span boundaries of the different CVS repositories.

If we want to fine tune the commit privs, and consequently the voting
privs (i.e. commit privs == voting privs), then we need current
committers to volunteer to surrender the commit privs of the CVS
repositories they have no interest in.  We have five or more CVS
repositories, which means we have that many potential communities.

>From that point forward, we would only grant commit privs to the
CVS module that the developer has proved themselves in.  The only
advantage of being a committer in one of the projects is that
your reputation can be "grandfathered" in to the other projects
should those committers agree.

Hopefully I am making sense here....


--
To unsubscribe, e-mail:   <mailto:avalon-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@;jakarta.apache.org>

Reply via email to