netpoetica
commented
10 years ago :+1: This is a very good idea - recommend to close or "vote to close" type of thing would be really helpful. I just received one that was most likely some sort of spam, because the ask was completely unclear and it was a self-referenced issue: https://github.com/joyent/node/issues/5256
Sometimes during the question answering, it becomes clear that an issue should be closed. For example, in joyent/node#4327 Isaac already said that the status code would only be added once it is standardized, and the draft has expired.
At that point, it is a "won't fix" issue, so questions like "is this still in an issue in 0.10" aren't relevant. Maybe there could be a shortcut to suggest the issue be closed? We could tell the triager that they need to explain the reason it should be closed in the issue.