> Pick one open source tool you use. [...] Spend a weekend fixing it
Beware: Your best path forward there may be, contrary to part of the thesis in this post, be to vibe code a replacement. There are a couple reasons why:
Expect to encounter significant push-back due to AI contribution. For example, I've had bug fixes to significant problems be rejected because "we are in the future going to be adopting a no-AI policy". Annoying because I spent my time working on it because they did not have a no-AI policy. Amusing to have another contributor contribute the exact same fix, like character for character, under a new PR (referencing my issue, so not done in isolation) and get it accepted.
There may also need to be sweeping changes to the project you are fixing -- which are going to be a burden to the maintainer and likely wouldn't be accepted because of that. A fork may be the way to go here, but also "vibe coding" a replacement might be the best option.
Earlier this year I build a replacement apt cache called apt-cacher-ultra. Part of it was because the existing apt-cachers had reliability issues, but a bigger part was I wanted something that would survive ubuntu.com being under a DDoS for a week or two. apt-cacher-ng was totally useless at that. The path I wanted to try was to have verified known good snapshots of the upstream, background refreshes, pre-fetching of known "hot" packages when the upstream refreshed. HUGE changes.
I've put 100 hours or more into this "vibe coded" alternative (mostly enhancements and fixes for other users use cases). I'm pretty confident that this wouldn't have been something the apt-cacher-ng or apt-cacher maintainers would have been interested in accepting.