logoalt Hacker News

linsomniac • today at 3:45 PM • 5 replies • view on HN

>My open source projects were barely sustainable

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.

Have the AI tooling do the heavy lifting of reproduction and benchmarking. One of my projects is fairly complicated and one user ran into some problems which he could describe the situation that caused it, but was light on any other details: my apt package cache was slow to serve the PHP update to his users. I asked AI to try to reproduce it: Set up a repo, set up different versions of my cache, have a client pull it, put an updated package in there, and have a client pull it again under different configurations. This could have taken me hours to do myself. AI did it with ~2 minutes of my effort.

>I have not organized my life around triaging annoyances

Then don't. AI can help with the triaging. Or, I give you permission: Close the repo for contributions. If you don't have time to maintain it, let people know, so they can fork or replace it. It sounds like your repos are already closed to contributions, due to lack of time/attention. That's fine, don't feel bad, just go ahead and make it official.


Replies

flatline • today at 3:55 PM

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.

➕ show 3 replies
yeoldeprogramme • today at 3:53 PM

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

necovek • today at 4:10 PM

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.

➕ show 2 replies
matkoniecz • today at 3:48 PM

> 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

aleph_minus_one • today at 4:44 PM

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