I Changed My License
Source Entity
Hacker News
A software developer reflects on 28 years of licensing, transitioning from LGPLv2 and MIT licenses to the EUPL 1.2. The shift highlights evolving philosophies in open-source distribution and legal protection for software creators.
The Evolution of Open-Source Licensing
After 28 years of active software development, the transition to the European Union Public License (EUPL) 1.2 represents a significant milestone in how developers manage intellectual property. The author’s journey reflects a broader shift in the tech industry, moving from the rigid structures of early copyleft movements toward more nuanced, legally robust frameworks designed for the modern digital ecosystem.
The Era of LGPL and Web Frameworks
In the early stages of the author's career, Midgard was distributed under the LGPLv2. During this period, the open-source landscape was less fragmented, and 'weak copyleft' licenses were the standard for web frameworks. The objective was to encourage adoption while maintaining a level of reciprocal contribution, a philosophy that defined the late 1990s and early 2000s approach to open-source software development.
The Rise of Permissive Licensing
By 2011, the focus shifted toward the MIT license as the author engaged deeply with the JavaScript and NPM ecosystems. The MIT license, characterized by its 'do whatever you like' simplicity, became the industry gold standard for rapid interoperability. This era prioritized frictionless integration, reflecting the needs of a fast-paced web development community that favored minimal legal overhead over strict copyleft enforcement.
Why EUPL 1.2 Matters
The recent decision to standardize on the EUPL 1.2 indicates a maturing perspective on software distribution. Unlike the MIT license, the EUPL 1.2 provides specific legal protections tailored to the European legal environment, ensuring that the software remains open while offering clearer guidelines for liability and jurisdiction. This transition suggests that as software projects reach greater maturity, developers are increasingly prioritizing legal clarity and regional compatibility over pure simplicity.
Broader Implications and Future Trends
The trajectory from LGPL to MIT and finally to EUPL 1.2 mirrors the evolution of the software industry itself—from niche frameworks to global, interconnected systems. As developers face increasing scrutiny regarding supply chain security and legal accountability, we can expect a trend toward more sophisticated licensing models that balance the 'open' ethos with necessary legal safeguards.
Conclusion
By documenting this 28-year transition, the author provides a valuable case study in how personal philosophy toward code ownership evolves alongside the industry. The move to EUPL 1.2 is not merely a technical change but a strategic decision to ensure the long-term sustainability and legal integrity of their software contributions in a complex global market.