Welp, I think Owen is probably the best judge here since he has seen them in 
Hadoop-ville, and since he probably is way more familiar with the code and its 
eventual PMC members than I am. I'll amend my VOTE then.

+1 to Incubation, with TLP-naming (in other words, option #2). I'll try and 
join the lists and help where I can too, cycles-willing :)

Cheers,
Chris



On 6/30/10 11:23 AM, "Owen O'Malley" <omal...@apache.org> wrote:

On Jun 30, 2010, at 10:51 AM, Mattmann, Chris A (388J) wrote:

> On 6/30/10 9:42 AM, "Eric Yang" <ey...@yahoo-inc.com> wrote:
>
> Original incubator proposal:
>
> http://wiki.apache.org/incubator/ChukwaProposal
>
> Vote put forward to incubator:
>
> 1. recommend TLP with guides to help the initial pmc,
> 2. accept incubating with tlp resource naming, but -incubating release
> naming
> 3. accept incubating requiring all incubator naming conventions,
> that might
> help the incubator simplify this decision.
>
> Result of the vote:
>
> Option 1) Ant Elder, Eric Yang, William A. Rowe Jr.
> Option 2) Ari Rabkin, Jerome Boulon, Chris Douglas, Greg Reddin
> Option 3) Bernd Fondermann
>
> Owen O'Malley +1 on proposal

Sorry, I meant to vote for option 2.  I think that it would be good to
have more visibility in before they become a TLP. They also need to
figure out how to add new committers to their project.

-- Owen

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org




++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.mattm...@jpl.nasa.gov
WWW:   http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Reply via email to