I have written a draft for the Reporting Bugs guide

[Dario Ruellan]

We do not want more people to open bugs. We want more people to open
*good* bugs reports. Reports that can be worked out by triagers,
maintainers, developers. This means the reports must be more on the
complete side. More on the technical side. Less on the "it did not
work". The triagers will complete the details.

But I can guarantee you that a extremely vague bug will be left aside.
Which, BTW, I think is wrong: it should be closed INVALID (no actual
data provided).

>
> And the second question is "would the proposed draft allow most
> people to report bugs?"

Yes, it will. And therein lies the danger. It is NOT easy to write an
usable bug report. Why should it be easy to write a bad one?

Excellent answer. Then, we can assume that we are not looking for a
simplification of the process, but a way to better organize the topics, and
perhaps add an introduction with things you must do before reporting, like
update, make sure it IS a bug, and identify a system or an app bug.