| ▲ | ryandrake 24 minutes ago | |
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. | ||