Quoting Andreas Kling

2026-06-05 · Source: Simon Willison's Weblog · Field: Technology & Digital — Software Development & Engineering · Depth: Novice, quick

Summary

Andreas Kling announced on June 5th, 2026, that the Ladybird browser project will no longer accept public pull requests, marking a significant change in its development model. This policy shift is driven by a re-evaluation of the assumption that substantial effort invested in a code patch reliably signifies good faith, a premise Kling states no longer holds true. He clarified that the origin of the code, whether typed by hand or generated by AI, is irrelevant; the paramount concern is who assumes responsibility for the code once it's integrated into the browser. As Ladybird evolves into a browser for real users, Kling emphasized that those introducing changes must be the same individuals who decide these changes are appropriate for the project and are prepared to answer for their consequences.

Key takeaway

For open-source project maintainers evaluating contribution models, Andreas Kling's decision highlights the increasing challenge of vetting external code. You should re-evaluate your project's reliance on "good faith" assumptions for pull requests, especially as your user base grows. Consider implementing stricter code ownership policies or transitioning to a more curated contribution model to ensure accountability and mitigate risks associated with unvetted external contributions.

Key insights

Ladybird ceases public pull requests, prioritizing direct accountability for all code changes.

Principles

• Code responsibility outweighs origin.
• Good faith cannot be assumed from effort.
• Project owners must own all code.

Topics

• Open-Source Governance
• Code Ownership
• Software Development Policy
• Project Contribution Models
• Browser Engineering
• Developer Accountability

Best for: CTO, VP of Engineering/Data, Software Engineer, Director of AI/ML

Related on AIssential

• GDS weighs in on the NHS's decision to retreat from Open Source — Public sector code should remain open by default to foster scrutiny and reuse, avoiding costs of privatization.
• Microsoft fixes VS Code after app gives Copilot credit for human's work — Default AI attribution in code commits sparked developer backlash and raised complex IP and liability questions.
• Can coding agents relicense open source through a “clean room” implementation of code? — AI-assisted code rewrites challenge traditional "clean room" definitions and open-source licensing compliance.
• Anthropic apologizes for invisible Claude Fable guardrails — Transparency in AI model safeguards is crucial for user trust and research integrity, even if it means refusing more queries.
• Cursor is CAUGHT red handed... — Attribution and transparency are critical in the open-source AI ecosystem, especially for high-value commercial applications.
• The Pope just weighed in on AI — AI's rapid advancement necessitates urgent ethical governance, robust safety measures, and clear economic justification.

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by Simon Willison's Weblog.