Coding Agents and the Chardet Controversy: A Clean Room Implementation Debate

Over the past few months, coding agents-AI systems designed to write code-have demonstrated an impressive ability to create what can be loosely termed a "clean room" implementation of existing software. This technique involves reverse-engineering the functionality of a piece of software and then reimplementing it from scratch, often under a different license. The most famous historical example is Compaq’s 1982 creation of a clean-room clone of IBM's BIOS, where one team reverse-engineered the BIOS to create a specification, which was then handed to another team for a ground-up implementation.

Chardet: A Case Study in Licensing and Clean Room Implementation

The recent controversy surrounding the Python library chardet has brought this issue to the forefront. Chardet, originally created by Mark Pilgrim in 2006, was released under the LGPL (Lesser General Public License). After Pilgrim retired from public internet life in 2011, maintenance of chardet was taken over by others, notably Dan Blanchard, who has been responsible for every release since version 1.1 in July 2012.

The New Release: chardet 7.0.0

Two days ago, Dan released chardet 7.0.0, which includes the following note in the release notes:

Ground-up, MIT-licensed rewrite of chardet. Same package name, same public API, drop-in replacement for chardet 5.x/6.x. Just way faster and more accurate!

The Controversy

Yesterday, Mark Pilgrim opened an issue on the chardet GitHub repository titled "No right to relicense this project." In his post, he thanked the current maintainers and contributors but raised serious concerns about the relicensing:

First off, I would like to thank the current maintainers and everyone who has contributed to and improved this project over the years. Truly a Free Software success story.

However, it has been brought to my attention that, in the release 7.0.0, the maintainers claim to have the right to “relicense” the project. They have no such right; doing so is an explicit violation of the LGPL. Licensed code, when modified, must be released under the same LGPL license. Their claim that it is a “complete rewrite” is irrelevant, since they had ample exposure to the originally licensed code (i.e., this is not a “clean room” implementation). Adding a fancy code generator into the mix does not somehow grant them any additional rights.

Dan’s Response

Dan Blanchard responded with a lengthy comment addressing Mark's concerns. He argued that the new version of chardet was indeed a ground-up rewrite and that no direct copying of the original codebase occurred. He also emphasized that the use of AI tools to assist in the development process does not violate the spirit or letter of the LGPL, as the AI systems did not have access to the original source code during their operation.

Ethical and Legal Implications

This controversy highlights several important ethical and legal issues:

• Licensing Compliance: The LGPL is a copyleft license that requires any modifications or derivative works to be released under the same license. The question here is whether a "clean room" implementation, even if assisted by AI, can bypass this requirement.
• AI and Intellectual Property: As AI tools become more prevalent in software development, questions about the ownership and licensing of AI-generated code will only grow more complex.
• Community Trust: Maintaining trust within the open-source community is crucial. Any perceived violation of licensing terms can lead to significant backlash and erosion of confidence.

Technical Details

To understand the technical aspects of this controversy:

• AI-Assisted Development: The use of coding agents to assist in the development process has become increasingly common. These tools can generate code based on high-level specifications, which can then be refined by human developers.
• Performance Improvements: Dan claims that the new version of chardet is not only faster but also more accurate. This suggests that significant optimization and algorithmic improvements were made during the rewrite.
• API Compatibility: