I strongly favor inclusion of an anti-tivoization clause. Hardware matters. In fact, (maybe if I recall right, it's already there), copyleft-next should be usable for free/open hardware too ideally.

Cheers, Aaron

On 06/23/2015 08:29 AM, Richard Fontana wrote:

On Tue, Jun 23, 2015 at 03:56:34PM +0200, Matthieu Gautier wrote:

...

Hello all,

I'm a developer and, in my quest to the perfect free license, I've found the copyleft-next project. The copyleft-next license (the next 0.4.0 version) seems to fulfill what I'm looking for but I would like some confirmations.

The license I search should :

• Ensures my code (and its modification) will be free however it is used.
• Lets users choose how to use the code (even with proprietary code)

If fact, I would like some kind of AGPLv3 + LGPLv3.

The next 0.4.0 version of copyleft-next seems to have those properties :

• The section 3 provides the "Affero clause"
• The definition of "Enhancement" exclude the simple usage a my code

from the license. So a code using my library (import a python module in my case) should not have to be free.

• But it missing the anti-tivoization clause.

Am I right ?

Yes, I think so. The absence of an anti-TiVoization clause was deliberate. I continue to feel that if one wants an anti-TiVoization policy it is best to use GPLv3, though I haven't really thought about the issue in quite a while. At least two erstwhile contributors/commentators objected strongly to the noninclusion of such a provision.

...

One another question : when do you plan to release the 0.4.0 version ?

Real Soon Now™, especially if there is interest from at least one person. :)

Richard

---

copyleft-next mailing list copyleft-next@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/copyleft-next