lists.openwall.net   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  linux-hardening  linux-cve-announce  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]
Message-ID: <46350240.6070605@simon.arlott.org.uk>
Date:	Sun, 29 Apr 2007 21:38:24 +0100
From:	Simon Arlott <simon@...e.lp0.eu>
To:	Andi Kleen <andi@...stfloor.org>
CC:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Adrian Bunk <bunk@...sta.de>,
	Diego Calleja <diegocg@...il.com>,
	Chuck Ebbert <cebbert@...hat.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 2.6.21

On 29/04/07 19:09, Andi Kleen wrote:
>>  - a lot of reporters will not use bugzilla, because it's damn 
>>    inconvenient even for reporting. If you propose something that uses 
> 
> Don't think that's true. There are plenty of projects who only
> accept bugs through bugzilla (mozilla, various distributions, etc.) 
> and I don't see any evidence of your claim being true.

These projects are probably losing plenty of trivial bug reports 
from people who shouldn't have to register with a bug tracker and 
fill in a long form every time to submit a short bug report.

> Sure there will be always people who cannot be bothered
> to use any kind of interface for bugs, but then

Most of the time bugzilla appears to be a great way to ignore 
bugs. Every large project seems to have one with bugs that 
stay open for years - bugzilla's own inability to quick search 
without javascript[1] being a good example (it's fixed now). 
If no one can get around to fixing reported bugs why should 
anyone bother submitting more?

They even released their software with a link to the bug if 
you tried to do a quick search without javascript:
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=70907
"THIS BUG IS FIXED IN BUGZILLA 2.22. D..."

> these are unlikely to stay on board during a longer 
> remote debugging q'n'a session either. So those people
> can be just ignored; they essentially don't exist in
> the bug report universe.

How will the people you ignore get their bugs fixed?

> I don't think the "keep it in Andrew's/Adrian's head" method
> is going to scale longer term at least (and one of them has 
> already thrown in the towel) 

People are doing something about this, at least for tracking 
the regressions at http://kernelnewbies.org/known_regressions 
(which is read-only unless you register, people have already 
commented on this).

> The "send it to a gigantic mailing list and hope someone catches
> it" method also doesn't seem to be that great. At least there
> are lots of lost reports in my experience this way.

I have had experience of this with the dvb mailing list (this was 
a couple of months before their news post referencing bugzilla 
too), even when I included a patch to fix it.

Someone suggested another way to fix a bug and I replied that it 
worked - that fix never went anywhere else and other people could 
be having the same problem today because it's still not been 
applied anywhere. (I will submit a -1 +1 patch myself when 
I have time this week).

> I suspect the real reason is more "Linus doesn't like web interfaces
> for no particular good reason". Not much can be done about that.
> Well perhaps someone can write a gopher based bugzilla interface 
> or something to solve that instead @) 

Bugzilla's advanced search interface is far too crowded, that 
should be clear to anyone. The simpler search usually isn't much 
use because either it finds too many bugs or "zarro boogs" and 
you're left wondering if the bug is there or not.

-- 
Simon Arlott
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ