Depending on the issues effected, I'd shut off comments/issues until the social media storm is over.
If it's a longer term issue, then throw up a Discourse/forum instance somewhere and close any effected issues with a comment along the lines of "go talk about it here, where you won't negatively effect development work."
You could also just turn off GitHub issues and move to a different system. Maybe make all new issues go into a forum/google group, and then when a valid issue comes along, allow a contributor to create a issue on GitHub.
Off topic: I think there's a huge opportunity for someone to shake up how support requests/bug reports/issues/tickets/etc. work. Part of that would be building tools that help developers manage support requests while still being newbie friendly. As well as issues like social media pressure. If anyone's working on something like that, I'd love to give feedback. I've had ideas on the subject, but haven't had the time to pursue it myself.
Comments
Depending on the issues effected, I'd shut off comments/issues until the social media storm is over.
If it's a longer term issue, then throw up a Discourse/forum instance somewhere and close any effected issues with a comment along the lines of "go talk about it here, where you won't negatively effect development work."
You could also just turn off GitHub issues and move to a different system. Maybe make all new issues go into a forum/google group, and then when a valid issue comes along, allow a contributor to create a issue on GitHub.
Off topic: I think there's a huge opportunity for someone to shake up how support requests/bug reports/issues/tickets/etc. work. Part of that would be building tools that help developers manage support requests while still being newbie friendly. As well as issues like social media pressure. If anyone's working on something like that, I'd love to give feedback. I've had ideas on the subject, but haven't had the time to pursue it myself.