RFC: Automatic trouble reporting
Johan Walles
walles at mailblocks.com
Wed Feb 2 01:54:09 CST 2005
Now that I think about it some more, the client-side should be what
needs implementing first. To begin with, the actual results could just
as well go to a mailing list or whatever. Finding a good way of
analyzing the result might be easier once you get to look at some real
data :-).
Regards //Johan
-----Original Message-----
From: Jeff Waugh <jeff.waugh at ubuntu.com>
To: ubuntu-devel at lists.ubuntu.com
Sent: Sun, 30 Jan 2005 23:10:45 +1100
Subject: Re: RFC: Automatic trouble reporting
> Regarding Bugzilla, it is (IMO) a very nice tool for manual bug
reporting,
> but it isn't very well suited for statistics gathering. It won't
answer
> the question "which program in Ubuntu crashes the most?" or "Was the
new
> release of X.Org's ATI driver any better than the previous one?".
There are plenty of modifications such as these on other bugzilla-based
systems, such as GNOME's "find duplicate crasher bugs" scripts. The
rest of
it is just reporting.
> On the server side, I imagine the results should be presented as a
> high-score list, roughly like Debian's Popularity contest. That would
> give you a "profile" of what parts of Ubuntu need attention.
Bugzilla provides good reporting on the stuff it does already. :-)
----------------------------------------------
Mailblocks - A Better Way to Do Email
http://about.mailblocks.com/info
More information about the ubuntu-devel
mailing list