> Pick one open source tool you use. Find the most annoying thing about installing or running it. Spend a weekend fixing it, with the people who maintain it. Then tell me about it.
My open source projects were barely sustainable when the few PRs that came in would fix actual, non-hypothetical, serious logic problems.
Now I've been seeing PRs like that, fixing annoyances, performance edge cases, or hypotheticals, across my open source repositories, and I don't have time for them. I especially don't have time to fix problems that probably nobody will ever experience, and yet they keep coming. I have not organized my life around triaging annoyances (let alone fixing them).
If the trend continues, I'll soon be forced to close repositories to contributions, or just stop maintaining the projects entirely. And I imagine that's the point a lot of maintainers are at.
rejecting a PR saying "i don't have the time to deal with this" is 100% valid thing to do. Don't let yourself be taken advantage of, it's your project. If the submitter doesn't like the answer then they an fork and go on their merry way, that's also a 100% valid thing to do and is the backbone of open source.
I've had my AI contribute to a bunch of open source so i'm on the other side of this.
For me they're real issues. Half of which i'd found before but never had the time to submit something for, the other half its things the AI will have encountered - and i check to confirm its a real issue.
The AI will follow guidance you leave in a repository. One of them said "no ai", so it reported that to me and I just forked and went on with my life.
There might be people farming for gh contribution i dontk now — but I can assure you the trend will continue, and afaict it is improving software; at least most of my contributions have been merged.
I don't accept PRs anymore for which there isn't an open issue where either maintainers discussed the issue or it has significant discussion among users. I'm trying to use issue labels to indicate if something is ready to accept PRs.
I see a lot of unsolicited PRs (and my case not from actual users but instead university students trying to pad their resume with random open source contributions but while clearly using AI exclusively)
>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.
That's sad, but don't let yourself get burned out.
Free software and open source licensing, and projects like Debian, are set up so the software survives even the death of the author and the project. They can make their own improvements for their own ecosystem without upstream support. They integrate what comes from upstream whenever they can.
Someone get their contributions accepted by upstream is a nice thing to have, but upstream don't have to accept it, and if they do, it's at their pace.
Secondly, don't let a pile of open issues and PRs bother you, unless they're fundamentally incorrect (in which case let your authorial voice be known). Because it's also useful for users of your software to give each other feedback and help each other out, e.g. "this app doesn't work with the latest macOS changes, but here's the code changes you'd need to fix it" means that users can help each other often for years before the maintainer gets around to looking at issues. If you're on some sort of code forge site, users can organise there. If you're not (and only accept patches by email or whatever), users can organise themselves elsewhere.
Isn't that why it says "with the people who maintain it"? Like maybe open an issue or reach out and tell the maintainer, 'hey, I have this issue, and I want to fix it, would you like a PR if I do?' And then if there is interest, maybe a discussion about it as necessary.
This is what I do, and have done, since long before LLMs. And if they aren't interested? If its a big enough problem for me, I maintain my own fork. Forking is the greatest part about open source projects!
Perhaps add some guidance to your README.md or AGENTS.md, saying that you prefer concise issue reports with simple isolated reproduction sets over PRs? And that they must be, as you said, _actual, non-hypothetical_ issues?
And be OK with closing issues that have dubious merit?
Just make a contributor license agreement based on Benedictine doctrine. At least one very successful FOSS project does that: https://sqlite.org/codeofethics.html
… What's your secret? I keep hearing from people on HN about how they're flooded by AI-driven PRs but my own projects get ignored completely. And most of the time that I check out some other random Show HN project, it's not getting much buzz either. For that matter, I commonly see stuff that has hundreds of seemingly organic stars, and flip over to the PRs and it seems pretty dead to me.
With the increasing power and lowering cost of LLMs, I wonder if we should move to a "apply these patches to the latest version for me" model. That way everybody is happy.
Consider taking donations. As a MIAB user, I love it and would be sad seeing it go away.
That being said, I know if one reaches that point in burnout, money won’t change anything. You are under no obligation to do any of this after all. So in the meantime, thank you. :)
and how does this get fixed? really - with more management is the only answer. who pays for this time - nobody. then they would blame the maintainer for being slow... and eventually fork if everyone's luck. why not close outright then?
Remember the "Savage Reservation" in Huxley's Brave New World?
We need the equivalent of that for open source software maintained by people from before 2004.
Perhaps it is time for pull requests to come with payment in escrow that gets transferred after the maintainer does a review and approval.
This would eliminate a lot of AI slop, and I wish I had a popular repo so I could try it. I might unfilter and glance at the non-funded PR's once a year.
> My open source projects were barely sustainable when the few PRs that came in would fix actual, non-hypothetical, serious logic problems.
As a maintainer of some projects: at this point I would appreciate far more useful review of already submitted PRs.
As long it is not blind copy-pasting LLM output. That would be highly obnoxious attack.
Just disable PRs
[flagged]
Why not delegate PR approval to a group of trusted contributors? Give 10 people review and merge permissions, require at least two approvals and passing CI checks, and let them handle the day-to-day PRs. Surely distributing the maintenance workload is a better alternative to closing the repository to contributions?
> to fix problems that probably nobody will ever experience
Have you considered that the person submitting the PR to fix said problem has themselves experienced it? I find that is most often the case. But there is definitely an increase in the "performance edge cases, or hypotheticals" framing, where I am equally befuddled/too tired.