> 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.

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.

Disclosure: I'm not a Debian Developer, yet I have worked on Debian derivatives and I'm somewhat familiar with internals of Debian from technical and human perspectives.

While I'm perfectly on the same page with the critics of the LLM generated summaries, I'm a bit torn on the issue.

For anyone not familiar with Debian ecosystem, there's a helper tool called Lintian. Lintian does all kinds of checks from package formatting, licenses to dependency management (which can detect both unnecessary yet included and necessary but missing dependencies via static analysis of your tool if necessary).

It's expected that your package to be "Lintian clean" to be able to included in Debian with minimum friction and wait. Even though it's Lintian clean, your package also checked by teams which are severely understaffed, and composed solely of voluntary people.

NEW queue also receives tremendous influx of packages (which can be considered a torrent, even). Since noon, there are 10 more ITP (intention to package) bugs open in my inbox.

As a result, at one hand, these people need every help they can get because getting new trainees and getting them to learn the intricacies is hard, on the other hand LLM generated text rightfully generate negative reactions from people. However, giving developers an automated check of what looks right and what looks wrong is helpful, in my perspective.

I wonder what people would have said it was a deterministic tool generating these reports and sending people these summaries as a "hey consider this feedback until a human has time to see your package".

This is a hard question and we need to think before impulsive reactions. I even don't have all or any of the answers, but at least I have some insight why this is there.

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."

Maybe it's an unpopular opinion, but a concise report from one of today's frontier models is not something I would be offended by, even if nobody read it beforehand. I guess the fact that there is a nontrivial cost to it also eases the existential angst of neither being deterministic (Lintian) nor having been produced by a person.

Eh, you read compiler and linter output don't you? Nobody read that before you did.

Sure LLMs are not nearly as rigorous about their output but that doesn't mean it's entirely not useful.

At a minimum you can have your LLM summarize the other LLMs output and go from there.

Do you share the same opinion about script generated (pre-LLM) review comments?