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

VanL van.lindberg at gmail.com
Thu Dec 5 16:36:06 UTC 2019


Hi Bruce,

On Thu, Dec 5, 2019 at 10:13 AM Bruce Perens via License-review <
license-review at lists.opensource.org> wrote:

> Why would a clean-room procedure be necessary? It's Open Source software,
> and everyone has the right to read it.
>

You are right, everyone has the right to read the software. They actually
have a lot more rights than that; the license grant is in section 2 of the
CAL.

As for the characterization as a clean room procedure, you described a
bunch of steps, which I attempted to summarize as a clean room procedure. I
can't see why all the different steps and caveats described would be
necessary otherwise. But I am not going to comment on the proposed
effectiveness of some steps presented without context on an internet
mailing list. Thus: could someone create a procedure to [accomplish
whatever it was that you were trying to describe accomplishing]?
Hypothetically yes. Practically, it all depends, so it is impossible to say
based upon a made-up scenario.


> Let's make sure I have this straight. You can't write other Open Source
> software that is compatible with Holochain, under any license but the CAL,
> because only software under the CAL license has a license to the patents?
>

You asked if there was something else other than the CAL that would help
protect the Holochain commons. The answer to that is yes, from an entirely
unsurprising application of patent law. I  also noted that means for that
patent to be licensed to others was also built into the CAL, and so it ends
up strengthening the commons rather than weakening it.

Perhaps I am reading too much into what you were saying. I have tried to be
straightforward, but this appears to be attempts to play "gotcha," rather
than an inquiry into the substantive changes in Beta 4.

Thanks,
Van
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensource.org/pipermail/license-review_lists.opensource.org/attachments/20191205/24ed5208/attachment.html>


More information about the License-review mailing list