You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by Pablo Duboue <pa...@gmail.com> on 2024/04/02 10:11:25 UTC

CLA requirements

Hello,

Just double checking, we need a CLA for a contribution irrespective of its
size or complexity, right?

From: https://www.apache.org/licenses/contributor-agreements.html

> All contributors of ideas, code, or documentation to any Apache projects
must complete, sign, and submit via email an Individual Contributor License
Agreement (ICLA).

If the contributor does not have an ICLA in place (and does not have an
employer), then should I ask them to sign a ICLA and to set UIMA for the
"notify project" bit of it?

[If they say they have, then I just email secretary@a.o to confirm?]

Best regards.

P

Re: CLA requirements

Posted by Pablo Duboue <pa...@gmail.com>.
On Tue, Apr 2, 2024 at 10:59 AM Richard Eckart de Castilho <re...@apache.org>
wrote:

> Hi,
>
> > On 2. Apr 2024, at 16:40, Richard Eckart de Castilho <re...@apache.org>
> wrote:
> >
> > I'll see if I find somebody on Slack to maybe provide more insight into
> ICLA vs Section 5.
>
> So folks on the ASF Slack back both ;) Essentially it boils down to risk
> management I guess.
>
> So this are my thoughts:
>
> If we accept contributions under Section 5 / without ICLA, we are at a
> larger risk that the contribution may be contested. So we should not do
> this for significant contributions - but
> if somebody corrects a typo, fixes a trivial bug, etc. it might be
> acceptable risk.
>
> If possible, an ICLA should be requested.
>
> In particular it must be provided before anybody actually may become a
> committer.


Thanks!

If the GSoC gets awarded, I'll push for the contributor to sign a ICLA as
they will be writing a fair amount of new code.

My question came about from a pull request I received from a person
applying. That's just code refactoring and will fit well under Sec. 5.

Thanks again,

P

Re: CLA requirements

Posted by Richard Eckart de Castilho <re...@apache.org>.
Hi,

> On 2. Apr 2024, at 16:40, Richard Eckart de Castilho <re...@apache.org> wrote:
> 
> I'll see if I find somebody on Slack to maybe provide more insight into ICLA vs Section 5.

So folks on the ASF Slack back both ;) Essentially it boils down to risk management I guess.

So this are my thoughts:

If we accept contributions under Section 5 / without ICLA, we are at a larger risk that the contribution may be contested. So we should not do this for significant contributions - but
if somebody corrects a typo, fixes a trivial bug, etc. it might be acceptable risk.

If possible, an ICLA should be requested. 

In particular it must be provided before anybody actually may become a committer.

Cheers,

-- Richard

Re: CLA requirements

Posted by Richard Eckart de Castilho <re...@apache.org>.
Hi Pablo,

> On 2. Apr 2024, at 12:11, Pablo Duboue <pa...@gmail.com> wrote:
> 
> Just double checking, we need a CLA for a contribution irrespective of its
> size or complexity, right?
> 
> From: https://www.apache.org/licenses/contributor-agreements.html

That page says "All contributors of ideas, code, or documentation to any Apache projects must complete, sign, and submit via email an Individual Contributor License Agreement (ICLA)."

To be honest, I remember it a bit differently, namely that often small contributions would be incorporated even without an ICLA just following the provisions of the Apache License 2.0 Section 5 which regulates contributions and the ICLAs would only be enforced for larger, regular contributions and be a prerequisite for commit access.

Maybe the page was updated in the meantime or maybe I remember wrongly.

>> All contributors of ideas, code, or documentation to any Apache projects
> must complete, sign, and submit via email an Individual Contributor License
> Agreement (ICLA).
> 
> If the contributor does not have an ICLA in place (and does not have an
> employer), then should I ask them to sign a ICLA and to set UIMA for the
> "notify project" bit of it?

I have to admit that I may not have chased down ICLAs from occasional drive-by contributors and accepted small contributions under the provisions provided by Section 5 of the license.
My experience is that going through the extra effort for a minor contribution typically means
that there won't be a contribution.

That said, I think it is a good idea in particular for a GSOC participant to jump through all the hoops as GSOC is a non-casual exercise in participating in open source development and that should IMHO also include the bureaucracy.

I'll see if I find somebody on Slack to maybe provide more insight into ICLA vs Section 5.

Cheers,

-- Richard