upvote
You can say, "go off and fork the project", and you'll get 20 forks, each one person's pet PR applied, and no more future progress without a dedicated maintainer triaging and coordinating all this stuff in one place. You are asking projects that are surviving but not necessarily thriving to simply die. And for what? To satisfy downstream developer demand for their AI-generated contributions to be accepted?

Not all contributions are equally valuable, and that is notwithstanding AI use. AI facilitates volume but not necessarily quality. Why should anyone spend resources benchmarking and reproducing a non-issue, or a PR that will not otherwise pass muster? We can automate a lot, but human judgment is still critical in making things to be used by humans.

reply
>you'll get 20 forks, each one person's pet PR applied

Sure; if the primary repo goes unmaintained, and nobody else steps up to maintain a fork, yes you might get multiple forks that solve a specific users individual issue. I'm not sure there's a way around that.

The comment I was replying to sounded like someone who was unavailable to handle non-AI requests as well. AI contributions is making it worse, though my biggest projects haven't been hit by it yet <knock on wood>.

Low quality contributions is a very real problem, I agree with that.

reply
how does the presence of those forks contribute to the project's demise in any way?
reply
It was common point of irritation and frustration to see projects like GNOME and Mozilla make bs excuses for not fixing bugs and randomly closing bug requests. People writing their own forks and patches were hailed as doing a worthy act. After AI, suddenly those people are all evil and the GNOME and Mozilla attitude is correct.
reply
Of course. So do you want a Grand Vizier to ban forks that are not valid so software runs the way it should be run?
reply
“ he could describe the situation that caused it, but was light on any other details”

You are too nice. Anyone who isn’t going to spend time to explain an issue should be automatically rejected.

We’re in this ugly situation where AI causes the problem and people’s idea to fix it is throw in more AI.

Just like throwing technology at climate change when our own obvious habits are destroying the planet. Let’s move to Mars.

reply
By running automated AI agents on untrusted inputs (PRs from strangers on a public repo), you open yourself up to attacks. And you could be spending money for somebody else.
reply
Agreed and this is a very real thing to be concerned about.

I like the idea of leaning on a decision like Jev model to identify such things.

reply
The only attacks possible would be the tools given to the agent.
reply
Assuming it can't perform a sandbox escape, at any rate. Maybe a Jev-like decision model would be a better idea.
reply
Or just don't allow tools, write a simple python script that uses the API and doesn't do tool calls, etc. etc. etc.

Table stakes for being an engineer these days should include knowing how to control LLMs, it's as fundamental as a working knowledge of databases. One doesn't need to know how design a data model from scratch or code up that python script using the OpenAI API from memory, but should know the general shape of what's possible and how to look it up.

reply
> AI can help with that! Give an agent some rules, like via a skill for the project, and then point it at the PR/Issue for triage to determine if it's one that fits the rules for auto-closing (already reported and decided WONTFIX, for example). Have it run this across all your repos.

For me it was a bit useful but it has not offset even 10% of damage caused by LLMs

and is solving least important problem

reply
> AI can help with that! Give an agent some rules, like via a skill for the project, and then point it at the PR/Issue for triage to determine if it's one that fits the rules for auto-closing (already reported and decided WONTFIX, for example). Have it run this across all your repos.

This requires a huge setup of the necessary AI infrastructure.

reply