No right to relicense this project · Issue #327 · chardet/chardet · GitHub
Mark Pilgrim Demands Return to Original LGPL License for chardet Amid Licensing Controversy
In a dramatic turn of events within the open-source community, Mark Pilgrim, the original creator of the widely-used Python library chardet, has publicly challenged the project’s current maintainers over what he describes as an unauthorized and illegal license change. The dispute centers around the release of chardet 7.0.0, which was published under a different license than the one Pilgrim originally used when he authored the library.
The Heart of the Dispute
Mark Pilgrim, a respected figure in the software development world, is best known for his influential works such as “Dive Into Python” and the “Universal Character Encoding Detector.” His creation, chardet, has been a cornerstone in the Python ecosystem for detecting character encodings in text data. Over the years, the library has been maintained and improved by a community of contributors, leading to its widespread adoption.
However, Pilgrim has now raised serious concerns about the licensing of the latest version of the library. In a public statement, he emphasized that the maintainers of chardet have no legal right to “relicense” the project. According to Pilgrim, the original code was released under the LGPL (Lesser General Public License), a copyleft license that requires any modifications or derivative works to be distributed under the same terms. This ensures that the software remains free and open for all users.
The LGPL Violation
Pilgrim’s argument hinges on the principles of the LGPL. He asserts that the maintainers’ claim that chardet 7.0.0 is a “complete rewrite” is irrelevant. Even if the code has been significantly altered, the maintainers had extensive exposure to the original, licensed code, which means they cannot simply change the license without violating the terms of the LGPL. Pilgrim also dismissed the idea that using a “fancy code generator” grants the maintainers any additional rights to alter the licensing terms.
The controversy has sparked a broader discussion within the open-source community about the importance of adhering to licensing agreements. Pilgrim’s insistence that the project be reverted to its original LGPL license underscores the need for transparency and respect for the legal frameworks that govern open-source software.
Community Reaction
The open-source community has been quick to weigh in on the issue. Many developers have expressed support for Pilgrim’s stance, emphasizing the importance of maintaining the integrity of open-source licenses. Others have called for a thorough review of the changes made in chardet 7.0.0 to determine whether they truly constitute a “complete rewrite” or if they are, in fact, derivative works that must adhere to the LGPL.
The maintainers of chardet have yet to respond publicly to Pilgrim’s demands. However, the situation has already garnered significant attention, with many in the community calling for a resolution that respects the original licensing terms.
The Broader Implications
This dispute highlights the challenges that can arise in the maintenance and evolution of open-source projects. As software projects grow and change hands, it is crucial to ensure that the original licensing terms are respected. Failure to do so can lead to legal complications and erode trust within the community.
For developers and organizations that rely on open-source software, this incident serves as a reminder to carefully review the licensing terms of the projects they use. It also underscores the importance of clear communication and transparency when making significant changes to a project’s codebase or licensing.
Conclusion
Mark Pilgrim’s call for the reversion of chardet to its original LGPL license is a significant moment in the open-source community. It highlights the ongoing tension between the need for innovation and the importance of adhering to established legal frameworks. As the situation unfolds, it will be closely watched by developers, maintainers, and users alike, serving as a case study in the complexities of open-source licensing.
For now, the community awaits a response from the maintainers of chardet and hopes for a resolution that upholds the principles of open-source software. In the meantime, Pilgrim’s stance serves as a powerful reminder of the importance of respecting the rights and intentions of original creators in the world of open-source development.
Tags & Viral Phrases:
- Open-source licensing controversy
- Mark Pilgrim chardet dispute
- LGPL violation in software
- chardet 7.0.0 licensing issue
- Free Software success story
- Code licensing rights
- Open-source community reaction
- Software licensing legal battle
- chardet maintainers under fire
- Mark Pilgrim demands LGPL reversion
- Dive Into Python creator speaks out
- Universal Character Encoding Detector
- Open-source project licensing challenges
- Software licensing transparency
- chardet licensing terms debate
,




Leave a Reply
Want to join the discussion?Feel free to contribute!