Remix.run Logo
▲ joshdata 4 hours ago

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

▲cwel 4 hours ago | parent | next [-]

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

▲Conscat 3 hours ago | parent | next [-]

And personally I have never once opened a PR for any issue I didn't personally experience. Even when I used an LLM to assist, I've only worked on things I personally needed.

▲awakeasleep 4 hours ago | parent | prev | next [-]

What makes you think a person is submitting the PR

▲cwel 4 hours ago | parent [-]

Poor phrasing on my part, I should have said "the person involved in the PR", "the one behind the prompt".

▲kuriho 4 hours ago | parent [-]

not the parent, but I received one PR adding a new feature to my and similiar projects at the same time. When I questioned the use case the PR sat around until it was closed months later. Hardly a real user.

▲j16sdiz 4 hours ago | parent | next [-]

Before AI, I have submit PR band-aids bugs I personally experienced, but don't bother enough to fix it properly. When the maintainer ask about it, I move on and ignore it. I just don't care. Some maintainer found them useful, some don't.

I came from the "free software as in free puppy" camp. I would stop by to play with the puppy, but I won't feed it.

I guess if I do the same today, I might submit a better-than-band-aid fix from LLM. You would probably think I am not a real user.

▲stackghost 4 hours ago | parent | prev [-]

Sounds more like a real user than an LLM, which would have given you a 4-heading treatise where the third heading was some variation on “Why this matters”.

▲riedel 3 hours ago | parent | prev | next [-]

Actually IMHO, we need better automatic build system integration with feature management. How cool would it be if the average user could vote with their feet if something is needed. Once there is enough adoption and no negative test reports consider merging it.

I guess also AI managed canary l releases could be an option IMHO that combine open PRs.

▲matkoniecz 4 hours ago | parent | prev | next [-]

> Have you considered that the person submitting the PR to fix said problem has themselves experienced it?

I had multiple PRs for entirely hallucinated problems.

Or where no human ever looked at project or PR and were just attacking open source projects with spam PRs pretending to be contributions. Not sure whether it was out of malice or done for some other reason. Maybe they were mistakenly thinking it is helpful?

▲shagie 2 hours ago | parent [-]

> Not sure whether it was out of malice or done for some other reason. Maybe they were mistakenly thinking it is helpful?

I believe a fair bit of this is an attempt to gain numbers where quantifiable numbers are advertised on otherwise indistinguishable resumes (with the corresponding belief that those numbers make differences in filtering or hiring decisions).

I base that on having seen people in the days of old put their Stack Overflow reputation on resumes thinking that having a rep of 4321 will be more likely hired than someone with a rep of 1234.

Having "210 accepted PRs on GitHub" (they believe) would appear to make them a more productive / less risky hire than someone who hasn't done any.

---

This is really a case of indistinguishable resumes where nearly everyone in the pool went to the same college, same internships, same capstone project, and maybe the same first year or two of professional experience.

▲JDups 2 hours ago | parent [-]

There are job applications that list having a certain amount of contributions to github projects as a requirement. Encourages useless spam. Also funny the implication that only projects on github have any worth.

▲shagie 2 hours ago | parent [-]

That wouldn't surprise me in the slightest. I see it with applicants for a position that doesn't have GitHub contributions listed as either a requirement or a nice to have.

I could see it as a "proof of familiarity with CI and expectations for a PR", though for applicants that are spamming the process with poor PRs (and people posting poor Q&A on Stack Overflow back in the day), this often hurts them more than it helps as its a demonstration of what they are going to be doing if they are hired (I've already got too many poor quality PRs to review, your PRs would not reduce the amount of time that the reviewer would need to spend).

▲levkk 4 hours ago | parent | prev [-]

That's not the case all the time anymore. It used to be. But it's not now.

So yeah, I've considered it and eliminated it for most PRs we used to get. Because no, a 2nd year student in university did not run into an obscure edge case in production that none of my 1M+ QPS users did.

▲zahlman 2 hours ago | parent [-]

Sure, but maybe the reason you're getting PRs is because you have 1M+ "QPS users", whereas I can't even think off the top of my head what QPS stands for.

▲thinkmassive 36 minutes ago | parent [-]

Could be "users who handle 1 million queries per second"

▲chasd00 4 hours ago | parent | prev | next [-]

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.

▲ravenstine 3 hours ago | parent | next [-]

PRs should be rejected by simply not enabling PRs in the first place. If PRs are needed for development, then that should be done in a private repo that is mirrored to a public one. I wouldn't even be surprised if that person'a readme says the project is open to contributions and that pull requests are welcome. I've found this contradiction to be very common, yet it seems like I'm in the minority for believing it's rude.

▲seki285 4 hours ago | parent | prev | next [-]

Forking also doesn't mean completely going your own way! I have multiple repos forked where we and the maintainer disagreed on the direction, so I keep my additions on top of theirs in my own repo just how I like

▲larodi 4 hours ago | parent | prev [-]

yeah sadly only 0.0001% of all users and reporters seem to understand this stand, which is oh-so-obvious if you have ever put anything public, but then people use opensource because it was hailed as free, more secure, and even more trustworthy. and as a result everyone and their dog not only seems to blindly prefer it but is then entitled to service which was never promised. what a massive cognitive dissonance indeed, but one that was carefully catered to and fed by the few key opinion leaders in the opensource sphere.

▲athrowaway3z 4 hours ago | parent | prev | next [-]

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.

▲ryandrake 9 minutes ago | parent [-]

I’m in this awkward spot, too. Previously if I found a bug in an open source project, I would just fix it and automatically offer the maintainer a patch. I wouldn’t even think about it. Now, with all the hostility and maintainer burnout, I have to think: Is this maintainer burnt out? Is he going to get all upset that I dared to open a PR? Am I going to need to manage his feelings and expectations? Is he going to object to AI? I always poke around to look at any CONTRIBUTOR docs to see what the project allows, whether they care about AI, and what their general attitude towards PRs are. Bad signs include a huge list of uncommented PRs and releases just chugging along with only the maintainer making changes. Often I’ll just not bother with the drama and just keep the fix in my fork forever. It’s not worth it to contribute back.

Parallel problem is a lot of projects don’t even offer a way to suggest fixes or changes anymore. This is probably partially maintainer burnout but I’ve seen it since before the AI craze. Many open source projects run on a locked down gitlab that doesn’t accept PRs at all. So I just email a patch into the void and run off my fork.

▲verst 4 hours ago | parent | prev | next [-]

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)

▲saulpw 3 hours ago | parent [-]

Yeah, I just started auto-closing PRs from new contributors to avoid drive-bys. I want to know that someone actually uses VisiData before they are allowed to propose a change.

▲amiga386 3 hours ago | parent | prev | next [-]

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

▲mceachen 2 hours ago | parent | prev | next [-]

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?

▲jjsullivan5196 2 hours ago | parent [-]

> I have a lot of people telling me what to do and it's exhausting

> Let me be the agent of a trove of people telling you what to do and how to do it

Do you see the problem here?

▲linsomniac 4 hours ago | parent | prev | next [-]

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

▲flatline 4 hours ago | parent | next [-]

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.

▲linsomniac 2 hours ago | parent | next [-]

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

▲zem 3 hours ago | parent | prev | next [-]

how does the presence of those forks contribute to the project's demise in any way?

▲hardbass an hour ago | parent [-]

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.

▲hardbass 3 hours ago | parent | prev [-]

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?

▲yeoldeprogramme 4 hours ago | parent | prev | next [-]

“ 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 4 hours ago | parent | prev | next [-]

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.

▲linsomniac 2 hours ago | parent | next [-]

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.

▲epistasis 3 hours ago | parent | prev [-]

The only attacks possible would be the tools given to the agent.

▲swiftcoder 2 hours ago | parent [-]

Assuming it can't perform a sandbox escape, at any rate. Maybe a Jev-like decision model would be a better idea.

▲epistasis an hour ago | parent [-]

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.

▲matkoniecz 4 hours ago | parent | prev | next [-]

> 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 3 hours ago | parent | prev [-]

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

▲zahlman 2 hours ago | parent | prev | next [-]

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

▲limagnolia 3 hours ago | parent | prev | next [-]

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!

▲tombert 4 hours ago | parent | prev | next [-]

Just make a contributor license agreement based on Benedictine doctrine. At least one very successful FOSS project does that: https://sqlite.org/codeofethics.html

▲BarryMilo 3 hours ago | parent [-]

> First of all, love the Lord God with your whole heart, your whole soul, and your whole strength.

I rolled my eyes so hard I died.

▲passivegains 14 minutes ago | parent [-]

> Devote yourself frequently to prayer.

every time I compile.

▲no_time 4 hours ago | parent | prev | next [-]

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

▲larodi 4 hours ago | parent | prev | next [-]

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?

▲exe34 an hour ago | parent | prev | next [-]

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.

▲awakeasleep 4 hours ago | parent | prev | next [-]

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.

▲dwoldrich 3 hours ago | parent | prev | next [-]

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.

▲groundzeros2015 4 hours ago | parent | prev | next [-]

Just disable PRs

▲ 3 hours ago | parent | prev | next [-]
[deleted]
▲matkoniecz 4 hours ago | parent | prev | next [-]

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

▲stevelacey an hour ago | parent | prev | next [-]

I sent a handful of PRs to rebing/graphql-laravel a few years back, and the ones that got merged were all small and self-contained. A maintainer's scarce resource is review time, not ideas, so anything that makes a diff cheap to judge (one concern per PR, a test, a short explanation of why) counts for more than how clever the change is.

The flood you're describing is the same problem with the cost of writing a patch pushed to zero while the cost of reviewing one stays the same.

▲merth 3 hours ago | parent | prev [-]

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?