Re: [DISCUSS] Spin out MR, HDFS and YARN as their own TLPs and disband Hadoop umbrella project

[Eric Baldeschwieler <er...@hortonworks.com>]

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 <ja...@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?
> 
> 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.
> 
> Doug