alt Hacker NewsI've never been involved with Linux kernel work, but in terms of the "You, as a person, not the AI, are responsible for the quality" policy, this to me is a just an "obvious" policy that should be applied to any non-vibe-coded software.
It's just another way of saying, you can't have AI submit things on its own and you can't "blame" AI for anything you submit, you're expected to understand and be able to explain anything you're putting forward, if there is an issue with your submission, doesn't matter at all if you go back to AI to address it, so long as all issues are properly addressed.
The code is either of sufficient quality, or it's not, doesn't matter whether you or AI wrote it, it's your name on it, you're responsible for it and its your reputation on the line.
Replies
The problem with this policy is that it works well when dealing with individuals, but you can still be swamped by "first-time sloppers" - sure, each one cannot ever submit again because it's low-quality slop, but the damage is done.
(And in reality EVERYONE's AI policy is a variation of this no matter how strict they get, because very few people will suddenly rip all of tridge's code out of Samba if he admits he used AI once, and nobody can withstand slopspam for long.)
I agree, I was writing something along those lines but with more words (which is not a good thing) :-).
> should be applied to any non-vibe-coded software
Should be applied to anything someone is releasing without big disclosures.
At least until a few months from now when it will be clear that human code is the weak point.