lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sun, 25 Nov 2007 22:36:40 +0100
From:	Adrian Bunk <>
To:	"Rafael J. Wysocki" <>
Cc:	Bartlomiej Zolnierkiewicz <>,,,
	Andrew Morton <>,
	Natalie Protasevich <>
Subject: Re: kernel bugzilla is FPOS (was: Re: "buggy cmd640" message
	followed by soft lockup)

On Sun, Nov 25, 2007 at 10:28:06PM +0100, Rafael J. Wysocki wrote:
> On Sunday, 25 of November 2007, Adrian Bunk wrote:
> > First of all, Bugzilla is a quite often used bug tracker in the open 
> > source world [1], so many users already know it.
> > 
> > But more important, "it pretends to require them to spend" isn't true 
> > because there's no pretending - we actually often require bug reporters 
> > to spend a lot of time on the bug report (e.g. when asking for 
> > bisecting).
> But not *initially*.
> We should not confuse *debugging* with *reporting bugs*.  While the former is
> actually more difficult and more time consuming than writing the code in which
> the bug is present, the latter should be as simple as sending an email.

For hardcore geeks like you and me sending an email might be easier than 
using some web interface.

Normal humans tend to be more accustomed to web interfaces, and 
following the instructions on some web page is _much_ easier than 
reading three text files for knowing what to write in an email.

> > I'm also sometimes writing bug reports in different areas, and in my 
> > experience it doesn't matter whether it's web-based Bugzilla, the 
> > email-based Debian bug tracker or whatever else system - the time spent 
> > on a good bug report is not spend on pasting the text whereever or on 
> > clicking on a few boxes, the time is spent on tracking the issue down 
> > and writing a good bug report.
> Apparently, you are expecting the reporters do *debug* problems, while they need
> not be aware of how to do that.
> IMHO, we should make reporting problems as simple as reasonably possible and

Agreed, and as said above simple = web interface.

> > What matters for a bug reporter is to get a solution for his problem 
> > within a reasonable amount of time.
> Still, it's annoying if you attach tons of information to the report and that
> information does not turn out to be useful.


> > > Also, some developers do not consider the Bugzilla as a useful thing and
> > > wouldn't like to use it (which is why this thread has appeared, among other
> > > things ;-)).
> > >...
> > 
> > And that's part of the problem.
> > 
> > Bugzilla is a usable tool, but it isn't the only tool available.
> > 
> > If there was one tool all developers would be willing to use that would 
> > be a reason why we should switch to whatever tool this is.
> The choice of the tool should be a result of the choice of a *method*.  IOW,
> we have to know our needs and choose the tool that satisfies them or write one
> if it doesn't exist.
> For now, IMHO, we don't really know what we need.

Even worse:
Different people have different opinions what they need and what they 
don't want...

> Greetings,
> Rafael



       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists