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

Bruce Perens bruce at perens.com
Sun Aug 25 19:59:11 UTC 2019


On Sun, Aug 25, 2019 at 12:38 PM Pamela Chestek <pamela at chesteklegal.com>
wrote:

>
> On 8/25/19 10:16 AM, Henrik Ingo wrote:
>
> > 2. I for one certainly wish that copyright legislation was more
> > friendly to duffers (I don't know what that word means, really...) and
> > less biased to favor big corporations who use every opportunity to
> > maximize their powers. But I don't see how any of this is Van's fault.
>

We went to some trouble to make Open Source friendly to duffers. Van's
"fault" is that he wants to break that for his license AND keep the result
within the Open Source brand. One or the other, please. I am also finding
that the extreme AGPL interpretations are not useful and are mostly
diversion from considering the CAL as we should.

(Maybe that's not a realistic hypothetical, I don't know - does everything
> have Javascript?)


A Wordpress module has the potential to provide PHP, HTML, Javascript, CSS.
Although it is modular, all of the PHP pieces are interpreted together as
one program. There can be use of Javascript, or not, but everything you are
seeing is the result of a PHP program creating an ephemeral HTML document.

There is also some question in my mind regarding who created the combined
work. I tend to view the combination happening when the module developer
creates instructions that cause that combination, not when the naive user
executes those instructions. The person who set the bomb is responsible for
its explosion, not the person who tread upon the trigger.

My point is this is well beyond the AGPL. For the AGPL, two more things
> have to happen before I have to provide the source code, I have to have
> modified the code and a user has to be able to interact with the program.
> For those who think that the AGPL is too far, or the outermost appropriate
> reach for copyleft, the CAL is beyond that.


Concur.

    Thanks

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


More information about the License-review mailing list