🔑Developer Switches Default License to EUPL-1.2
Strong Copyleft Licenses Are the New Norm
TL;DR
A developer is now defaulting to EUPL-1.2 for new projects, arguing it closes the 'SaaS loophole' and requires reciprocal licensing. This shift could impact how open-source projects are licensed in the future.
A developer has switched their default license from permissive to EUPL-1.2, a strong copyleft license that requires reciprocal licensing regardless of distribution method. This move is significant for developers who prioritize open-source values over permissive licensing. The EUPL-1.2 license closes the 'SaaS loophole' and ensures that derivative works must also be open-source. The developer has published several projects under EUPL-1.2, including reticulum-js and dacar. This change could influence the licensing of future open-source projects, especially in Europe.
Key Points
Developer has three distinct eras of software licensing over 28 years.
Midgard was licensed under LGPLv2, a strong copyleft license.
Example website with Midgard was X11 licensed, a permissive license.
Developer switched to MIT license around 2011 for JavaScript projects.
EUPL-1.2 is OSI-approved and requires reciprocal licensing for all distributions.
Why It Matters
The shift to EUPL-1.2 impacts developers who prioritize strong copyleft licenses. Projects like reticulum-js and dacar now require derivative works to be open-source, ensuring broader adoption of open-source values. This move challenges the dominance of permissive licenses and could influence future licensing decisions in the open-source community.
Frequently Asked Questions
Why does this matter?
The shift to EUPL-1.2 impacts developers who prioritize strong copyleft licenses. Projects like reticulum-js and dacar now require derivative works to be open-source, ensuring broader adoption of open-source values. This move challenges the dominance of permissive licenses and could influence future licensing decisions in the open-source community.
What happened?
A developer is now defaulting to EUPL-1.2 for new projects, arguing it closes the 'SaaS loophole' and requires reciprocal licensing. This shift could impact how open-source projects are licensed in the future.
Comments
Be the first to comment
Enjoyed this article?
Get it daily. 7am. Free. Reads in 5 minutes.
Join 3,461 builders reading daily.