<html><head></head><body>Good ideas, if anyone actually implements it. A couple of comments.<br>
<br>
Most users are not programmers - they will not know how to recogize similear backtraces are the same root cause. Worse I know of many cases where I - a programmer - was wrong.<br>
<br>
The more automated detection we can do the better. In fact many random crashes have been traced down to the same root cause, so we really need the ability to check the user's config in a distribution specific way. If some misconfiguration is found we can ignore the backtrace.<br>
<br>
Keep privacy in mind as well.<br>
<br>
Since I'm not offering to do the painting I'll step away from the bikeshed now.<br>
-- <br>
Sent from my Android phone with K-9 Mail. Please excuse my brevity.<br><br><div class="gmail_quote">Niko Sams <niko.sams@gmail.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre style="white-space: pre-wrap; word-wrap:break-word; font-family: sans-serif">Hi,<br /><br />I'd like to talk about an idea on how DrKonqi (which is a really<br />useful thing btw) could be<br />further improved.<br />In short: DrKonqi shouldn't create bugs directly but talk to a "layer" between.<br /><br />DrKonqi -> <a href="http://crashes.kde.org">crashes.kde.org</a> -> <a href="http://bugs.kde.org">bugs.kde.org</a><br /><br /><a href="http://crashes.kde.org">crashes.kde.org</a> is a new web application - a bit similar to bugzilla:<br />- lists all reported crashes with intelligent filtering duplicates<br />- developers can set duplicates<br />- developers can link a crash to a bug (or create automatically a bug<br />for a crash)<br />- developers can enter a solution (that will be presented to the user<br />that hits this crash)<br /> eg.:<br /> - "update to version x.y"<br /> - "temporary workaround: don't click button x"<br /> - "you missconfi
gured
x, see <a href="http://y.com">http://y.com</a> how to fix"<br /> - "the developers are aware of this issue but have not yet fixed<br />it, see <a href="http://bugs.kde.org">http://bugs.kde.org</a>/... for details"<br /> - "the bug is fixed but an update has not yet been released.<br />Update to version x.y once it released."<br />- comments can be added by users and developers (to ask how to reproduce etc)<br /><br />For the end user there could be the following scenarios:<br />- user posts the crash, <a href="http://crashes.kde.org">crashes.kde.org</a> finds a duplicate crash in<br />it's database and will tell the<br /> user on how to proceed (see possible solutions above)<br />- user posts the crash, <a href="http://crashes.kde.org">crashes.kde.org</a> can't find an exact duplicate<br />and will show the user<br /> all possible duplicates<br />- user posts the crash, <a href="http://crashes.kde.org">crashes.kde.org</a> doesn't find a duplicate. User<br />gets t
he
possibility to<br /> subscribe to updates for this crash to get an email when a solution<br />for his crash was entered<br /> by the developers<br /><br />One big difference in implementation I would propose:<br />DrKonqi makes a *single* POST to <a href="http://crashes.kde.org">crashes.kde.org</a> including all<br />information and then just shows<br />a WebView where the server side can do anything. That gives greater<br />independence of the used<br />KDE version and changes on the server side.<br /><br />Advantages over current solution:<br />- <a href="http://bugs.kde.org">bugs.kde.org</a> isn't filled with duplicates<br />- <a href="http://crashes.kde.org">crashes.kde.org</a> can be specialized on crashes<br />- sending a crash would not only help developers fixing that bug but<br />also help the user by showing<br /> a solution for his issue.<br /><br />What software could <a href="http://crashes.kde.org">crashes.kde.org</a> run? I'm not sure, maybe a<br />bugzilla
installation or something<br />custom written. Or some other bugtracking software.<br /><br />So, what do you think?<br />Niko<br /></pre></blockquote></div></body></html>