I am not sure why you've been so heavily downvoted, other than "lots of people disagree".
Perhaps if bug-lists are so awful to read (and I have no doubt that they are) then the people reading them need more [close] buttons.
[close - no ref to standard]; [close - no test example code]; etc, and these provide templated replies that ask people for correct reports.
"We closed this bug. You MUST provide a clear reference to the specification showing how $THING is non-compliant.
AND
you MUST provide a test example code snippet".
This would help de-stress people reading the bugs, and might prompt people providing bugs to provide correct information.
I agree that templates are often hateful nasty things - templates on Wikipedia are really nasty approach. But here the alternative is, well, also pretty unpleasant for some people.
Yeah, the more information you require the less likely people are to fill it in.
I've been a fan of "search" not categorise for bugs for this reason. People are more likely to blog about, or tweet about a bug than put it into a bug tracker.
The role of an issue gardener is a really useful one too. A person whose job it is to go into issues, and make them useful for developers. To communicate with all sides, and enhance the process for everyone.
A great example of this is when @pyalot tested out various webgl implementations on different browsers. Then he went to all the bug trackers, and made notes. Then linked to various specifications, and pointed to test cases.
This one guy through this has done a massive service to WebGL and the web. I've seen too often various bugs and issues go through 2-3 browser iterations because that's how long it takes for people to seriously test out features and report bugs.
The collaboration going on now because of open bug trackers in web browsers is amazing.
Perhaps if bug-lists are so awful to read (and I have no doubt that they are) then the people reading them need more [close] buttons.
[close - no ref to standard]; [close - no test example code]; etc, and these provide templated replies that ask people for correct reports.
"We closed this bug. You MUST provide a clear reference to the specification showing how $THING is non-compliant.
AND
you MUST provide a test example code snippet".
This would help de-stress people reading the bugs, and might prompt people providing bugs to provide correct information.
I agree that templates are often hateful nasty things - templates on Wikipedia are really nasty approach. But here the alternative is, well, also pretty unpleasant for some people.