www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shane Curcuru <...@shanecurcuru.org>
Subject Re: Replacing CLA with DCO+ALv2
Date Wed, 25 Oct 2017 23:53:17 GMT
What specific purpose would changing our long-held incoming licensing
scheme fulfill?

Until we have a specific reason, and a thorough legal review, I'd be -1
from my perspective on changing any of our CLA process.


- Shane

Roman Shaposhnik wrote on 10/23/17 7:32 PM:
> Hi!
> my understanding has always been that while CLAs may be a bit
> cumbersome they are are basically the most robust mechanism
> for taking care of IP provenance. That's why ASF still uses them.
> This thinking was challenged today by a recent example of Chef
> moving from a CLA model to a DCO based one for an overall
> ALv2 licensed project.
> Here are the details:
>     https://blog.chef.io/2016/09/19/introducing-developer-certificate-of-origin/
> but the punch line is this (and I quote): "However, the DCO in conjunction
> with the Apache License may be considered an alternate CLA"
> Has the thinking around this somehow shifted? Is Chef alone in thinking
> that DCO + ALv2 gives you all you need from a CLA?
> Personally I still feel that CLA is justified (even if it is a bit clunky to
> administer) but at the same time I'd love to know if somebody really
> took the time to do this kind of risk/benefit analysis lately.
> Thanks,
> Roman.

To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org

View raw message