[License-review] For approval: The Cryptographic Autonomy License (Beta 4)

[Henrik Ingo]

On Fri, Dec 13, 2019 at 12:32 AM Josh Berkus <josh at berkus.org> wrote:

> People build applications in layers.  Imagine the sofware I'm copying is
> a CAL-licensed database, but what I'm building is some node.js-based
> end-user app.
>

Just to interject on this specific point: This is a great and relevant
example.

And this is exactly a situation where IMHO opinion the approach in CAL is a
good one. You have an obligation to fulfill your obligations under CAL, but
the CAL doesn't mandate you to implement some particular API in your
node.js app. You can choose to use a more manual export procedure if you
wish.

The alternative, that you would be required to implement some specific
feature in your node.js code, which isn't even CAL licensed, would IMO be
much more problematic. And questionable from an OSD point of view, so I'm
not sure it's even an option.

henrik

-- 
henrik.ingo at avoinelama.fi
+358-40-5697354        skype: henrik.ingo            irc: hingo
www.openlife.cc

My LinkedIn profile: http://fi.linkedin.com/pub/henrik-ingo/3/232/8a7
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensource.org/pipermail/license-review_lists.opensource.org/attachments/20191213/2580f82e/attachment.html>