Quoting Andreas Kling

Serenity OS, a notable open-source operating system project, has announced a significant policy change that will reshape how the community contributes to its development. The project will no longer accept public pull requests, marking a departure from traditional open-source collaboration models. This decision reflects broader concerns about maintaining code quality and accountability in an era where artificial intelligence tools increasingly assist in software development.

Project creator Andreas Kling explained that the decision stems from changing assumptions about code contributions. Historically, substantial patches demonstrated genuine effort and commitment, serving as a proxy for good faith contributions. However, this assumption no longer reliably holds in practice. The core concern isn't whether code was manually typed or generated through AI assistance, but rather who bears responsibility for the contributed code once it's merged into the project.

The restriction aims to ensure that all contributions come with clear accountability and ownership. By limiting pull requests to a curated group of trusted developers, Serenity OS can maintain stricter quality control and verify that contributors take responsibility for their work.

The shift highlights critical challenges facing modern open-source projects:

• AI-assisted coding tools have complicated traditional quality assessment metrics
• Projects now require more sophisticated vetting processes beyond code review
• Accountability and legal responsibility have become central to contribution policies
• Open-source maintainers must balance community inclusivity with project integrity
• The definition of "good faith contribution" has evolved with technological capabilities

Serenity OS's decision reflects a growing tension in open-source development. While AI coding assistants offer productivity benefits, they introduce ambiguity about code ownership and responsibility. Major projects may need to adopt similar gatekeeping measures to protect their integrity and ensure contributors stand behind their work.

This policy shift signals that open-source governance is evolving. Rather than purely democratic contribution models, projects may increasingly require established relationships and demonstrated accountability. For developers and organizations, this underscores the importance of clear attribution, responsibility frameworks, and quality assurance in collaborative software development.