Mailing-List: contact general-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@hadoop.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1278)
Subject: Re: [DISCUSS] Spin out MR,
 HDFS and YARN as their own TLPs and disband Hadoop umbrella project
From: Eric Baldeschwieler <eric14@hortonworks.com>
In-Reply-To: 
 <CALEq1Z_CP5yY5sJBYaCoKARN98wgeUURcbEDUHO7MD+ps3WctA@mail.gmail.com>
Date: Fri, 31 Aug 2012 15:43:07 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <DC46198F-708F-4220-8D9D-9D116EEBC9F8@hortonworks.com>
References: <0C112F45-3130-4093-B0F2-2D1F02B8C84C@jpl.nasa.gov>
 <897DECF2-B806-469D-BC78-88D1A63583A7@hortonworks.com>
 <F86CEB15-8ECE-4BF7-A36F-8FFFAF364BBB@jpl.nasa.gov>
 <CADY20s4gB2u3+TOb9nebb87CJsY4O_2AEZW5QR3fPPbPnLE6AQ@mail.gmail.com>
 <20120829234728.GI32535@linspire.com>
 <CADY20s4r_s9fkP7HHCAuWACxD5EALX=XwC379c7Dn1cvnb77nA@mail.gmail.com>
 <2D356EF8-C7E2-4A3C-85F1-19C2B12D69FA@hortonworks.com>
 <CAGiCgd3fRCyocGFML7RGHiFCRBVz4ELZ9Rx2c1t5zW9KhBET4g@mail.gmail.com>
 <CALEq1Z8wFSm6EzB-iqusTa8as5bDSsAMBpg6wyOxDGEeWa_4Gw@mail.gmail.com>
 <CAGiCgd2hpNMttKjM3bgCs4iTyJQ1=8Gz25q3YQrHhkLZkc4JhA@mail.gmail.com>
 <CALEq1Z_CP5yY5sJBYaCoKARN98wgeUURcbEDUHO7MD+ps3WctA@mail.gmail.com>
To: general@hadoop.apache.org

I'd be fascinated to hear more from folks who have lead other projects =
at Apache how Hadoop's (and Lucene's, same DNA) committer management =
process compares and some good and bad lessons learned from those =
projects.  Chris M has mentioned his experience from other projects.  =
Can others comment?

Many projects do seem to have Emeriti lists / processes.  How do people =
feel about that?

How does the committer list size of Hadoop compare to other major Apache =
projects?

Other lessons learned?

On Aug 31, 2012, at 1:44 PM, Doug Cutting wrote:

> On Fri, Aug 31, 2012 at 12:00 PM, Inder.dev Java =
<java.inder@gmail.com> wrote:
>> How often you call for  Emeriti lists.
>> Otherwise , if list is simply growing, then people may surprise like =
this.
>> And also some people(Eli Collins) showed concerns about growing lists =
above
>> right. But in reality all that people may not be active and not =
looking to
>> project from long. Having them in active list will not help to Hadoop
>> right. If they really want to active and help to project, they can =
regain
>> at that time. Otherwise people may think to add new people, as list =
already
>> big like above. no?
>=20
> Keeping people who are no longer active on the committer list
> shouldn't cause problems.  No quorum is required for votes.  Emeritus
> is used for folks who no longer follow the project at all.  Some
> committers may no longer be contributing code regularly but they
> should still be reading the developer mailing lists and may vote.
> More active contributors primarily determine the current technical
> direction of the project by making contributions.
>=20
> Doug