o flesh out the proposal, address intial concerns,
and figure out whether it has a chance of being accepted. The
author's role is to build consensus, and gather dissenting opinions.
Following this discussion the author should draft a HEP proposal
following the HEP template. The proposal shoul
eing accepted. The
author's role is to build consensus, and gather dissenting opinions.
Following this discussion the author should draft a HEP proposal
following the HEP template. The proposal should accurately reflect and
address feedback and dissenting opinions. For example, flesh out
dea is
HEP-able by sending mail to the general list. If the scope of the
idea is limited to a specific project the discussion may happen on the
project-specific list or jira. This gives the author a chance to
flesh out the proposal, address initial concerns, and figure out
whether it has a chance of
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,
e build system to use maven).
>
>HEP Workflow
>
>
>The author of a HEP should first try to determine if their idea is
>HEP-able by sending mail to the general list. If the scope of the
>idea is limited to a specific project the discussion may
ts backwards compatibility (eg modifies released
>> public APIs in an incompatible way).
>>
>> - The feature requires that an existing component be substantially
>> re-designed (eg NameNode modified to use Bookkeeper).
>>
>> - The implementation impact
On Wed, Jul 14, 2010 at 11:57 AM, Doug Cutting 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
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 t
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 wrote:
> Eli,
>
> Great work. I l
On Wed, Jul 14, 2010 at 6:23 PM, Aaron Kimball 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 exampl
ight 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 wrote:
>
>> Eli,
>>
>> Great work.
On 07/14/2010 11:41 PM, Eli Collins wrote:
I was assuming HEPs would just be placed in the public domain, period.
Like design docs posted on jira they're just text posted to a mailing
list, not sure checking them into svn needs to require they have an
alternate license. Something I'm missing?
I
12 matches
Mail list logo
