Comment 5 for bug 1774404

P.S. Just to give you and impression, when I say "guide on how to write good bug report" I mean something along the lines of [1] (there's so much truth to this document!). Written for non-programmers in a way to make them understand how a developer actually works with the provided information and what they can do (and shouldn't do!) in order to help and increase their chances of a fix.

Obviously this is a long document and people are often impatient, too (yes, as a developer I get the exact same feeling when I get a "bad" bug report), so I'm not sure something like this would help either...

[1] https://www.chiark.greenend.org.uk/~sgtatham/bugs.html