You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by robert burrell donkin <ro...@gmail.com> on 2006/03/19 13:26:04 UTC

[POLICY][DOC] IP clearance process refinements

A few observations from following the process as currently documented
and proposals for improvements:

1 this process can only be executed by a ASF member or officer with
incubator karma. this needs to be documented on the clearance form.

PROPOSAL: document this and add section on form so that it's clear who executed

do we need a name for this role?

2 there is no tie between grant.txt and the incubator IP clearance.
this makes oversight difficult.

PROPOSAL: the clearance form should include the official name for the
grant as recorded in grants.txt.

3 there is no indication the form which CLA's and CCLA's are relevant.
this makes oversight difficult.

PROPOSAL: the form should include official names (as listed in the
foundation documents) for those donating the code.

4 there is no tie to the actual donated software. this makes oversight
difficult.

PROPOSAL: the md5 for the donation should be listed on the form. the
repository URL where the actual donated is/will be checked in should
be listed.

should this be in the incubator repository or in the project?

5 the VOTE from the project receiving the code is unnecessary and
confusing. it serves no useful legal purpose and normal apache process
can handle objections when the code is committed.

PROPOSAL: scrap this requirement

i think that these proposals are uncontroversial (representing how the
process is expected to work) and so can be dealt with by lazy
consensus. so unless i hear any objections, i'll update the documents
in a day or two...

- robert

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


Re: [POLICY][DOC] IP clearance process refinements

Posted by robert burrell donkin <ro...@gmail.com>.
On 3/19/06, Dain Sundstrom <da...@iq80.com> wrote:
> On Mar 19, 2006, at 6:25 AM, robert burrell donkin wrote:
>
> > On 3/19/06, Leo Simons <ma...@leosimons.com> wrote:
> >> On Sun, Mar 19, 2006 at 12:26:04PM +0000, robert burrell donkin
> >> wrote:
> >
> > <snip>
> >
> >>> 3 there is no indication the form which CLA's and CCLA's are
> >>> relevant.
> >>> this makes oversight difficult.
> >>>
> >>> PROPOSAL: the form should include official names (as listed in the
> >>> foundation documents) for those donating the code.
> >>
> >> Hrmpf. Aren't official names supposed to be private?
> >
> > didn't know that
> >
> >> I think we have a
> >> map of "nickname" -> "official name" which is somewhere private. I
> >> think
> >> the rule should be that all non-official names should be
> >> registered in
> >> that mapping.
> >
> > anyone know where this lives?
>
> Do you mean this?
>
>   http://people.apache.org/~jim/committers.html

that's generated by a script. appears that jim fixes up any nick names
before it's entered into the original. therefore using the name in the
original should satisfy those who wish to use a nick name.

> >>> 5 the VOTE from the project receiving the code is unnecessary and
> >>> confusing. it serves no useful legal purpose and normal apache
> >>> process
> >>> can handle objections when the code is committed.
> >>>
> >>> PROPOSAL: scrap this requirement
> >>
> >> *shrug*. I like how it makes explicit that its a group decision
> >> (which
> >> also implies you don't go sue the individual that did the commit
> >> if there
> >> is ever a problem).
> >
> > the vote proved to be confusing in practice. the concensus seems to be
> > +0 'yes but only if it's legal'.
> >
> > the legal oversight is supposed to be provided by the incubator pmc
> > not the project where the code lands.
> >
> > this is probably a good reason why the donation should be initially
> > committed into the incubator repository. it can then be yanked by
> > anyone in incubator. alternatively, the code could be committed to a
> > private repository since it's only there for the records.
> >
> > AIUI the commit should be safe enough since the execution will be done
> > by an ASF official or member. processing a grant is an official ASF
> > operation and the work is done on behalf of the foundation.
> >
> > anyone who knows more like to jump in here?
>
> I personally think a vote is just good form.  Donations of entire cvs
> or svn trees require the assistance of infrastructure and I would
> hate to ask them to do something and then have the community
> ultimately reject the code.

i think that this can be handled by normal consensus building.
processing a software grant takes quite a lot of time and effort so
the member or officer will be convinced that the project wants the
code before starting out.

it's really the timing with regard to incubator pmc approval which
caused the confusion. the current process says that a formal vote must
be held prior to approval by the incubator pmc.

infrastructure shouldn't be involved until the code is signed off from
a legal perspective by the incubator pmc. if the grant involves
infrastructure then a VOTE will be required before the request is
actioned but infrastructure work shouldn't be actioned until after
legal sign off. so, really a second vote would be necessary in any
case.

seems cleaner to separate these issues:

1 preparation by member or officer
2 incubator legal signoff
3 hand over to project to be handled in the standard way. if
infrastructure needs to be involved a formal VOTE will be required to
action the work.

- robert

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


Re: [POLICY][DOC] IP clearance process refinements

Posted by Dain Sundstrom <da...@iq80.com>.
On Mar 19, 2006, at 6:25 AM, robert burrell donkin wrote:

> On 3/19/06, Leo Simons <ma...@leosimons.com> wrote:
>> On Sun, Mar 19, 2006 at 12:26:04PM +0000, robert burrell donkin  
>> wrote:
>
> <snip>
>
>>> 3 there is no indication the form which CLA's and CCLA's are  
>>> relevant.
>>> this makes oversight difficult.
>>>
>>> PROPOSAL: the form should include official names (as listed in the
>>> foundation documents) for those donating the code.
>>
>> Hrmpf. Aren't official names supposed to be private?
>
> didn't know that
>
>> I think we have a
>> map of "nickname" -> "official name" which is somewhere private. I  
>> think
>> the rule should be that all non-official names should be  
>> registered in
>> that mapping.
>
> anyone know where this lives?

Do you mean this?

  http://people.apache.org/~jim/committers.html

>>> should this be in the incubator repository or in the project?
>>
>> As long as the policy documents where it is, then it should be ok.  
>> I'd
>> vote for incubator repo.
>
> +1
>
> anyone care to suggest a suitable location in the incubator  
> repository?

+1 it would be nice to have a single location which contained all of  
the original untouched donations.

>>> 5 the VOTE from the project receiving the code is unnecessary and
>>> confusing. it serves no useful legal purpose and normal apache  
>>> process
>>> can handle objections when the code is committed.
>>>
>>> PROPOSAL: scrap this requirement
>>
>> *shrug*. I like how it makes explicit that its a group decision  
>> (which
>> also implies you don't go sue the individual that did the commit  
>> if there
>> is ever a problem).
>
> the vote proved to be confusing in practice. the concensus seems to be
> +0 'yes but only if it's legal'.
>
> the legal oversight is supposed to be provided by the incubator pmc
> not the project where the code lands.
>
> this is probably a good reason why the donation should be initially
> committed into the incubator repository. it can then be yanked by
> anyone in incubator. alternatively, the code could be committed to a
> private repository since it's only there for the records.
>
> AIUI the commit should be safe enough since the execution will be done
> by an ASF official or member. processing a grant is an official ASF
> operation and the work is done on behalf of the foundation.
>
> anyone who knows more like to jump in here?

I personally think a vote is just good form.  Donations of entire cvs  
or svn trees require the assistance of infrastructure and I would  
hate to ask them to do something and then have the community  
ultimately reject the code.

-dain

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


Re: [POLICY][DOC] IP clearance process refinements

Posted by robert burrell donkin <ro...@gmail.com>.
On 3/19/06, Leo Simons <ma...@leosimons.com> wrote:
> On Sun, Mar 19, 2006 at 12:26:04PM +0000, robert burrell donkin wrote:

<snip>

> > 3 there is no indication the form which CLA's and CCLA's are relevant.
> > this makes oversight difficult.
> >
> > PROPOSAL: the form should include official names (as listed in the
> > foundation documents) for those donating the code.
>
> Hrmpf. Aren't official names supposed to be private?

didn't know that

> I think we have a
> map of "nickname" -> "official name" which is somewhere private. I think
> the rule should be that all non-official names should be registered in
> that mapping.

anyone know where this lives?

> I think its kind-of cool the ASF allows you to use a pseudonym if you
> really want to.

sounds reasonable but this scenario did prove to be a problem.

so i think that we need some way to link into the official documents.
an email address would probably be good enough for individuals.

is there any reason not to include the official name for corporations?

> > 4 there is no tie to the actual donated software. this makes oversight
> > difficult.
> >
> > PROPOSAL: the md5 for the donation should be listed on the form. the
> > repository URL where the actual donated is/will be checked in should
> > be listed.
>
> +1. Or the sha1, I think that is now best practice :-)
>
> > should this be in the incubator repository or in the project?
>
> As long as the policy documents where it is, then it should be ok. I'd
> vote for incubator repo.

+1

anyone care to suggest a suitable location in the incubator repository?

> > 5 the VOTE from the project receiving the code is unnecessary and
> > confusing. it serves no useful legal purpose and normal apache process
> > can handle objections when the code is committed.
> >
> > PROPOSAL: scrap this requirement
>
> *shrug*. I like how it makes explicit that its a group decision (which
> also implies you don't go sue the individual that did the commit if there
> is ever a problem).

the vote proved to be confusing in practice. the concensus seems to be
+0 'yes but only if it's legal'.

the legal oversight is supposed to be provided by the incubator pmc
not the project where the code lands.

this is probably a good reason why the donation should be initially
committed into the incubator repository. it can then be yanked by
anyone in incubator. alternatively, the code could be committed to a
private repository since it's only there for the records.

AIUI the commit should be safe enough since the execution will be done
by an ASF official or member. processing a grant is an official ASF
operation and the work is done on behalf of the foundation.

anyone who knows more like to jump in here?

> > so unless i hear any objections, i'll update the documents
> > in a day or two...
>
> If you have more cycles available, you might want to look at the IP
> clearance we've set up for Harmony - its worked rather well and is
> probably about ready to be merged as appropriate (there's some stuff in
> there about "authorized contributors" which we probably don't want nor
> need in general) with the main incubator policies.

unlikely ATM i'm afraid. might be able to get back to this once JCL
1.1 is finally released.

perhaps we do need the "authorized contributors" recorded somewhere as
a model for the next time...

- robert

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


Re: [POLICY][DOC] IP clearance process refinements

Posted by Leo Simons <ma...@leosimons.com>.
On Sun, Mar 19, 2006 at 12:26:04PM +0000, robert burrell donkin wrote:
> A few observations from following the process as currently documented
> and proposals for improvements:
> 
> 1 this process can only be executed by a ASF member or officer with
> incubator karma. this needs to be documented on the clearance form.
> 
> PROPOSAL: document this and add section on form so that it's clear who executed

+1

> do we need a name for this role?

Don't think so. People just confuse those names (Re: "champion").

> 2 there is no tie between grant.txt and the incubator IP clearance.
> this makes oversight difficult.
> 
> PROPOSAL: the clearance form should include the official name for the
> grant as recorded in grants.txt.

+1.

> 3 there is no indication the form which CLA's and CCLA's are relevant.
> this makes oversight difficult.
> 
> PROPOSAL: the form should include official names (as listed in the
> foundation documents) for those donating the code.

Hrmpf. Aren't official names supposed to be private? I think we have a
map of "nickname" -> "official name" which is somewhere private. I think
the rule should be that all non-official names should be registered in
that mapping.

I think its kind-of cool the ASF allows you to use a pseudonym if you
really want to.

> 4 there is no tie to the actual donated software. this makes oversight
> difficult.
> 
> PROPOSAL: the md5 for the donation should be listed on the form. the
> repository URL where the actual donated is/will be checked in should
> be listed.

+1. Or the sha1, I think that is now best practice :-)

> should this be in the incubator repository or in the project?

As long as the policy documents where it is, then it should be ok. I'd
vote for incubator repo.

> 5 the VOTE from the project receiving the code is unnecessary and
> confusing. it serves no useful legal purpose and normal apache process
> can handle objections when the code is committed.
> 
> PROPOSAL: scrap this requirement

*shrug*. I like how it makes explicit that its a group decision (which
also implies you don't go sue the individual that did the commit if there
is ever a problem).

> i think that these proposals are uncontroversial (representing how the
> process is expected to work) and so can be dealt with by lazy
> consensus.

Yeah, I think that's official :-)

> so unless i hear any objections, i'll update the documents
> in a day or two...

If you have more cycles available, you might want to look at the IP
clearance we've set up for Harmony - its worked rather well and is
probably about ready to be merged as appropriate (there's some stuff in
there about "authorized contributors" which we probably don't want nor
need in general) with the main incubator policies.

cheers!

Leo, Out Of Cycles(tm)

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


Re: [POLICY][DOC] IP clearance process refinements

Posted by robert burrell donkin <ro...@gmail.com>.
On 3/19/06, Justin Erenkrantz <ju...@erenkrantz.com> wrote:
>
> On 3/19/06, robert burrell donkin <ro...@gmail.com> wrote:
> > sorry for the confusion: this is about the actual process of preparing
> > the paperwork required by the incubator not the receipt of the
> > software grant form. AIUI the receipt of the software grant form needs
> > an officer but an officer or a member can fill in the rest of the
> > paperwork required by the incubator before they can approve a grant.
>
> Well, anyone can fill out the form.  Then, an Officer can receive the
> form on behalf of the Foundation (the preferred recipient for all
> forms is the Secretary).  The Incubator PMC still needs to review the
> form to ensure it is up to our standards before the code donation can
> commence (i.e. that it is the right document, etc, etc.).
>
> The Officer receiving it is not ensuring the legitimacy of the
> document - they are just saying, "Yup.  Got it."  The Incubator PMC is
> responsible for confirming the content of the document and ensuring
> that it's "right."


it's the not the software grant form i was talking about: the incubator has
it's own form which needs to be filled in and committed into subversion
before the incubator pmc will sign off the grant. see
http://incubator.apache.org/ip-clearance/index.html.

the software grant form needs to be filled in by the donator and ack'd by an
officer (ideally jim). the incubator form needs to be filled in by either an
officer or a member and committed into subversion.

- robert

Re: [POLICY][DOC] IP clearance process refinements

Posted by Justin Erenkrantz <ju...@erenkrantz.com>.
On 3/19/06, robert burrell donkin <ro...@gmail.com> wrote:
> sorry for the confusion: this is about the actual process of preparing
> the paperwork required by the incubator not the receipt of the
> software grant form. AIUI the receipt of the software grant form needs
> an officer but an officer or a member can fill in the rest of the
> paperwork required by the incubator before they can approve a grant.

Well, anyone can fill out the form.  Then, an Officer can receive the
form on behalf of the Foundation (the preferred recipient for all
forms is the Secretary).  The Incubator PMC still needs to review the
form to ensure it is up to our standards before the code donation can
commence (i.e. that it is the right document, etc, etc.).

The Officer receiving it is not ensuring the legitimacy of the
document - they are just saying, "Yup.  Got it."  The Incubator PMC is
responsible for confirming the content of the document and ensuring
that it's "right."

HTH.  -- justin

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


Re: [POLICY][DOC] IP clearance process refinements

Posted by robert burrell donkin <ro...@gmail.com>.
On 3/19/06, Justin Erenkrantz <ju...@erenkrantz.com> wrote:
> On 3/19/06, robert burrell donkin <ro...@gmail.com> wrote:
> > A few observations from following the process as currently documented
> > and proposals for improvements:
> >
> > 1 this process can only be executed by a ASF member or officer with
> > incubator karma. this needs to be documented on the clearance form.
> >
> > PROPOSAL: document this and add section on form so that it's clear who executed
> >
> > do we need a name for this role?
>
> Only Officers - which includes every PMC Chair - can receive documents
> on behalf of the ASF.  Members can not.  Directors may or may not -
> depending upon the item being received.  So, the answer is "Officers".

sorry for the confusion: this is about the actual process of preparing
the paperwork required by the incubator not the receipt of the
software grant form. AIUI the receipt of the software grant form needs
an officer but an officer or a member can fill in the rest of the
paperwork required by the incubator before they can approve a grant.

- robert

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


Re: [POLICY][DOC] IP clearance process refinements

Posted by Justin Erenkrantz <ju...@erenkrantz.com>.
On 3/19/06, robert burrell donkin <ro...@gmail.com> wrote:
> A few observations from following the process as currently documented
> and proposals for improvements:
>
> 1 this process can only be executed by a ASF member or officer with
> incubator karma. this needs to be documented on the clearance form.
>
> PROPOSAL: document this and add section on form so that it's clear who executed
>
> do we need a name for this role?

Only Officers - which includes every PMC Chair - can receive documents
on behalf of the ASF.  Members can not.  Directors may or may not -
depending upon the item being received.  So, the answer is "Officers".
 -- justin

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