I have to deal with that frequently and would say, it really depends what you want.
Do you think the issue is useful but you don't want to implement it? Keep the feature request open and say you're open to contributions (or maybe getting paid to implement it).
Do you think it's out of scope and shouldn't get implemented? Say that, close the issue and lock it if people keep discussing.
I can also recommend creating response templates for these things. Be clear and assertive, back and forth wastes everyones time and just leads to more frustration on both sides.
Do you think the issue is useful but you don't want to implement it? Keep the feature request open and say you're open to contributions (or maybe getting paid to implement it).
Do you think it's out of scope and shouldn't get implemented? Say that, close the issue and lock it if people keep discussing.
I can also recommend creating response templates for these things. Be clear and assertive, back and forth wastes everyones time and just leads to more frustration on both sides.