Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Received-SPF: pass (athena.apache.org: domain of Jim.Kellerman@microsoft.com
 designates 131.107.115.214 as permitted sender)
From: "Jim Kellerman (POWERSET)" <Jim.Kellerman@microsoft.com>
To: "core-dev@hadoop.apache.org" <core-dev@hadoop.apache.org>
Date: Fri, 15 May 2009 14:41:33 -0700
Subject: RE: project split coming soon!
Thread-Topic: project split coming soon!
Thread-Index: AcnVpUvN3tcsTGUeTcSBe2nHvlPljwAAC63Q
Message-ID: 
 <EAFDEC03CDA5D644878904F4A8F0158A6286DB8FDE@NA-EXMSG-C103.redmond.corp.microsoft.com>
References: <C7B25FAC-492D-4BA1-97F6-1263CC585593@yahoo-inc.com>
	 <0AF6234F-8BE5-4F99-931A-12B3B6FF5242@apache.org>
 <4aa34eb70905151436v40b9e3c3jda71725931dcd201@mail.gmail.com>
In-Reply-To: <4aa34eb70905151436v40b9e3c3jda71725931dcd201@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

I have to agree with Dhruba. I don't see the need to split up committers
(esp if they are on the PMC). Although Stack and I cannot contribute to
Hadoop or Zookeeper currently because of our employer, that situation could
change, and if it does, I don't think either of us should have to go throug=
h
the "trial by fire" to get re-instated.

---
Jim Kellerman, Powerset (Live Search, Microsoft Corporation)


> -----Original Message-----
> From: Dhruba Borthakur [mailto:dhruba@gmail.com]
> Sent: Friday, May 15, 2009 2:36 PM
> To: core-dev@hadoop.apache.org
> Subject: Re: project split coming soon!
>=20
> 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:
>=20
> 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.
>=20
> 2. I have never seen an existing committer abuse his
> priviledge/responsibility to commit code that is not approved by the
> community-at-large
>=20
> thanks,
> dhruba
>=20
>=20
>=20
> On Fri, May 15, 2009 at 10:18 AM, Owen O'Malley <omalley@apache.org>
> wrote:
>=20
> > 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,szets
> zwo,
> > 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