linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: "David S. Miller" <davem@redhat.com>, alan@lxorguk.ukuu.org.uk
Cc: greearb@candelatech.com, linux-kernel@vger.kernel.org,
	linux-net@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: networking bugs and bugme.osdl.org
Date: Sun, 29 Jun 2003 19:35:44 -0700	[thread overview]
Message-ID: <17280000.1056940541@[10.10.2.4]> (raw)
In-Reply-To: <20030629.151302.28804993.davem@redhat.com>

--"David S. Miller" <davem@redhat.com> wrote (on Sunday, June 29, 2003 15:13:02 -0700):

>    From: Alan Cox <alan@lxorguk.ukuu.org.uk>
>    Date: 29 Jun 2003 23:07:07 +0100
>    
>    What you don't get is that like you I'm distributing work. I'm
>    getting end users to spot bug correlations - and thats why I want
>    better tools
>
> DaveM:
> I understand this part, it's great sounding in theory.
> 
> But all the examples I've seen are you sifting through bugzilla making
> these correlations.  I've seen no evidence of community participation
> in this activity.

People have been. Maybe not with the networking bugs, but I've seen
people sift through other stuff, and mark off duplicates, and point
out similarities. People go chase attatched patches back into the tree,
and people test fixes they didn't submit the bug for, and report status.
I'd like more of that, but it happens already.
 
> The greatest tools in the world aren't useful if people don't want
> to use them.
> 
> Nobody wants to use tools unless it melds easily into their existing
> daily routine.  This means it must be email based and it must somehow
> work via the existing mailing lists.  It sounds a lot like what I'm
> advocating except that there's some robot monitoring the list
> postings.

Agreed, the interface could be better - we're working on it. It won't
be totally change free, but it could be better integrated. Feedback is
very useful, though it helps a lot of you can pinpoint what's the 
underlying issue rather than "this is crap". Better email integration
is top of the list, starting with sending stuff out to multiple people
when filed, not a single bottleneck point.
 
> But then who monitors and maintains the entries?  That's the big
> problem and I haven't heard a good solution yet.  Going to a web site
> and clicking buttons is not a solution.  That's a waste of time.

There is an army of elves out there, quite capable and willing.
Like most change, it takes a little time, but it's started already.

> AEB:
>
> See, you think you are doing the submitter a favour.
> I prefer the point of view that the submitter does us a favour.
 
Absolutely. Personally, I think testing & communication with users is 
more what we're lacking as a community than coding power. In Dave's 
case, it sounds like he's so swamped, it's not an issue for him. 

However, finding and fixing stuff earlier on will actually reduce
the workload, IMHO. It's a damned sight easier to find a bug you wrote
yesterday than one you wrote last year. I *love* things like nightly
regression testing that reaches out and larts me with a bug report
in < 24 hrs of me screwing things up.

Lastly, I'd rather ditch bug reports based on crap content, or overall
impact, than whether I happened to be busy at the moment they came in.

M.

  reply	other threads:[~2003-06-30  2:22 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-27  5:30 networking bugs and bugme.osdl.org David S. Miller
2003-06-27  5:46 ` Martin J. Bligh
2003-06-27  5:47   ` David S. Miller
2003-06-27  7:59     ` Matti Aarnio
2003-06-27  8:00       ` David S. Miller
2003-06-27 15:00       ` Martin J. Bligh
2003-06-27 14:34     ` Martin J. Bligh
2003-06-27 14:56       ` Davide Libenzi
2003-06-27 21:37         ` David S. Miller
2003-06-27 21:54           ` Ben Greear
2003-06-27 21:54             ` David S. Miller
2003-06-27 22:15               ` Ben Greear
2003-06-27 22:19                 ` David S. Miller
2003-06-27 22:36                   ` Ben Greear
2003-06-28  0:00                     ` David S. Miller
2003-06-28  0:15                       ` Martin J. Bligh
2003-06-28  0:32                         ` David S. Miller
2003-06-28  0:19                       ` Larry McVoy
2003-06-28  0:27                         ` Martin J. Bligh
2003-06-28 19:20                           ` Alan Cox
2003-06-29  0:40                             ` Daniel Jacobowitz
2003-06-29  0:44                             ` Martin J. Bligh
2003-06-27 23:08                   ` Alan Cox
2003-06-28  0:21                     ` David S. Miller
2003-06-28 19:19                       ` Alan Cox
2003-06-28 22:03                         ` David S. Miller
2003-06-28 23:15                           ` Alan Cox
2003-06-28 23:20                             ` David S. Miller
2003-06-28 23:46                               ` Alan Cox
2003-07-12 17:07                           ` Jan Rychter
2003-07-13  4:15                             ` Greg KH
2003-07-14 20:25                               ` USB bugs (was: networking bugs and bugme.osdl.org) Jan Rychter
     [not found]                                 ` <20030714230236.GA7195@kroah.com>
2003-07-15 20:24                                   ` Jan Rychter
2003-07-13  5:22                             ` networking bugs and bugme.osdl.org David S. Miller
2003-07-13  5:42                               ` Jan Rychter
2003-06-27 22:02           ` Davide Libenzi
2003-06-27 21:31             ` Ben Collins
2003-06-27 23:25               ` Andrew Morton
2003-06-27 22:30                 ` Ben Collins
2003-06-28  0:32                   ` Larry McVoy
2003-06-28 19:26                     ` Alan Cox
2003-06-28  0:38                 ` Martin J. Bligh
2003-06-28  1:14                   ` Andrew Morton
2003-06-28  2:13                     ` Martin J. Bligh
2003-06-28  2:35                       ` Andrew Morton
2003-06-28  6:08                         ` Martin J. Bligh
2003-06-28  3:27                       ` Jamal Hadi
2003-06-27 22:02             ` David S. Miller
2003-06-27 22:11               ` Davide Libenzi
2003-06-27 22:13                 ` David S. Miller
2003-06-27 18:50     ` Ben Greear
2003-06-27 21:44       ` David S. Miller
2003-06-27 22:47         ` Martin J. Bligh
2003-06-27 22:53           ` Larry McVoy
2003-06-28  0:44             ` David S. Miller
2003-06-28  0:09           ` David S. Miller
2003-06-27 23:04         ` Alan Cox
2003-06-28  0:19           ` David S. Miller
2003-06-29 21:15           ` David S. Miller
2003-06-29 21:45             ` Andries Brouwer
2003-06-29 21:51               ` David S. Miller
2003-06-29 22:49                 ` Andries Brouwer
2003-06-29 23:21                   ` Davide Libenzi
2003-06-29 22:07             ` Alan Cox
2003-06-29 22:13               ` David S. Miller
2003-06-30  2:35                 ` Martin J. Bligh [this message]
2003-07-20 16:46                   ` Petr Baudis
2003-06-27 15:25 John Bradford
2003-06-27 16:18 Nicolas Mailhot
2003-06-28  8:00 John Bradford
2003-06-28  8:10 John Bradford
2003-06-28 22:37 John Bradford
2003-06-29 22:28 John Bradford

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='17280000.1056940541@[10.10.2.4]' \
    --to=mbligh@aracnet.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davem@redhat.com \
    --cc=greearb@candelatech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).