A lot of novice users file bugs  that tend to be long, rambling, and full of irrelevant information, which makes them hard to parse. We may benefit from using a standard template in the description field that guided users through how to format a reasonable bug report, like this:



SUMMARY
<One sentence summary of the bug>

STEPS TO REPRODUCE
1. <First, I did this>
2. <Then I did that>
3. <And then I did this other thing>


EXPECTED RESULT
<Here's what I wanted to happen>


ACTUAL RESULT
<Here's what actually happened>


REPRODUCIBILITY
<Here are the configurations/software versions/Linux distros/conditions under which it doesn't happen>


ADDITIONAL INFORMATION
<Logs and other information that may be helpful>



Any specific products and components should of course be free to tweak or override it.