Christophe Pettus: The Maintainer Is Not the Owner

Why It Matters

Relicensing without full contributor consent threatens legal stability and erodes trust across the open‑source ecosystem, especially as AI‑generated code blurs traditional copyright boundaries.

Key Takeaways

• Maintainers lack rights to relicense code without all copyright holders' consent.
• AI‑generated rewrites are not legally recognized as clean‑room implementations.
• Changing a project's name avoids trademark conflicts and clarifies forks.
• License stability is essential for downstream users' trust and compliance.
• Transparent contributor tracking prevents future legal disputes over ownership.

Pulse Analysis

The chardet episode underscores a fundamental principle of open‑source law: stewardship does not confer ownership. While a maintainer can merge patches and publish new releases, the underlying copyrights remain fragmented among original authors, contributors, and any third‑party code. Without explicit assignments or a contributor licence agreement, any attempt to shift the license—especially from a copyleft regime like LGPL to a permissive one—requires unanimous consent. Failure to secure that consent not only exposes the maintainer to potential infringement claims but also destabilizes downstream projects that rely on the original licensing terms.

Artificial intelligence adds a new layer of complexity. The clean‑room doctrine, traditionally enforced by separating specification and implementation teams, assumes no exposure to the source code. When a large language model such as Claude is trained on the very code being rewritten, that wall collapses; the model’s weights effectively encode the original work. Courts have yet to rule on whether AI‑generated output can be deemed a non‑derivative clean‑room product, leaving maintainers on uncertain legal ground and making the AI‑driven relicensing strategy risky.

Practitioners can avoid these pitfalls by following proven fork‑and‑maintain practices. The pgBackRest continuity fork pgxbackup kept the MIT license, adopted a distinct name, and clearly positioned itself as a separate project, preserving both legal and brand integrity. Maintaining accurate contributor records, announcing stewardship changes publicly, and respecting original naming preferences further safeguard against disputes. As open‑source ecosystems mature, adhering to these norms ensures that projects remain reliable, legally sound, and attractive to both developers and enterprise adopters.