upvote
Personally I’ve been forking a lot more OSS and modifying it for my own use with little regard to contributing back because I haven’t read any of it myself and am not going to make public claims about it. It used to be I’d spend hours or days fixing a bug or adding a feature and getting it merged upstream seemed to help validate that effort. Now there is no effort so no need for validation and I continue on my way.

The commits are in my fork if anyone wants them but I can’t imagine why anyone would.

On the other hand a couple weeks ago I found an annoying bug in a coding agent project and had my agent fix it. It was a very small fix so I could tell it was correct with very little effort. I didn’t open a PR because that required a vouch, but I documented an issue (mostly on my own) and included the patch. I also referenced it in a downstream issue. Then I went to bed. The next morning, I saw a note from downstream thanking me - they’d updated to latest version and the issue was fixed.

The projects bot had reproduced the issue based on my description, tested the fix, validated it, and opened a PR. The maintainer merged it an hour later (it was two lines and obviously correct - easy call with the bots validation) and released it.

It felt like progress.

reply
>> The commits are in my fork if anyone wants them but I can’t imagine why anyone would.

This recently happened with solvespace (I am a maintainer). Someone posted a link to a fork with a bunch of goodies added. I think they just had AI implement some big features that had already been discussed and were either rejected or far future/maybe. That fork still exists but looks to be dead, as there hasn't been any new development since it first appeared. I had a good look at all the commits but I don't see any that I really want to grab as-is. Some of it looked a bit promising though.

I recommend you at least make upstream aware of your fork if there is anything in it that they might want.

reply