Re: Bugzilla bug tracking database for 2.5 now available.

["David S. Miller" <davem@redhat.com>]

   From: "Martin J. Bligh" <mbligh@aracnet.com>
   Date: Fri, 15 Nov 2002 14:11:56 -0800

   Right, but look at the flip side ... once that bug has been logged
   in bugzilla, the person who would have emailed lkml now has an easily
   searchable interface, and could have found the bug, found out what the
   patch for it was, and fixed it themselves, without ever bothering you,
   lkml, or anyone. I'm not saying that'll happen 100% of the time, but 
   it should help overall ... will just take a short period whilst data 
   builds up.
   
I'm more concerned about the inevitable explosion of duplicates
and "fixed already"'s.

This is why a lot of people warned early on, and were wary about,
having someone full time managing and watching over this bug database.
It is specifically to deal with dups and things of this nature.

I don't want to be concerned about spending each morning closing a
screenful of dups or "fixed already" reports.  Then the bug database
isn't helping me, it's rather making more work for me.

This work is someone else's job.  On linux-kernel, we have a "someone
else" to do this already, the entire readership of linux-kernel. :-)

In bugzilla however, all of this work now must be done by whoever at
OSDL is watching over the bugzilla database all day long and _ME_.
That is an inefficient use of resources.

Even if the whole readership of linux-kernel moved over and started
watching over the bug database as they do now with the lists, that
still leaves tons of work for me because only I can click on the
"CLOSE" button for the bug report.  I want the whole readership of
linux-kernel to have this capability, to close the bug.  This way I
can do what I do with linux-kernel when I'm just too damn busy to read
that day's posting, hit the big delete key.