hadoop-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eli Collins <...@cloudera.com>
Subject Re: HEP proposal
Date Thu, 15 Jul 2010 06:42:09 GMT
Yup.

"As updates are necessary, the HEP author can check
in new versions if they have commit permissions, or can email new HEP
versions to the editor for committing."

Thanks,
Eli

On Wed, Jul 14, 2010 at 10:36 PM, Dhruba Borthakur <dhruba@gmail.com> wrote:
> on a related note, since a HEP-initiator might not be a apache committer,
> does it mean that it is the responsibility of the editor/champion to check
> versions of the HEP proposal into svn?
>
> thanks,
> dhruba
>
> On Wed, Jul 14, 2010 at 6:23 PM, Aaron Kimball <aaron@cloudera.com> wrote:
>
>> Eli,
>>
>> Great work. I like where this is going.
>>
>> Here's something that I think might be problematic:
>>
>> 3. Copyright/public domain -- Each HEP must either be explicitly
>> labelled as placed in the public domain (see this HEP as an example).
>>
>>
>> "must either be placed in the public domain, or..?" I assume the
>> alternative
>> is an open source copyright license? You should state what this is. PEP's
>> alternative is "licensed under the Open Publication License."  (
>> http://www.opencontent.org/openpub/) Is that your intent?
>>
>> Upon acceptance of a PEP, the PEP workflow states that it should be checked
>> into svn. Are we planning to host accepted HEPs in the Hadoop svn? If so,
>> we
>> should specify that non-public-domain HEPs should be placed under a license
>> listed on http://www.apache.org/legal/resolved.html. The Open Publication
>> License isn't listed there. Nor are the GFDL and other documentation
>> licenses (presumably not because they're not specifically allowed, but
>> because Apache deals with code more than documentation). Note that
>> CC/Attribution/Share-Alike is allowed. You may want to recommend that one?
>>
>> - Aaron
>>
>>
>> On Wed, Jul 14, 2010 at 3:00 PM, Eli Collins <eli@cloudera.com> wrote:
>>
>> > On Wed, Jul 14, 2010 at 11:57 AM, Doug Cutting <cutting@apache.org>
>> wrote:
>> >
>> > > On 07/14/2010 10:46 AM, Eli Collins wrote:
>> > >
>> > >> 5. How the set of editors is selected?
>> > >>>   "The editors are apointed and removed by the PMC informally,
>> similar
>> > to
>> > >>>   how the Apache Board appoints shepherds to projects."
>> > >>> This needs a reference. How does Apache Board appoints shepherds?
>> > >>>
>> > >>
>> > >> Good question, anyone know? Since it's informal I imagine shepherds
>> > >> volunteer. The editors could be a subset of the PMC that either
>> > >> volunteers or is rotated periodically.
>> > >>
>> > >
>> > > Shepherds are assigned randomly by the chair 48 hours before each
>> > meeting.
>> > >  Perhaps a better analogy for an editor is an Incubator Champion?
>> > >
>> > >
>> > >
>> >
>> http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Champion
>> > >
>> > > Champions are volunteers.  So, rather than assigning an editor, a HEP
>> > might
>> > > ask for one to volunteer.  Any PMC member might volunteer.
>> > >
>> >
>> > That sounds reasonable. Having a PMC member volunteer will likely result
>> in
>> > someone who has more expertise in the area and will perhaps be more
>> > responsive.
>> >
>> > Thanks,
>> > Eli
>> >
>>
>
>
>
> --
> Connect to me at http://www.facebook.com/dhruba
>

Mime
View raw message