3 ms·
Done incorrectly, this can sound passive aggressive, but I suggest adding a short notice in your README: - Feature requests should follow ((list your rules)).
by dictum 9y ago
Done incorrectly, this can sound passive aggressive, but I suggest adding a short notice in your README:
- Feature requests should follow ((list your rules)). All requests that don't follow the rules will be ((closed|ignored))
- ((The maintainers of this project)) will only add new features ((at their leisure)). If you cannot contribute a pull request for ((feature X)), make a feature request ((following the rules on item 1)) and wait. Please do not be impatient.
- If you can implement ((feature X)), please do so and open a pull request.
My personal experience is that dealing with third-party code, merge conflicts and waiting for responses can be even more draining than writing code, so there's that.
- usrusr 9y agoReorder to make the second bullet the first: people are prone to feeling entitled to their feature after jumping through all those hoops, don't give them the chance to stop reading at that point.
- j_s 9y agoCan you provide a link to an example of doing this or something similar?
- subatomic 9y agoIf you mean something like contribution guidelines, then they're everywhere. Here's one of mine as an example: https://github.com/benhowell/react-grid-gallery/blob/master/.github/contributing.md https://github.com/benhowell/react-grid-gallery/blob/master/...
- icelancer 9y agoI do this at work in my social media channels and such. I clearly state the rules of engagement and delete 99.999% of communication that doesn't fit the list. (Sometimes I'll answer communication from those who don't get it right, almost always they are high-profiled individuals you occasionally have to break a rule for. [I also usually regret it. Maybe I'll learn someday.])