I'm really bad at saying no to PRs. I really appreciate people sending contributions, but it's not always right for a project.
miniblog.
Related Posts
Sending patches/PRs to projects creates asymmetric work. The maintainer needs to think about the future work it might create.
Fortunately CI running tests, checking formatting, even enforcing commit message style helps! Reducing the amount of work needed to accept a PR matters.
I love it when a years-old patch eventually gets applied upstream: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=24645
It gives me hope that sending patches is almost always worthwhile!
(These days I have commit access to Emacs too.)
Trellis Modulation https://en.m.wikipedia.org/wiki/Trellis_modulation was a critical modem innovation: it made sending multimedia over telephone lines feasible!