The GNOME.org Extensions hosting for GNOME Shell extensions will no longer accept new contributions with AI-generated code. A new rule has been added to their review guidelines to forbid AI-generated code.
Due to the growing number of GNOME Shell extensions looking to appear on extensions.gnome.org that were generated using AI, it’s now prohibited. The new rule in their guidelines note that AI-generated code will be explicitly rejected
Have people died to desktop extensions?
Cause that’s the topic here.
You’re fighting a holy war against all AI, dune style.
I’m saying this is a super low risk environment where the implications appear to be extra try/catch blocks the code reviewers don’t like – not even incorrect functionality.
Well I was just arguing that people generally are using AI irresponsibly, but if you want to get specific…
You say ban the users, but realistically how are they determining that? The only way to reliably check if something is AI is human intuition. There’s no tool to do that, it’s a real problem
So effectively, they made it an offense to submit AI slop. Because if you just use AI properly as a resource, no one would be able to tell
So what are you upset about?
They did basically what you suggested, they just did it by making a rule so that they can have a reason to reject slop without spending too much time justifying the rejection
I’m only responding to this thread, yes, not the vast irreparable harm llms are doing to society and the world. Those are different arguments and I don’t see any coupling between them at all.
I say ban users who submit code that causes problems. If that’s mostly AI shit, fine, but I’d be shocked if humans didn’t also submit trash of a different sort. You ask how can they realistically determine that…isn’t that literally what this entire thread is about? I don’t think “using AI” is a criteria for anything. Their actual, real problem is with bad code they have to deal with, so why is “it uses AI 😭” the metric rather than “bad code”? Your entire argument seems circular to me.
I don’t think you understand what doing code reviews is like.
So someone submits terrible code. You don’t get to just say “this is bad code” and reject it wholesale, you have to explain in exhaustive detail what the problems are. Doing otherwise leads to really toxic environments. It’s killed countless projects
That’s why you write rules. You don’t have to argue if they need tests or not, you tap the sign and reject it without actually reviewing it if it doesn’t meet the requirement
Same thing here. You open up vibe coded nonsense so you tap the sign and reject it without bothering to review it. Do the same thing with “bad code” as a reason and it starts insane drama.
People are really sensitive about their code, and there’s a whole methodology around how to do without ending up in a screaming match