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

[Henrik Ingo]

On Thu, Dec 12, 2019 at 11:30 PM Nigel T <nigel.2048 at gmail.com> wrote:

> On Thu, Dec 12, 2019 at 3:17 PM VanL <van.lindberg at gmail.com> wrote:
>
>> The hypothetical then expanded again to user accounts, memberships,
>> badges, user content, etc - the whole WordPress ecosystem. I can't say that
>> the whole WordPress ecosystem would be able to easily comply. But you
>> yourself identify that the information is stored in the database or the
>> filesystem, and it is accessible, so compliance is possible. I would also
>> note plugins like WP-all-export.
>>
>
> These specifics were provided to refute Henrik's assertion that WordPress
> has been 4.2 compliant for years.  These are not "expanded hypotheticals"
> but counter-examples.
>
>
Just to be clear, I of course agree that there can exist software that
would not allow easy export of user data in a CAL compliant manner. But I
did feel compelled to point out that the initial Wordpress examples given
by you and Bruce are in fact compliant! Only on your third attempt did you
manage to present a sufficiently complicated scenario that it plausibly
might not be compliant out of the box. Yet even then Van pointed out that
there could exist and a user could easily install a plugin specifically
designed to export all data of a given user, regardless of what arbitrary
set of other plugins you had activated.

Further, I have also pointed out that if we were talking about a blogging
software that actually was licensed under CAL, it would of course be even
more likely to support such export functionality than Wordpress.

So I think this discussion - which raised a very valid question - has shown
that in practice the current language in CAL will work well and while
problematic cases can be constructed, they seem to be the exception and
users should simply avoid such software, should they actually exist in the
future.

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/347f0311/attachment.html>