A few days after Micro$lop announced they’re using AI to develop Windows, PCs with Win11 started to have a bug, where the screen goes black (usually no signal), then the GUI slowly crawls back to be visible one-by-one. I wonder what kind of Linux equivalent we will have.
Slop can only create slop.
The Maintainers Summit reached consensus to deprecate the Assisted-by tag. Remove the documentation requiring it. Signed-off-by: Sasha Levin <[email protected]> --- Documentation/process/coding-assistants.rst | 21 +------------------ Documentation/process/submitting-patches.rst | 10 --------- .../it_IT/process/submitting-patches.rst | 10 --------- scripts/checkpatch.pl | 11 ---------- 4 files changed, 1 insertion(+), 51 deletions(-) diff --git a/Documentation/process/coding-assistants.rst b/Documentation/process/coding-assistants.rst index 051f0d819f68e..509dbf23a099b 100644 --- a/Documentation/process/coding-assistants.rst +++ b/Documentation/process/coding-assistants.rst @@ -40,24 +40,6 @@ is responsible for: * Adding their own Signed-off-by tag to certify the DCO * Taking full responsibility for the contribution -Attribution -=========== - -When AI tools contribute to kernel development, proper attribution -helps track the evolving role of AI in the development process. -Contributions should include an Assisted-by tag in the following format:: - - Assisted-by: LLM [TOOL1] [TOOL2] - -* ``[TOOL1] [TOOL2]`` are optional specialized analysis tools used - (e.g., coccinelle, sparse, smatch, clang-tidy) - -Basic development tools (git, gcc, make, editors) should not be listed. - -Example:: - - Assisted-by: LLM coccinelle sparse - Procedure for finding and fixing bugs ===================================== @@ -82,8 +64,7 @@ these steps: another one. The fix must not add build warnings and must pass the checkpatch.pl checks (see submitting-patches.rst). 6. Commit the working fix with a detailed message describing the problem, the - solution and a Fixes tag. Do not add a Signed-off-by tag, and add an - Assisted-by tag, as described above. + solution and a Fixes tag. Do not add a Signed-off-by tag. 7. Identify the maintainers and lists using scripts/get_maintainer.pl. Documentation/process/security-bugs.rst shows how to do that. 8. Indicate what could not be done. If the fix could not be built or tested, or diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst index 7ae79452e1b46..5f4e0156cca78 100644 --- a/Documentation/process/submitting-patches.rst +++ b/Documentation/process/submitting-patches.rst @@ -632,16 +632,6 @@ bugzilla.kernel.org is a public place in this sense, but email addresses used there are private; so do not expose them in tags, unless the person used them in earlier contributions. -Using Assisted-by: ------------------- - -If you used any sort of advanced coding tool in the creation of your patch, -you need to acknowledge that use by adding an Assisted-by tag. Failure to -do so may impede the acceptance of your work. Please see -Documentation/process/coding-assistants.rst for details regarding the -acknowledgment of coding assistants. - - .. _the_canonical_patch_format: The canonical patch format diff --git a/Documentation/translations/it_IT/process/submitting-patches.rst b/Documentation/translations/it_IT/process/submitting-patches.rst index a742610cb0709..d0e0d6c9ecc2e 100644Switch to FreeBSD.
Too popular, it’ll get AI slop eventually too.
We’re gonna have to gird our loins for TempleOS
Redox OS and Haiku are promising alternatives that reject AI code.
TempleOS generates random words with a fraction of the energy use of LLMs. The feature is called godspeak.
Switch to NetBSD instead, please.
Oh boy. NetBSD! GNU Hurd!
sorry, all the bsd’s are on the list and HURD might actually need it to get anywhere…
Huh, I found some useful alternatives on that list in case I needed a hardened anti-AI distro. Garuda Linux, they do not use AI at the moment but they also don’t have a firm policy yet either. Thankfully, they haven’t made this list, which is a good thing as most of them are pretty annoyed with AI. There are only some slop herders in the ranks but they seem to use it for personal stuff.
Time to give up computing!
there’s always 9front
Strong
I love this “A is imperfect so switch your entire existence to B” kind of answer that provides no value.
lol it wasn’t meant to be serious advice. I am not a fan of any of the BSDs on the desktop. I am a happy Fedora user. Linus and the kernel team made their stance on AI clear. We aren’t going to change that. If it gets to the point where it is worse than the alternatives, as a result of AI, I will look elsewhere. Until then, it works.
So you’ll stick around until you’re (possibly the first person you’ve heard about) affected by a (potentially serious, as in data loss) bug?
Maybe! There have always been bugs. I didn’t jump ship any of those times. What matters most is how it compares to the alternatives. What are your plans?
Fair enough 👍
lemmy borked and double posted. -deleted
Yeah AI in open source is probably the least negative thing about AI can’t count how many tickets are still open and they are not even that hard to deal with AI seems suitable for the job imo
“Yeah AI in open source is probably the least negative thing about AI. I can’t count how many tickets are still open, and they are not even that hard to deal with. AI seems suitable for the job imo”
Your comment with punctuation.
Breathe, son.
Tbh, with the current state of AI you also need to write a million test cases so the agent can measure if it succeeded and didn’t cause bad side-effects while at it. Which is kind of tricky when dealing with hardware stuff. They’d probably need to buy thousands of computers with all different hardware to test whether tickets for driver issues/shortcomings have actually been solved.
And with AI agents you oftentimes end up in situations anyway where it “solves” one issue but breaks two other things. So the number of open tickets might go down, or we’d end up causing more issues and tickets by this kind of automation…
I’d say it’s tricky to impossible to just make AI close a lot of tickets and actually solve them regarding something like an operating system kernel. There’s just too much human labour involved and a lot of edge-cases and hardware stuff to be factored in.
It’s dangerous to go alone. Take this: .:;,.,;:,.?
Use it wisely, friend.
Probably less Linus outbursts overall since he will have less humanSlop code to review…
Yeah, because the AI vendors sponsoring the project will pull their money out of Linux and create a hard fork that has all the C code converted to Rust with AI.
I think Linus is converting a lot of the kernel to Rust himself tbh.
Linus does very little programming anymore
Im aware, but he is actively using Claude to write some new code for the kernel.
“Linus outbursts”, like they’re not 100% deserved in severity and frequency.
Thats what I’m saying lol
