Tired of Useless bug reports? Dario to the rescue! && Bugday April 4-5 2009
You may have noticed a "Dario Andres" at the top of the bug-closer list for the last... well, a while now. I think he got tired of all the useless plasma backtraces, because he and George Kiagiadakis have been cooking up a rewrite of the crash dialog you get everytime something goes *boom
( Read more... )
>>folk to make the language used more concise, more clear and less unfriendly. e.g.
>>"Are you willing to help the developers?" should be "Can the developers contact you for
>> more information if required?".
>>Language like "You are not willing to help the developers" is very unfriendly and also
>>unclear i.e. sending a report is helping. Change to "You do not want to be contacted about
>>this report".
Yes, I need some help/advice about the texts. Thanks for the suggestions
>>I don't really understand the need for this screen though. Why not just open a window to
>>bugs.kde?
Because bugs.kde.org is not user friendly ;) (joke joke)
We are currently integrating an automatic bugzilla reporting tool for crashes (no need to go to the bugzilla site): and because this can create lots of bug reports with mostly no effort, we need to limit its use. How? Ensuring us that the reports the tool will send to the bugtracker are useful enought and can really help the developers to triage and fix the bug itself.
So we need 1) a *good* backtrace / 2) details / 3) and , if necessary, "willing to help"(help more, after reporting the bug)
Thanks for the comments
Reply
Leave a comment