Re: [patch] scsi: revert "[SCSI] Get rid of scsi_cmnd->done"

On Sun, Jan 06, 2008 at 08:10:44PM +0100, Willy Tarreau wrote:
On Sun, Jan 06, 2008 at 08:56:25PM +0200, Adrian Bunk wrote:
On Sun, Jan 06, 2008 at 07:34:02PM +0100, Willy Tarreau wrote:
...
As to using bugzilla for bug tracking... Well, I agree that bug
tracking is important when you work on multiple problems at once.
But bugzilla should be the developer's tool, not the end user's.
That means that it should only be our job to create entries there
if end users find it too difficult, and that we should just invite
them to *try* to report there to save us some time.

Where does this opinion end users would find Bugzilla too difficult come
from? Many other projects use Bugzilla without big problems.

Is this just plain FUD or based on real reports from end users?
In the latter case, please give pointers to them so that whatever
problems exist can be fixed.

I, as an end user of ntpd, have been harrassed to use it to get an
ntp bug reported "because by mail it would get lost". What complicated

Noone knows how many thousand bug reports have never reached lkml
since majordomo silently dropped them.

This is the price for having lkml relatively spam-free.

an interface it is when you don't know it ! I remember I wanted to
attach a patch and it didn't even get through the first time. I did
it wrong. Blame me if you want, but an interface which need training
for proper use is certainly not for casual end users.

What exactly is the problem with attaching files?
What is "it didn't even get through the first time" exactly?

Also, it's very annoying to have to create an account somewhere, leaving
there one of the passwords you use on many other sites, just to help a
random developer fix a bug in his code. You quickly wonder if someone
else will report it and have more patience.

If you already lack patience at this point, would you be willing to
bisect which requires more than a dozen kernel recompiles and reboots?

Another recent example: a coworker recently told me he installed the
latest beta from ubuntu, and that he had some problems with his WIFI
randomly hanging. I asked him if he filed a bug, he replied me "no,
it's too much boring, I'm not the only one with this hardware, others
have certainly already done it". When the release went out, he insisted
telling me he was right not filing the bug because indeed it was fixed !

He wouldn't have sent a bug report no matter how to report it.

We must accept that end users :
1) do not like creating accounts (remember or divulgate passwords,
and risk of getting spam)

Send _one_ email to lkml and you'll get forever spam to this address.

With one email addresses of mine exactly that happened.

2) do not know how to classify their problem, and are not even
sure it's a real bug. On the first page, when uncertain they
would probably click "Other". Adding doubt in the reporter's
mind is counter-productive as it will refrain him from being
precise about what he did to get the problem.

If the bug ends at Other/Other that's not a problem - this usually gets
fixed within a few hours.

3) are not familiar with our vocabulary :
- "Tree" : mainline? mm? mjb? ac? what's that ?
- "Component" : Configuration? LSM? Modules? Other?

Then let's improve that.

=> finally, I'm not sure I had to click "Other" in the first place,
I want to choose something else, I click "Back" and I get back
to the login page! Bye bye.

Works fine here.

Did you disable cookies?

Also :
"No binary modules - NVIDIA users this means YOU!"
=> about half the reporters will wonder if they should stop here
or not. Most of those with an NVidia chipset and/or graphics
card will wonder, while the bug may still interest us.

Then sugggest a better text.

At least, on the mailing list, there's no real rules, the mail will
be posted anyway. And if the user gets flamed, at least we have the
report.
...

If majordomo didn't drop it.

And if it didn't get ignored and forgotten.

Regards,
Willy

cu
Adrian

--

"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 majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Re: Mantis package bombs
    ... for you to report problems in the place that's most accommodating ... things to bugzilla personally. ... implied when I described the bug as "outstanding" rather than "still ... if a bug is likely to be an upstream bug (not ...
    (Fedora)
  • Re: [patch] scsi: revert "[SCSI] Get rid of scsi_cmnd->done"
    ... This bug was actually hidden in bugzilla for ages, ... The bugzilla just tracked a bug reported to lkml. ... "if you have a problem with the Linux kernel, then report it to lkml" ...
    (Linux-Kernel)
  • Re: [patch] scsi: revert "[SCSI] Get rid of scsi_cmnd->done"
    ... Noone knows how many thousand bug reports have never reached lkml ... filing or get back to terminate the report. ... But I would like kernel people to become less egocentric ... Send _one_ email to lkml and you'll get forever spam to this address. ...
    (Linux-Kernel)
  • Re: 2.6.25-rc8: FTP transfer errors
    ... Yes, Mark, we used to do things that way for every bug in the kernel. ... We should be very careful about git-bisect. ... the developers, because when they think they might have fixed it, ... But I know that a report is a report, and even if I have a ...
    (Linux-Kernel)
  • Re: [patch] scsi: revert "[SCSI] Get rid of scsi_cmnd->done"
    ... movement into this bug was ... ... The problem is that mailing lists are far too often equivalent to ... And another of the advantages of using Bugzilla is that it gives us ... tracking tool, but it's a bloody useless workflow one for actually ...
    (Linux-Kernel)