FWIW, I have a CLA on file.
See the full list here
http://people.apache.org/~jim/committers.html

Guillaume Nodet

Jeremy Hughes wrote:

Now that there are some more folks are getting interested in Woden,
and Guillame has posted a patch - thanks, and Venkat seem keen to also
:-) ... it got me thinking. What do we as committers of patches need
to do to ensure there are no IP issues with code contributed as a
patch by someone who hasn't submitted an ICLA to the ASF. OK, so when
you attach a patch to a JIRA you "Grant license to ASF for inclusion
in ASF works (as per the Apache Software License §5)". However this
isn't as strong as the ICLA. In fact come to think of it I don't know
where the list of ICLAs for non-committers is kept? Dims do you know?

The Xerces project has further instructions [1] where you give the
name of your employer, whether you authored the code, whether you have
the right to grant the copyright, whether your employer has any rights
to the code (thru employment contract), third party license
restrictions.

The DB project FAQ [2] says "Contributors who are not committers are
in a somewhat fuzzy spot." :-) ... "if you make a large contribution,
or many contributions, a DB committer will likely ask you to submit an
ICLA"

I favour the DB project approach - I'm guessing the Xerces charter was
written before the option on the JIRA "attach a file" page. We could
add this to the Woden site.

Dims, is there anything more official from the board on this? is the
DB approach sufficient? Is there a list of people with email ids who
have ICLAs submitted to the ASF - a list that any committer can
access?

Many thanks,
Jeremy

[1] http://xerces.apache.org/xerces2-j/charter.html §7.3
[2] http://db.apache.org/derby/faq.html#derby_icla

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to