Giridharan Kesavan's omission as a committer is an oversight on part of
the hadoop team. Ideally, he should be listed as a release engineer with
Secondly, QA/Release/etc are necessarily evils to ship a high quality
product while contrib projects are not.
That leaves us with contrib committers.
Can you point to earlier email threads that cover the topic of giving
committer access to contrib projects? Specifically, what does it mean to
award someone committer privileges to a contrib project, what are the
access privileges that come with such rights, what are the dos/don'ts,
Thirdly, are there instances of contrib committers creating branches?
From: Arun C Murthy [mailto:a...@yahoo-inc.com]
Sent: Monday, August 17, 2009 6:18 PM
Subject: Re: Proposal to create a branch for contrib project Zebra
On Aug 17, 2009, at 4:38 PM, Santhosh Srinivasan wrote:
> Is there any precedence for such proposals? I am not comfortable with
> extending committer access to contrib teams. I would suggest that
> be made a sub-project of Hadoop and have a life of its own.
There has been sufficient precedence for 'contrib committers' in
Hadoop (e.g. Chukwa vis-a-vis the former 'Hadoop Core' sub-project)
and is normal within the Apache world for committers with specific
'roles' e.g specific Contrib modules, QA, Release/Build etc.
- in fact, Giridharan Kesavan is an unlisted 'release' committer for
I believe it's a desired, nay stated, goal for Zebra to graduate as a
Hadoop sub-project eventually, based on which it was voted-in as a
contrib module by the Apache Pig.
Given these, I don't see any cause for concern here.
> -----Original Message-----
> From: Raghu Angadi [mailto:rang...@yahoo-inc.com]
> Sent: Monday, August 17, 2009 4:06 PM
> To: firstname.lastname@example.org
> Subject: Proposal to create a branch for contrib project Zebra
> Thanks to the PIG team, The first version of contrib project Zebra
> (PIG-833) is committed to PIG trunk.
> In short, Zebra is a table storage layer built for use in PIG and
> Hadoop applications.
> While we are stabilizing current version V1 in the trunk, we plan to
> more new features to it. We would like to create an svn branch for the
> new features. We will be responsible for managing zebra in PIG trunk
> in the new branch. We will merge the branch when it is ready. We
> the changes to affect only 'contrib/zebra' directory.
> As a regular contributor to Hadoop, I will be the initial committer
> Zebra. As more patches are contributed by other Zebra developers,
> might be more commiters added through normal Hadoop/Apache procedure.
> I would like to create a branch called 'zebra-v2' with approval from