I think there might be value in creating a “Maintainer’s Cookbook” of socially appropriate phrases that they can use to decline interest in feature requests, te

I think there might be value in creating a “Maintainer’s Cookbook” of socially appropriate phrases that they can use to decline interest in feature requests, technical support, pull requests, bug reports, etc. “That looks like an excellent feature! Good work, thanks for showing it to me :)” [pull request closed] “I’m sorry to hear that it’s not working out for you. If you’re able to work out what went wrong, feel free to post an update.” [closes issue] “That’s an unfortunate flaw to have encountered. It doesn’t come up in my usage, but I agree with your diagnosis. If you end up fixing it in your own fork, please do mention this issue.” [closes issue] And an accompanying “Open source user guide” that covers the basics (much of which I don’t know today) “How to fork, repackage, and replace an upstream Node dependency when you’re trying to fix a bug” “When is it appropriate to submit an issue/feature/pull request?” “How do I upvote something I want to see an open source author do for me?” etc.