I would like to propose an alternative: the "GRAND-FATHER"-ing proposal to make all existing hadoop committers be committers on all three new sub-projects. And then adopt a process to create new committers specific to one sub-project. There are two main reasons for doing this:
1. The proposal of breaking up the existing set of committers into individual sub-projects seem to be adhoc. I would hate to support a scheme that causes more controversy, especially among the core set of committers. 2. I have never seen an existing committer abuse his priviledge/responsibility to commit code that is not approved by the community-at-large thanks, dhruba On Fri, May 15, 2009 at 10:18 AM, Owen O'Malley <omal...@apache.org> wrote: > On May 14, 2009, at 7:15 PM, Owen O'Malley wrote: > > Another aspect of the split is that I need to divide the committers up to > the sub-projects where they work. I'd propose the following breakdowns: > > core: ab,acmurthy,cdouglas,cutting,ddas,dhruba,enis,gkesavan,hairong,johan > lohit,mahadev,matei,nigel,omalley,rangadi,runping,sharad,shv,sradia, > stevel,szetszwo,taton,tomwhite,yhemanth,zshao > > hdfs: acmurthy,cdouglas,cutting,dhruba,enis,gkesavan,hairong, > nigel,omalley,rangadi,shv,sradia,stevel,szetszwo,tomwhite > > mapreduce: acmurthy,cdouglas,cutting,ddas,enis,gkesavan,johan, > lohit,mahadev,matei,nigel,omalley,runping,sharad,sradia,stevel,szetszwo, > tomwhite,yhemanth,zshao > > I'm not trying to cut people off, just figuring out where people have > contributed and committed patches in the past. So please look at the > sub-projects I've got you listed in and ensure they match your desires. And > of course, if we realize there was a mistake, it is easy to fix later, by > just asking. > > -- Owen