[License-review] For Approval: The Cryptographic Autonomy License

VanL van.lindberg at gmail.com
Sun Apr 28 14:50:34 UTC 2019

Hello Pam,

Thanks for the questions and comments - I'll respond to all of them, but I
will take some out of order as some take either more thought or more

On Sat, Apr 27, 2019 at 9:38 AM Pamela Chestek <pamela at chesteklegal.com>

> On 4/23/19 6:18 PM, VanL wrote:
> > In this case, my client identified that it was in their business
> > interest to have a strong network copyleft license that was maximally
> > respecting of user freedom.
> Any software that replicates APIs (e.g., Dalvik), even if entirely
> written from scratch, would have to be offered under the CAL. Is that
> your intention?

Yes, that is correct in general - although note that reimplementations of
an API (like Dalvik) could be offered under a Compatible Open Source
License. So in a hypothetical scenario where Java were available under the
CAL, Google's Apache-licensed Dalvik would be compliant.

> I do NOT read this license as not having any copyleft effect on software
> that simply uses APIs. Is that correct? If my reading is incorrect, can
> you walk me through it?

That is correct. Barring constructed hypotheticals, consuming an API would
not have any licensing implications.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensource.org/pipermail/license-review_lists.opensource.org/attachments/20190428/6700ca3b/attachment.html>

More information about the License-review mailing list