Return-Path: 
 <commons-dev-return-20673-qmlist-jakarta-archive-commons-dev=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-commons-dev-archive@apache.org
Received: (qmail 41455 invoked from network); 6 Dec 2002 20:43:19 -0000
Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131)
  by daedalus.apache.org with SMTP; 6 Dec 2002 20:43:19 -0000
Received: (qmail 16430 invoked by uid 97); 6 Dec 2002 20:44:27 -0000
Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org
Received: (qmail 16390 invoked by uid 97); 6 Dec 2002 20:44:26 -0000
Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:commons-dev-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:commons-dev-subscribe@jakarta.apache.org>
List-Help: <mailto:commons-dev-help@jakarta.apache.org>
List-Post: <mailto:commons-dev@jakarta.apache.org>
List-Id: "Jakarta Commons Developers List" <commons-dev.jakarta.apache.org>
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Delivered-To: mailing list commons-dev@jakarta.apache.org
Received: (qmail 16378 invoked by uid 98); 6 Dec 2002 20:44:25 -0000
X-Antivirus: nagoya (v4218 created Aug 14 2002)
Message-ID: <20021206204318.41217.qmail@web12403.mail.yahoo.com>
Date: Fri, 6 Dec 2002 12:43:18 -0800 (PST)
From: Morgan Delagrange <mdelagra@yahoo.com>
Reply-To: morgand@apache.org
Subject: Re: [beanutils] moving reflection classes out of beanutils 
To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
In-Reply-To: <BDCACB16-0942-11D7-8A15-003065DC754C@blueyonder.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

--- robert burrell donkin
<robertburrelldonkin@blueyonder.co.uk> wrote:

<snip/>

> 
> the guidelines have an inbuilt mechanism whereby
> components may - if they 
> wish - prevent a new existing commons committer
> joining. that is, they can 
> veto the addition of the committers name to the list
> of developers for the 
> component.
> 
> - robert
> 

Are you sure about that?  I don't see that anywhere:

  http://jakarta.apache.org/commons/charter.html

AFAIK there are no restrictions on existing committers
working on other existing components.  If you're
implying that committers can exercise their veto on
the actual commit of a new developer's name to the
STATUS file, that's not so.  Commits can only be
vetoed for valid technical reasons.  I can't imagine
the technical justification for "you can't work on my
component". 

Adding your name to the STATUS file is a courtesy. 
Nobody should be ostracized for not doing it:

Version 1.8:
http://cvs.apache.org/viewcvs/jakarta-commons/beanutils/STATUS.html#rev1.8

Version 1.6:
http://cvs.apache.org/viewcvs/jakarta-commons/beanutils/src/java/org/apache/commons/beanutils/MethodUtils.java#rev1.6

- Morgan


=====
Morgan Delagrange
http://jakarta.apache.org/taglibs
http://jakarta.apache.org/commons
http://axion.tigris.org
http://jakarta.apache.org/watchdog

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

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