The Reddit open-source community r/opensource has announced that it does not welcome projects that use AI, are built with AI, or are built for AI. A follow-up post, however, stated explicitly that Linux is not banned, and said the revised rules are not yet complete. Between the blanket rejection in the original wording and the case-by-case acceptance in practice, the moderators retain discretion. Being able to distribute software as open source is a separate matter from being able to showcase it in this forum, and the conditions for participation can also affect developers who don't use AI.
Linux is tolerated, but the line on AI is left to discretion
In the original announcement, u/Wolvereness set out a policy of rejecting, as a group, projects that use AI, are produced with AI, or are developed for AI purposes. The policy applies to posts on r/opensource, not to Reddit as a whole. It was a broad announcement that covered not only code written with AI but also software that uses AI and projects aimed at AI.
The announcer, however, did not present a standard that could be applied mechanically. Asked in the comments about the difference from things like AI-assisted bug checking, Wolvereness answered that there is "no 'objective' way to enforce this policy," and explained that the rule exists to preserve the discretion to remove posts. As for Linux, he said it meets the project minimums and would be allowed under a subjective line. The original comments had thus already acknowledged individual exceptions.
The follow-up said Linux has not been banned and that banning it in the future is unimaginable, while also stating that personal projects like those built in two Claude Code usage windows are not welcome. Tolerating Linux does not mean the initial rejection of AI-related projects has been fully withdrawn. Examples of what is accepted and what is turned away were given, but the revised rules that would separate the two are unfinished, and the boundary may shift in response to ongoing feedback.
Accordingly, the treatment of Linux alone does not tell us whether other projects can be showcased for the same reason. The decision to allow a showcase in the forum is also separate from the question of what kind of code Linux development itself accepts.
Open-source eligibility and posting eligibility are different things
The Open Source Initiative's Open Source Definition sets standards for licensing when software is distributed. Clause 5 prohibits discrimination against persons or groups, and clause 6 prohibits discrimination against fields of endeavor. It is not, however, a provision obliging any particular forum to accept every submission. r/opensource had layered project track-record and poster requirements on top of its long-standing license requirements.
The r/opensource entries in the table below are the conditions from the original announcement; the revised version is not yet complete.
| What is judged | What sets the standard | Confirmed conditions / scope |
|---|---|---|
| Software distribution | OSI Open Source Definition | Licensing standards for distribution. No discrimination against or restriction of persons, groups, or fields of endeavor |
| Project showcase | r/opensource original announcement | In addition to the long-standing OSI license requirement: over a year of active maintenance, multiple contributors (subjectively three or more), and an existing community |
| Poster participation | r/opensource original announcement | Accounts over a year old and sufficient Reddit activity (long-standing conditions). The ability to speak English is also required |
Separating distribution license, project posting conditions, and poster participation conditions into three rows shows that a solo developer who doesn't use AI could still be shut out, while the openness of the license is preserved separately. If years and headcounts are made conditions, young projects and small-team development can be excluded before anyone examines how AI is actually used.
The original announcement excludes typical school assignments and does not accept recruitment of maintainers or contributors. In other words, it requires that a project already have multiple contributors, yet cannot be used to recruit those collaborators here. Certain registered nonprofits and similar organizations may be exempted from minimum project and account standards through prior approval, but the announcement does not state that the exemption extends to the AI rules as a whole.
The moderators also took a hard line on the exception process. Wolvereness warned of permanent suspension and muting for anyone who requests an exception after attempting to post, and estimated that exception requests and similar messages amount to about 20 a day. That figure is the author's own explanation of the moderation burden, not an independent count. How much the new conditions will actually reduce that burden has not yet been shown.
The English requirement and the effort of verifying translations
The original announcement asked people who cannot speak English to find another community. The reason the moderators gave was that they cannot tell text generated by AI apart from text the author wrote and ran through AI translation, and that posters themselves cannot verify that a translation is correct. What is required is the ability to speak English, not to be a native English speaker. Even so, for people who participate using AI translation, it adds a condition unrelated to the content of the code.
Not all moderators appear to have agreed on this language condition. According to a comment by ssddanbrown, he learned of the change through a review notification triggered by increased activity, and said he disagrees with the English rule and with how it was worded. He said he had seen nothing showing discussion with the other moderators, but did not rule out that they had consulted through another channel, so it cannot be asserted that there was no internal discussion at all.
An alternative way of accepting posts has also been proposed. HotHardware's Alan Velasco described a format that places the original-language text alongside the translation so that others can verify its accuracy. He himself adds the caveat that checking would take more time. Side-by-side text increases the material available for checking, but it does not by itself guarantee accuracy or remove the need for verification work.
If participants are required to have English ability, the burden of checking translations shifts onto them. If side-by-side original and translated text is accepted, someone has to take on the verification. This is not only a question of how to judge AI use; it is also a choice about who bears the effort of keeping the showcase open.
The follow-up said the rules would not target or favor particular ethnicities or social classes, but it did not say the English or headcount conditions had been specifically withdrawn. The revised version will have to answer how far the rejected AI use extends and how the year, headcount, and English conditions fit together. The measure of its practicality will be whether developers considering a showcase can check the conditions before posting, and whether the moderators can explain their reasons for removals.