New rules apply in the Reddit community r/opensource. Among other things, they are intended to prevent posts from being created with the help of generative AI, i.e. with tools that automatically generate text or source code. In addition, contributors are required to have sufficient knowledge of English. Both meet with clear criticism in the community.
The matter is initially a conflict within the community. But it highlights a development that extends far beyond a single forum: open-source projects must clarify how they deal with contributions whose origin can no longer be clearly attributed to a person.
Why the debate affects projects outside Reddit
Open source works through trust and traceable contributions. Anyone who submits an extension vouches for it with their name, history and reputation. Generative AI shifts this balance in two directions.
First, the effort required to submit anything at all decreases. More pull requests, i.e. change proposals to a code repository, and more discussion contributions are created. The review capacity of the maintainers, i.e. the responsible project maintainers, does not grow at the same rate.
Second, the assessment becomes more difficult. An AI-generated contribution can be technically correct. But it can also appear plausible and yet miss the project's architecture because the model does not know the context. These cases are only recognised on close reading – precisely where resources are scarce.
Ban, labelling or review obligation
In practice, different approaches are emerging by which communities react to this situation. Roughly, they can be described as follows:
- Restriction: AI-generated contributions are prohibited or heavily restricted. The advantage is clarity, the disadvantage is the difficulty of enforcement – reliable proof of machine generation hardly exists.
- Transparency: Contributions may be created with AI support but must be labelled. This shifts responsibility to the submitting person and allows more targeted review.
- Outcome orientation: The origin remains secondary; what matters are tests, documentation and the willingness to explain and maintain the contribution.
The criticism of restrictive rules has a comprehensible core: formal hurdles affect not only automated submissions but also people who find things more difficult linguistically or professionally. A rule against AI can therefore, in its implementation, exclude the very people it was meant to include.
Consequences for projects with open-source components
For companies that run web projects on an open-source basis – for example with TYPO3 and its extension ecosystem, i.e. the third-party extensions – the debate is not an academic question. Every integrated extension is foreign code in your own system.
Until now, the assessment of an extension has relied on indicators such as maintenance status, release history, number of contributors and response time for security reports. These indicators remain valid. But they need supplementing when part of the contributions is machine-generated: activity alone is then no longer a reliable quality signal, because commits can be generated more easily than solid expertise.
How quality can be recognised in future
Instead of looking at pure activity metrics, it is worth taking a look at a project's governance, i.e. its rules and decision-making processes:
- Is there any documented stance on AI-assisted contributions at all?
- Are pull requests commented on in substance or mostly waved through?
- Do automated tests exist that catch regressions?
- Is it recognisable who bears responsibility for security issues?
- How quickly and how soundly are responses to issues given?
These points can be checked in a few minutes per component and belong in the shortlist before a dependency moves into a production system.
Don't forget your own side
The same questions arise internally. Anyone who uses AI tools in development – and that is now everyday practice in many teams – should clarify in a binding way how generated code is handled. Clear responsibilities in review, documentation of the tools used and the rule that no one submits code they cannot explain are sensible.
If your own code is contributed back to open-source projects, the rules of the respective project are added. A contribution that violates the local AI policy costs time at best and reputation at worst.
Assessment
The dispute in r/opensource is an early example of communities adapting their rules to generative AI – and of the fact that there is not yet a consensus-capable solution for this. For web and software projects, this means aligning the selection of open-source components more strongly with governance and review quality rather than with activity figures. Anyone who additionally defines within their own team how AI-assisted contributions are reviewed and labelled gains room for manoeuvre before rules are imposed from outside.