hadoop-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mattmann, Chris A (388J)" <chris.a.mattm...@jpl.nasa.gov>
Subject Re: [VOTE] Abandon mrunit MapReduce contrib
Date Fri, 11 Feb 2011 19:57:41 GMT
Awesome Patrick, we'd probably need one more active mentor. Any takers?

After we get that, then we cook up a proposal on the Incubator wiki here [1], and follow the
process here [2] to get started...

Cheers,
Chris

[1] http://wiki.apache.org/incubator/MRUnitProposal
[2] http://incubator.apache.org/guides/proposal.html

On Feb 11, 2011, at 11:52 AM, Patrick Hunt wrote:

> On Fri, Feb 11, 2011 at 9:44 AM, Mattmann, Chris A (388J)
> <chris.a.mattmann@jpl.nasa.gov> wrote:
>> Guys, BTW, if you need help or a mentor in Apache Incubator-ville for MRUnit, I would
be happy to help.
> 
> I was going to suggest the same thing (mrunit to incubator). I would
> also be happy to be a mentor.
> 
> Patrick
> 
>> 
>> On Feb 11, 2011, at 9:04 AM, Eric Sammer wrote:
>> 
>>> On Fri, Feb 11, 2011 at 11:48 AM, Owen O'Malley <omalley@apache.org> wrote:
>>> 
>>>> On Feb 11, 2011, at 8:02 AM, Eric Sammer wrote:
>>>> 
>>>> - allow mrunit to have its own release cycle. This is, I think, the most
>>>>> 
>>>> 
>>>> important.
>>>>> 
>>>> 
>>>> If you submit your work to Apache we can evaluate it for inclusion in the
>>>> 0.20.100 branch to get your changes released in a timely manner.
>>> 
>>> 
>>> I'm thinking in general (beyond the next immediate release). Independent of
>>> where mrunit goes, I think it should leave the contrib tree to facilitate
>>> light weight releases (the dependency on Hadoop proper is a public facing
>>> API - a pure client). I think most projects could benefit from this with the
>>> exception of things that are tightly coupled to Hadoop releases or touch
>>> non-public APIs.
>>> 
>>> 
>>>> I would actually prefer to move it to Extras or Incubator and leave this
>>>>> within the ASF.
>>>>> 
>>>> 
>>>> Extras is **NOT** inside of the ASF. Extras is a source hosting system for
>>>> non-Apache projects that are related to Apache projects.
>>> 
>>> 
>>> Got it. Thanks for correcting me. I only mentioned it because someone
>>> suggested it to me initially.
>>> 
>>> 
>>>> Right now, I picked github because of the ability to easily
>>>> collaborate with others (and to use git).
>>>> 
>>> 
>>> I agree that it is unfortunate that Apache doesn't yet support read-write
>>>> git access. However, you'll find that building a community is easier at
>>>> Apache than at github.
>>>> 
>>> 
>>>> -- Owen
>>>> 
>>> 
>>> 
>>> 
>>> --
>>> Eric Sammer
>>> twitter: esammer
>>> data: www.cloudera.com
>> 
>> 
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Chris Mattmann, Ph.D.
>> Senior Computer Scientist
>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>> Office: 171-266B, Mailstop: 171-246
>> Email: chris.a.mattmann@nasa.gov
>> WWW:   http://sunset.usc.edu/~mattmann/
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Adjunct Assistant Professor, Computer Science Department
>> University of Southern California, Los Angeles, CA 90089 USA
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 
>> 


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


Mime
View raw message