3 ms·
I think you have those options on how to react to a feature request: 1. Great idea, I/we will implement it 2. Great idea, Pull Request welcome! 3. Ou
by andix 4y ago
I think you have those options on how to react to a feature request:
1. Great idea, I/we will implement it
2. Great idea, Pull Request welcome!
3. Out of scope, won't be implemented (even if a pull-request is submitted), because ..., /close
4. Out of scope, (no explanation) /close
If you're the single maintainer of a project, it's easy. Write one sentence and just close the issue or pull request.
If you're a team maintaining a project, you need to agree with the team on that, obviously.
But keep in mind: random Github users are just random Giuthub users, random people. Treat them with the respect they deserve. If they don't deserve a lot, just close their issues.
- sanjayio 4y agoI like this as a policy, might give a brief explanation why 4. You might link to a roadmap for example that makes it clear why the Issue isn’t being prioritized.
- andix 4y agoYou can do that, but it’s your project, you decide how to handle it. If you’re too lazy to write a roadmap, just don’t. You don’t owe random people on GitHub anything. Also not an explanation. Especially if they’re not treating you well.