The suggestions posted here (give a quote, say no, say you are not interested) are part of a larger, useful guideline: Respond by specifying clearly what would

The suggestions posted here (give a quote, say no, say you are not interested) are part of a larger, useful guideline: Respond by specifying clearly what would be required for this feature to land in your code. This can be money, this can be someone stepping up to do it and maintain it, this can be technical requirements under which you can see this go into your framework. Yes, users opening issues are demanding, but as a github repo owner you can ask for anything as well and put up barriers that the user needs to solve to see it happen. They may be motivated too. Specifying clearly the problems and what is needed to overcome them leads the user to appreciate you more. It will sharpen your thinking on why exactly you are saying no. And sometimes you will be surprised by someone actually making you happy by meeting your requirements.