yeah, I understand the practical side of the problem and is certainly not easy as you say. as for issue templates, reporting guidelines etc., they make it even less likely that people report a problem. as the article mentions, even on a project that encouraged feedback it was still not reported that it doesn't run on the mac. so my takeaway is that there shouldn't be any guidelines for issue reporting if someone wants to catch even a glimpse of the real issues. I'd say there should be a good process in line that deals with the issues and asks for necessary information afterwards, so potential reporters are not driven away by issue requirements. knowing this I'd say projects that have issue guidelines hurt themselves in the end.