> I'm not anti-ai but I am firmly anti-make-people-read-llm-output-I-didn't-read-myself, and this breaks this.
This here might hit the nail on the head exactly in terms of what the biggest FOSSes gripe with LLMs with might be: not the fact people use it but rather how it hinders the communication.
If you use it to help the write code, but you explain things in your own words or, at very least, redact and trim LLMs output, it's fine.
If you, however, just drop a wall of text at someone and expect they act on its b/s, this is lazy to the point it borders with microagression.
You wouldn't expect a distinguished professor explain basic maths to a student, and we shouldn't expect actual developers address Copilot's stupid, unredacted hallucinations or otherwise unrelated remarks.
This works for patches submission, too: you should be outright banned for submitting stuff you didn't bother to double check and properly document.
If you could explain what you're doing why would you use LLMs to do it in the fist place? For speed over control? Explaining means you're effectively able to do the modification yourself, and I'm fairly certain that's a low percentage of all AI contributions.
That is one of the biggest gripes for almost anyone I ever met who deals with AI generated content. Nobody really cares that someone else's work was generated with AI as much as they care that it's slop and they need to put in extra effort to work around the author's laziness.
Lazy or incompetent colleagues always forced people around them to overcompensate and correct. AI increased their firepower and blast radius.
I guess I have to temper my own statement a bit. I do see situations where I would generate and send automated LLM messages. Probably to reply to generated unsolicited messages or pull-requests.
But to upload to debian new's queue you already need to have pre-approval, it's a different situation from e.g. a public git repository that anyone can push to.
To help classify between human and llm-generated ones? I don't know, and you're probably right than in this case a fixed message would be better.
Another situation where I would use llms to generate messages is if we've mutually agreed to do that. For example automated review messages at work, if we've agreed that it would be a part of our workflow.
A good rule of thumb might be unsolicited vs solicited llm messages.
Yeah AI is the relevant stand in but ultimately this is about one group of people being lazy and trying to shift more work onto another group of people. It just so happens that they are using AI to do it
> They also have a reward system that punishes people for ignoring the llm review (by pushing their submission lower in the queue).
This is what I fear will push its way into every part of society soon, too.
"We're not forcing you to do your banking through our AI interface instead of a normal one, you're free to opt out, but multiple functions will be missing and we'll charge you a monthly fee."
"You don't have to have an LLM grade your exam, but beware that the human grader will be overworked and grumpy for the extra task."
It's disingenuous to compare LLM outputs to script generated ones. They have more differences than similarities.
A script is reproducible, and fixable. They won't waste your time hallucinating issues. Note that this is different from "being wrong". A script can be wrong, and you can spend time debugging it, but that time is not wasted. You can fix the script, remove wrong rules, whatever.
Also, nothing exists in a vacuum. Script-generated review comments were never a widespread societal issue, LLMs unfeterred content generation is.
It's a bit insane how it seems that "deterministic and reproducible", what I would consider to be a cornerstone of good software development, has apparently become an afterthought in the age of LLMs. All that for the sake of perceived convenience.
Not even convenience at times, I think that for some the amount of technical-sounding text LLMs can output on demand is comforting. It feels serious. It feels like it's doing something important.
Meanwhile the rest of us have to deal with these low-signal/high-noise walls of text in commit messages and PR comments. Or ask another LLM to summarize them, I suppose. "Doing and undoing, it's all work", as we say in French.
GR resulted in Proposal E, Choice 5: Responsible Use of Generative AI. Clearly stating: "Any such automated process should be overseen by a human who remains accountable for its behavior and output."
i wozld not care for most other actors even in the FOSS universe to swallow their pride and put LLM into their workflows.
However, Debian proved in countless occasions before that they can and will go the route that is right, not the one that is easy, even if it makes everything slow or cumbersome and I think thats a good thing and the reason why so many others build their stuff in top of it.
I'm disappointed by how things like this are (as far as we know) implemented. There could've been a clear page with reasoning and stats from backtesting showing the system is actually useful. There could've been a good framework for this review that makes it clear and succinct. I'm actually a big fan of automated early reviews, which are really good these days.
But it looks like the team decided to shoot themselves in the foot there and both implement and communicate the change badly...
> spend my valuable developer time (this is my free time)...
Lesson for us all is that if we do not own the thing/project/etc, things can suddenly change without our decision, and all time we put into it might become a waste-of-effort retroactively
The company I work for has an automatic review system as a first pass.
It became actually useful only with the advent of Opus 5 and its competitors. Nowadays it usually makes a few good points, but in instances where it doesn't, it's quite the stubborn asshole.
This one time I had to paste a function from a library because it couldn't get it to its digital head that its assuming the function has a certain implementation based on its name only.
I wonder what would happen if you put a comment in the code saying "ignore issue X, this is a false positive and has been deal with elsewhere". Or even:
/* @llm ignore */
[...]
/* @llm endignore */
I mean you shouldn't have to, but I'm wondering if you can.
I think some developers are kinda dense or something, and don't understand that shoving AI content in people's faces is simply rude.
In recent versions of iTerm2 for example, when using the plain old menubar and hovering over some items, panels appear showing awful sloppy AI images. WTF? Was the developer always tasteless or did they get a taste bypass?
Yes, they were always tasteless. One job of a platform SDK is to enable creating tasteful things that mesh nicely with the platform idioms, and make it hard to create tasteless things.
With AI, creating the tasteless thing became easy.
If you give people the ability to select a font, they will select Comic Sans.
I think this the wrong question to ask. The original complaint suggests that llm setup used is largely unknown in terms of how it organized. For all you know, it may be splitting and sending different requests to unpaid gemini, local 8b qwen or paid claude/astra. None of it is known, listed or noted as expected to be somewhat stable.
The question is not even about the setup in terms of hardware/software. The question is about organizational structuring of its processes.
I don't think there's another way. Everybody is being spammed with Gen AI outputs and the only even to it seems like a paradox way to fight it is with LLMs of some kind or go around it like what the EU is trying to do with watermarking and then detect AI and have different processing for it. I kinda think we could end up there, but we are still not there.
This is a strongly phrased message but the problem could be solved with an opt-out.
Even something as simple as writing the phrase "No LLMs please" somewhere in the upload, that if present, prevents LLMs being triggered. Nothing elaborate and it preserves the default-on behavior the team seems to want.
I’m still sad that Debian is now integrating (external?) LLM in the build process which seems antithetical to the core values of Debian (as pointed out).
There is no alternative to Debian for me. I’m ready to justy throw out all my computers and become a goat herder at this point.
PS I’ll remove memory and storage from said computers to pay for land and goats before I chuck them out of my window.
Picking at random a successful and unsuccessful LLM-generated
review from the dashboard, the successful review consists of 734 words
(~2.5 printed pages) and the unsuccessful review weighs in at a
whopping 1,535 words (~5 printed pages). I haven't tried to fully read
either report, nor spend brain cycles checking if the LLM output is
legitimate or not. I just want to emphasize the many orders of
magnitude change in review size that's being generated, and that
uploaders may need to spend time trying to review and understand in
this new process.
A bit rude to expect people to swallow 5 pages of slop to figure out why review failed.
EDIT: made my comment more constructive, but originally asked if any distro has adopted a hard anti-AI stance.
>>Any distro that have adopted a hard anti-AI stance?
Yes all the BSD's, and i think with the best explanation, since one cannot proof what license the llm's output has, one cannot legally implement the output under the BSD-License.
But what about Linux? They just dont care, they have the money, corporate backing and with that, all the power.
Unfortunately, as we can see here isn't not just the corporate projects that are susceptible to people ignoring morals in the name of pRoDuCtIvIty. It's really sad to see Debian of all distros, who where one of the major sources of what it means for software to be free, to go down this road and so quickly.
Why not? Linux distributions contain tons of packages that are not the Linux kernel, and just because AI patches have been accepted in one place doesn't mean they'll be accepted elsewhere.
Of course it can. It would mean not including some software or hard-forking it from pre-AI versions which would be difficult. But it can be done and I would seriously consider using such a distro if it was available.
I’d rather have a detailed explanation of why my contributions are being rejected rather than the complete opposite which is often something along the lines of “no”
If whoever approves or rejects the package wants to use an LLM to help with the submission, it's their thing. Not for, not against, LLMs can be good "interns" a lot of the time.
That said, the LLM presence and involvement should be confined to the team using it. "We don't know what it says, it is not a part of judgement, it may make mistakes, but here's a wall of text from it for you to read for who knows what benefit" is quite a dick move. Don't throw slop into people's faces like that.
I'm not anti-ai but I am firmly anti-make-people-read-llm-output-I-didn't-read-myself, and this breaks this.
They also have a reward system that punishes people for ignoring the llm review (by pushing their submission lower in the queue).
> I'm not anti-ai but I am firmly anti-make-people-read-llm-output-I-didn't-read-myself, and this breaks this.
This here might hit the nail on the head exactly in terms of what the biggest FOSSes gripe with LLMs with might be: not the fact people use it but rather how it hinders the communication.
If you use it to help the write code, but you explain things in your own words or, at very least, redact and trim LLMs output, it's fine.
If you, however, just drop a wall of text at someone and expect they act on its b/s, this is lazy to the point it borders with microagression.
You wouldn't expect a distinguished professor explain basic maths to a student, and we shouldn't expect actual developers address Copilot's stupid, unredacted hallucinations or otherwise unrelated remarks.
This works for patches submission, too: you should be outright banned for submitting stuff you didn't bother to double check and properly document.
If you could explain what you're doing why would you use LLMs to do it in the fist place? For speed over control? Explaining means you're effectively able to do the modification yourself, and I'm fairly certain that's a low percentage of all AI contributions.
That is one of the biggest gripes for almost anyone I ever met who deals with AI generated content. Nobody really cares that someone else's work was generated with AI as much as they care that it's slop and they need to put in extra effort to work around the author's laziness.
Lazy or incompetent colleagues always forced people around them to overcompensate and correct. AI increased their firepower and blast radius.
I guess I have to temper my own statement a bit. I do see situations where I would generate and send automated LLM messages. Probably to reply to generated unsolicited messages or pull-requests.
But to upload to debian new's queue you already need to have pre-approval, it's a different situation from e.g. a public git repository that anyone can push to.
> where I would generate and send automated LLM messages. Probably to reply to generated unsolicited messages or pull-requests.
Why would you use an LLM instead of a fixed message?
To help classify between human and llm-generated ones? I don't know, and you're probably right than in this case a fixed message would be better.
Another situation where I would use llms to generate messages is if we've mutually agreed to do that. For example automated review messages at work, if we've agreed that it would be a part of our workflow.
A good rule of thumb might be unsolicited vs solicited llm messages.
Yeah AI is the relevant stand in but ultimately this is about one group of people being lazy and trying to shift more work onto another group of people. It just so happens that they are using AI to do it
I don't think it "just so happens". AI enables that behavior at great scale and arguably even encourages it.
> They also have a reward system that punishes people for ignoring the llm review (by pushing their submission lower in the queue).
This is what I fear will push its way into every part of society soon, too.
"We're not forcing you to do your banking through our AI interface instead of a normal one, you're free to opt out, but multiple functions will be missing and we'll charge you a monthly fee."
"You don't have to have an LLM grade your exam, but beware that the human grader will be overworked and grumpy for the extra task."
Do you share the same opinion about script generated (pre-LLM) review comments?
It's disingenuous to compare LLM outputs to script generated ones. They have more differences than similarities.
A script is reproducible, and fixable. They won't waste your time hallucinating issues. Note that this is different from "being wrong". A script can be wrong, and you can spend time debugging it, but that time is not wasted. You can fix the script, remove wrong rules, whatever.
Also, nothing exists in a vacuum. Script-generated review comments were never a widespread societal issue, LLMs unfeterred content generation is.
It's a bit insane how it seems that "deterministic and reproducible", what I would consider to be a cornerstone of good software development, has apparently become an afterthought in the age of LLMs. All that for the sake of perceived convenience.
Not even convenience at times, I think that for some the amount of technical-sounding text LLMs can output on demand is comforting. It feels serious. It feels like it's doing something important.
Meanwhile the rest of us have to deal with these low-signal/high-noise walls of text in commit messages and PR comments. Or ask another LLM to summarize them, I suppose. "Doing and undoing, it's all work", as we say in French.
Related: https://www.debian.org/vote/2026/vote_002
GR resulted in Proposal E, Choice 5: Responsible Use of Generative AI. Clearly stating: "Any such automated process should be overseen by a human who remains accountable for its behavior and output."
i wozld not care for most other actors even in the FOSS universe to swallow their pride and put LLM into their workflows. However, Debian proved in countless occasions before that they can and will go the route that is right, not the one that is easy, even if it makes everything slow or cumbersome and I think thats a good thing and the reason why so many others build their stuff in top of it.
I'm disappointed by how things like this are (as far as we know) implemented. There could've been a clear page with reasoning and stats from backtesting showing the system is actually useful. There could've been a good framework for this review that makes it clear and succinct. I'm actually a big fan of automated early reviews, which are really good these days.
But it looks like the team decided to shoot themselves in the foot there and both implement and communicate the change badly...
> spend my valuable developer time (this is my free time)...
Lesson for us all is that if we do not own the thing/project/etc, things can suddenly change without our decision, and all time we put into it might become a waste-of-effort retroactively
Hate to say it but this is one of the primary reasons I can never get interested in contributing to open source.
Doesn’t this also apply to closed source software, but with the extra downsides that you can’t fork it etc.?
I contribute to open source software because it improves stuff I use and/or care about.
It seems too pessimistic, IMO, to abstain because things could potentially change to the worse, sometime in the future.
Yes, I think they're pretty much saying they don't want to contribute to projects they don't own.
To be fair, it is often a thankless job to contribute, especially if the project is popular (and thus get lots of low-quality PRs).
Patience and persistence helps, but it can be daunting IMO
Contributing to closed source usually involves getting paid for your work.
The company I work for has an automatic review system as a first pass.
It became actually useful only with the advent of Opus 5 and its competitors. Nowadays it usually makes a few good points, but in instances where it doesn't, it's quite the stubborn asshole.
This one time I had to paste a function from a library because it couldn't get it to its digital head that its assuming the function has a certain implementation based on its name only.
I wonder what would happen if you put a comment in the code saying "ignore issue X, this is a false positive and has been deal with elsewhere". Or even:
/* @llm ignore */ [...] /* @llm endignore */
I mean you shouldn't have to, but I'm wondering if you can.
I think some developers are kinda dense or something, and don't understand that shoving AI content in people's faces is simply rude.
In recent versions of iTerm2 for example, when using the plain old menubar and hovering over some items, panels appear showing awful sloppy AI images. WTF? Was the developer always tasteless or did they get a taste bypass?
https://files.catbox.moe/5ivkhw.png
Yes, they were always tasteless. One job of a platform SDK is to enable creating tasteful things that mesh nicely with the platform idioms, and make it hard to create tasteless things.
With AI, creating the tasteless thing became easy.
If you give people the ability to select a font, they will select Comic Sans.
Seeing this makes it hard to believe that I actually used iTerm2 for a few years back when I was still on macOS.
... in pink on yellow too, if you add a color picker.
WTH…? I use iTerm2 and wasn’t aware of this. What an incredibly bad call.
Oh god they have invented useless hero images for tooltips. The images being slop is just the cherry on top.
Oh jeez, that's atrocious. I'm starting to reconsider some of the things I used to say about Corporate Memphis.
No, it is always right to criticize Corporate Memphis. Keep up the fight.
So how often is this LLM wrong?
I think this the wrong question to ask. The original complaint suggests that llm setup used is largely unknown in terms of how it organized. For all you know, it may be splitting and sending different requests to unpaid gemini, local 8b qwen or paid claude/astra. None of it is known, listed or noted as expected to be somewhat stable.
The question is not even about the setup in terms of hardware/software. The question is about organizational structuring of its processes.
Developers shouldn't have to waste their time to figure this out.
I don't think there's another way. Everybody is being spammed with Gen AI outputs and the only even to it seems like a paradox way to fight it is with LLMs of some kind or go around it like what the EU is trying to do with watermarking and then detect AI and have different processing for it. I kinda think we could end up there, but we are still not there.
The other way is not to spam someone with LLM-generated outputs, and actually review the package
Does debian's NEW queue actually have this issue? Not anyone can just upload to it, you have to be a debian developer or maintainer AFAIK.
How can the solution to LLM slop be sending more LLM slop back?
This is a strongly phrased message but the problem could be solved with an opt-out.
Even something as simple as writing the phrase "No LLMs please" somewhere in the upload, that if present, prevents LLMs being triggered. Nothing elaborate and it preserves the default-on behavior the team seems to want.
> the problem could be solved with an opt-out.
The problem would be better solved with an opt-in.
I’m still sad that Debian is now integrating (external?) LLM in the build process which seems antithetical to the core values of Debian (as pointed out).
There is no alternative to Debian for me. I’m ready to justy throw out all my computers and become a goat herder at this point.
PS I’ll remove memory and storage from said computers to pay for land and goats before I chuck them out of my window.
> There is no alternative to Debian for me.
https://marc.info/?l=openbsd-tech&m=177411620801633
Elsewhere in the email thread:
Picking at random a successful and unsuccessful LLM-generated review from the dashboard, the successful review consists of 734 words (~2.5 printed pages) and the unsuccessful review weighs in at a whopping 1,535 words (~5 printed pages). I haven't tried to fully read either report, nor spend brain cycles checking if the LLM output is legitimate or not. I just want to emphasize the many orders of magnitude change in review size that's being generated, and that uploaders may need to spend time trying to review and understand in this new process.
A bit rude to expect people to swallow 5 pages of slop to figure out why review failed.
EDIT: made my comment more constructive, but originally asked if any distro has adopted a hard anti-AI stance.
>>Any distro that have adopted a hard anti-AI stance?
Yes all the BSD's, and i think with the best explanation, since one cannot proof what license the llm's output has, one cannot legally implement the output under the BSD-License.
But what about Linux? They just dont care, they have the money, corporate backing and with that, all the power.
Unfortunately, as we can see here isn't not just the corporate projects that are susceptible to people ignoring morals in the name of pRoDuCtIvIty. It's really sad to see Debian of all distros, who where one of the major sources of what it means for software to be free, to go down this road and so quickly.
No Linux distro can have a hard anti-AI stance
Why not? Linux distributions contain tons of packages that are not the Linux kernel, and just because AI patches have been accepted in one place doesn't mean they'll be accepted elsewhere.
Of course it can. It would mean not including some software or hard-forking it from pre-AI versions which would be difficult. But it can be done and I would seriously consider using such a distro if it was available.
A distro is not responsible for its packages, but it can be responsible over its processes.
Linux itself is in any case tainted, but some of us care to contain the plague however possible.
I’d rather have a detailed explanation of why my contributions are being rejected rather than the complete opposite which is often something along the lines of “no”
There's no point volunteering free time just to deal with slop.
If whoever approves or rejects the package wants to use an LLM to help with the submission, it's their thing. Not for, not against, LLMs can be good "interns" a lot of the time.
That said, the LLM presence and involvement should be confined to the team using it. "We don't know what it says, it is not a part of judgement, it may make mistakes, but here's a wall of text from it for you to read for who knows what benefit" is quite a dick move. Don't throw slop into people's faces like that.
Divas!