Re: Clarification about ICLA for non-committers

2025-07-01 Thread PJ Fanning
I raised https://issues.apache.org/jira/browse/LEGAL-704 On 2025/06/30 23:37:24 Justin Mclean wrote: > Hi, > > > Would it be possible to adjust the 1st paragraph to reduce the ambiguity? > > The contributor of the code or documentation is the copyright holder > > and the fact that the code is com

Re: Clarification about ICLA for non-committers

2025-06-30 Thread Justin Mclean
Hi, > Would it be possible to adjust the 1st paragraph to reduce the ambiguity? > The contributor of the code or documentation is the copyright holder > and the fact that the code is committed by someone who has signed a > CLA does not alter this. That’s not a page owned by the incubator. Perhaps

Re: Clarification about ICLA for non-committers

2025-06-30 Thread PJ Fanning
I'm happy with the interpretation that CLAs are only required by committers. The docs [1] do say this though: All contributors of ideas, code, or documentation to any Apache projects must complete, sign, and submit via email an Individual Contributor License Agreement (ICLA). The purpose of thi

Re: Clarification about ICLA for non-committers

2025-06-30 Thread Justin Mclean
Hi, > I don't think that it is usually necessary to ask contributors to file an > ICLA in order to send a patch. Correct, it is not required, as someone who has signed an ICLA (i.e a committer) will merge the patch. > If I understand correctly such ICLA is required only for new committers and >

Clarification about ICLA for non-committers

2025-06-30 Thread Enrico Olivelli
Hello, I was discussing with some members (in particular PG Fanning) in the Openservless podling community about the requirements for contributors to file an ICLA in order to submit patches to an Apache Project on Github. I don't think that it is usually necessary to ask contributors to file an IC