Nowhere it said you can't argue for your fix/change in an open issue.
Just that once the maintainer close the issue: `So should you get angry and start abusing them? No.`
Edit: And nowhere it makes any comments on how much/little the maintainer should listen to issues just that once he closed it you need to respect it and move on.
I had that. It was unpleasant (to say the least) but on a different situation I rejected a direction. User went elsewhere and we all ended up losing.
I disagree with the attitude expressed there. Don't like it. Build your own. Every maintainer has his style, I don't think that's a constructive style and as a maintainer I never use that style. I might disagree with someone, I will never say fuck off. Even if I think someone should fork, I will offer help with the fork, at least in advice.
Writing the code isn't where it ends. I thank every user who uses my code. Otherwise it's just another code dump. The users are what makes the work worthwhile. To me.
Just that once the maintainer close the issue: `So should you get angry and start abusing them? No.`
Edit: And nowhere it makes any comments on how much/little the maintainer should listen to issues just that once he closed it you need to respect it and move on.