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

[Bruce Perens]

On Fri, Dec 6, 2019 at 2:14 PM Bruce Perens <bruce at perens.com> wrote:

> The problem is that to assure that the data terms are applied to the
>> entire network, they _must_ assert their patents against any interoperable
>> Open Source software that is not licensed under those terms.
>>
>
And this seems to be a fundamental flaw in any action-required license
where it is essential that the action *always *be followed. The requirer of
the action must act to prohibit any Open Source software that isn't under
those terms.

In contrast, the GPL requires source-code distribution, but it is not a
problem if you do not distribute the source for an independent, but
interoperable, program. It is not essential that the action be followed
every time.

This is why the needs of holochain are inseparably attached to CAL, and
must be considered during the approval process. Holochain requires that the
data-return action *always* be followed to preserve user data rights, a
fundamental feature of the network. This required globally-essential action
is a new feature, not enacted in any currently-approved Open Source
license, and IMO too dangerous to approve.

    Thanks

    Bruce
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensource.org/pipermail/license-review_lists.opensource.org/attachments/20191206/bd5671f5/attachment.html>