Gnome bans AI slop code from Extensions repo

Coding is one of the tasks that generative AI systems have become proficient at, leading to the popularisation of vibe coding, although with the added convenience of AI-generated code comes added risk, especially from those who don't necessarily understand what the code they're generating is doing under the hood. Aside from potential issues like inefficiency, mistakes, or generally ignoring project rules, AI-generated code also raises questions about more serious issues, like security. With the rise in AI-generated code, the Gnome Project has noticed an uptick in AI-generated extensions submitted to the Gnome Shell Extensions repository, and it has decided to address the influx of AI code by implementing a blanked ban on vibe-coded extensions. 

The Gnome project leadership's main issue appears to be a combination of both stylistic inconsistency and being sure that developers can understand and explain the code when submitting it for review. While the new rule doesn't quite ban code entirely, it specifies that it should only be used as a learning tool or for code completion. The actual design and engineering of extensions must be done manually. Gnome's new rule on AI code reads as follows:

While it is not prohibited to use AI as a learning aid or a development tool (i.e. code completions), extension developers should be able to justify and explain the code they submit, within reason.

Submissions with large amounts of unnecessary code, inconsistent code style, imaginary API usage, comments serving as LLM prompts, or other indications of AI-generated output will be rejected.