incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William A. Rowe Jr." <>
Subject Re: [VOTE] Move Chukwa to incubator
Date Tue, 22 Jun 2010 07:47:00 GMT
On 6/22/2010 2:42 AM, ant elder wrote:
> On Mon, Jun 21, 2010 at 8:09 PM, William A. Rowe Jr.
> <> wrote:
>> On 6/21/2010 1:31 PM, Owen O'Malley wrote:
>>> On Jun 21, 2010, at 11:06 AM, Mattmann, Chris A (388J) wrote:
>>>> Chukwa has been around for a while now and from my (albeit limited)
>>>> impression, pretty successful. What's the rationale for going the
>>>> Incubator route rather than putting up a Board TLP resolution? Just
>>>> wanted to check, thanks guys!
>>> The problem is that none of the Chukwa PMC members have been on any
>>> Apache PMCs before. My belief is that having training wheels for a bit
>>> would be a good thing.
>> And the podling's committee itself seeks the extra guidance as they become
>> a self-managing committee, so the mentors all agreed with this proposal.
>> If anything, it makes checking off the graduation matrix much simpler as
>> they are already committers, we already have the IP vetting when the code
>> came into Hadoop.  We should obviously re-review the grants and trademark
>> assignments during incubation.
> I'm not totally convinced by that reasoning, wouldn't it be simpler to
> just go directly to TLP and have those listed here as mentors agree to
> help out by being on the initial PMC?
> If it does incubate what would be delaying its graduation? Its already
> got everything we list in the incubator docs - diverse committers,
> done several releases etc.
> The current proposal doesn't use the incubator naming for the mailing
> lists and svn location, from past discussions here it should really be
> using the incubator naming unless its a very special case. Is this a
> special case?

If that is the desire of the incubator, to refer this project to a TLP,
I'm happy to serve on that pmc for the first 6 mos - 1 yr, whatever it
takes for the project to become comfortable with all of the aspects.

Note these committers were not hadoop pmc members, in fact it was this
disjoint arrangement that pointed out the need to fork this subproject
into its own entity, under the direction of its own community.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message