Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: harmony-dev@incubator.apache.org
Message-ID: <79028263.1127222675284.JavaMail.root@set.superlinksoftware.com>
Date: Tue, 20 Sep 2005 10:16:36 -0400
From: acoliver@apache.org
Reply-To: acoliver@apache.org
To: harmony-dev@incubator.apache.org
Subject: Re: [discussion] Committer Addition Process
In-Reply-To: <E7205DFC-8E20-4B62-B0AA-D5E4B0F1253C@apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla Thunderbird 1.0.6 (Macintosh/20050716)
References: <E7205DFC-8E20-4B62-B0AA-D5E4B0F1253C@apache.org>

> So I'd like to keep it really simple :
> 
> 1) Anyone with a contribution that would belong in SVN can be  
> considered for commit status by the PMC (PPMC while in incubation).   
> This contribution can be anything - new code, a patch to existing  code, 
> documentation, a change to the website, testing code or other  
> resources, etc. (Hopefully this gets people interested in harvesting  
> good docs from the WIKI, as that's worth commit status IMO)
> 

I'm not sure how this seeds initial committers though.  Start with this, 
any existing Apache committer or member who has turned in his ACQ and 
requests commit access.  This will at least get an initial set of 
committers to the repository.  Its also the "likely suspects".

> 2) If offered commit status by the PMC and accepted by the  individual, 
> we will get an ACQ from the individual along with an ICLA  if not 
> already on file with the ASF secretary.  I'd ask that  individuals wait 
> to do an ACQ until offered, as the ACQ will be  evolving over time as we 
> learn, and I'd like to ask that a new  committer have the current 
> version on file as of the date of them  being added as a commmitter.
> 

This will probably be less of a problem when there is code.

> 3) The individual would be given free reign in the area to which they  
> contributed, and trusted to engage with the relevant part of the  
> community for other areas of our codebase/resourcebase.
> 

And if they request access to another area provided they have no issues 
they should be given so forthwidth.  Start one UNIFIED project not 12.

> Comments?  If people agree to this, I'd like to add this to our  website 
> as part of the project policy.
> 

If this opens the repository to code then I think its great.  If not, 
then I think it sucks.

-Andy

> geir
>