Bug#242419: general: need for a webbased BTS
Scripsit Jesus Climent <email@example.com>
> Setting a web page where a user could, with some php/python/whatever code in
> the background, put a sensible bug report for whichever tool he is using and
> report it using simple, guided steps, is not a bad thing.
If the user is incapable of communicating via email, there is no way
to ask him supplementary questions to help narrow down what the bug is
and how to fix it. Then he might as well not have filed the bug - it
will most likely be tagged moreinfo and, after a number of years or
months have passed, be closed in someone's spring cleaning.
Yes, there *are* users who are capable of getting a useful bug report
together in the first try, such that they don't need being asked
questions. But I have a hard time imagining a user with that much clue
who nevertheless is incapable of sending an email.
> You cannot expect all users to learn everything to report a bug. Putting such
> barriers to users just endangers us to learn the user needs, and blinds our
> eyes from focusing on their needs.
If the user is incapable of communicating by email, the chances are
narrow indeed that we will be able to learn anything from him.
> The social contract states that we are to help our users,
The social contract does nowhere state that we need to make it easy to
file bugreports that are useless because the submitter cannot be
> Feel free to close such bugs if they are use- or senseless.
EVERY bug filed by a user who cannot be contacted to clarify later is
useless. Why should we waste effort to get them into the system only
to be closed without any action?
Henning Makholm "Jeg køber intet af Sulla, og selv om uordenen griber
planmæssigt om sig, så er vi endnu ikke nået dertil hvor
ordentlige mennesker kan tillade sig at stjæle slaver fra
hinanden. Så er det ligegyldigt, hvor stærke, politiske modstandere vi er."