You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@commons.apache.org by Sander Striker <st...@apache.org> on 2002/10/24 19:01:20 UTC

Carte blanche commit access, WAS: RE: veto rights

> From: Morgan Delagrange [mailto:mdelagra@yahoo.com]
> Sent: 24 October 2002 18:35

> --- Peter Donald <pe...@apache.org> wrote:
>> On Thu, 24 Oct 2002 11:20, Morgan Delagrange wrote:
>> It is up to the components maintainers/developers.
>> They are the people who are in the best position
>> to judge whether a candidate should be given voting 
>> rights. Some may choose to be more exclusive and
>> some may be a free for all - however it will always
>> be the develoeprs who decide where their component 
>> evolves. 
> 
> See, that's what bugs me.  If I contribute significantly,
> I should be able to vote in my opinion.

Vote on what?  On the components you have _significantly_
contributed to (IOW, you should have commit privilidges)?
Or on any component?  If the latter, I'd say, no, you
haven't earned the right to vote on those components
(that is, not cast binding votes, non-binding is ok).

> However in the absense of a reasonable metric for
> significant contributions, it's left to the judgement
> of established developers who may or may not be
> "exclusive".  Again, I think you err on the side of
> inclusion.

Personally I think it works fine.  If not, there is
always a PMC that can step in and ask why this significant
contributor still hasn't got commit privs.
 
> Well, I don't quite agree, but I'm willing to concede
> the point as long as once I gain commit access to
> "Apache Commons", I can commit to all components and
> not just the component(s) to which I've already
> contributed. 

I'd say "forget it" personally.  I don't think it is
a good idea to give people carte blanche once they
have contributed to one component.  At least not
without the explicit permission of the developers of
that component.

If your patches are good, gaining commit privilidges
shouldn't be a problem.  If it is, because the developers
on that component are being (overly) exclusive, the
PMC can step in and ask for clarification.  [deja-vu]

I'm getting the feeling I'm rehashing something that
was said before though... And yes:  
  Message-ID: <20...@lyra.org>

Greg said it a lot better too ;)

Sander