lkml.org 
[lkml]   [2003]   [Jul]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: networking bugs and bugme.osdl.org
Date
>>>>> "David" == David S Miller <davem@redhat.com> writes:
David> From: Alan Cox <alan@lxorguk.ukuu.org.uk> Date: 28 Jun 2003
David> 20:19:32 +0100

David> On Sad, 2003-06-28 at 01:21, David S. Miller wrote:
>> I respond to private reports with "please send this to the lists,
>> what if I were on vacation for the next month?" I never actually
>> process or analyze such reports.

David> Which means you miss stuff.

David> Not my problem Alan. If the user gives a crap about their
David> report mattering, they'll do what I ask them to do. If users
David> send their report to the wrong place, it will get lost, just
David> like if their cat their report into /dev/null. I have no reason
David> to feel bad about the information getting lost.

David> If it's too much for them to do as I ask, it's too much for me
David> to consider their report.
[...]

I think this is one of the largest problems of the current Linux
development model.

Many people seem to divide people into 'users' (who aren't particularly
useful) and 'developers', who actually do something. People (like me),
who can devote a _little_ time to narrowing down and reporting bugs fall
into the 'user-whiner' class. And get ignored.

What results is that you only get bug reports from active
developers. Which means that rare bugs don't get fixed.

David> It is not a dream, it works perfectly fine and has done so for
David> 5+ years of Linux maintainence.

It hasn't. The result is a system that works for you (and other active
developers), but not for everyone. As an example -- try running Linux on
a modern laptop, connecting some USB devices, using ACPI, or
bluetooth. Observe the resulting problems and crashes. You'll hit loads
of obscure bugs that have been reported, but never got looked at in
detail. I certainly have hit them and reported most, and most got
dropped in various places.

Does this mean these are unimportant bugs? No. This does indeed mean
(following your thinking) that these aren't important bugs for me. I
have worked around them in various ways, some involving actually buying
new hardware, or not using certain features at all. And the cycle will
go on -- others will hit the bugs, report them once, see them dropped,
move on.

David> Let's see, what makes more sense from my perspective. Should I
David> reward and put forth effort for the people who fart a bug report
David> onto the lists and expect everyone to stop what they're doing
David> and fix the bug, or should I reward and put forth effort for the
David> guy who spent the time to put together a stellar bug report and
David> also doesn't mind retransmitting it from time to time whilst
David> everyone is busy?

Interesting you should think you're 'rewarding' people. I thought your
goal was to have fun working on cool software and making it
better. I also thought I had the same goal as a bug-reporter.

When I write software, I care about every bug report and consider people
doing the reporting a very valuable resource.

--J.
[unhandled content-type:application/pgp-signature]
\
 
 \ /
  Last update: 2005-03-22 13:46    [W:0.120 / U:0.068 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site