linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: mbligh@aracnet.com
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: Fri, 27 Jun 2003 17:09:07 -0700 (PDT)	[thread overview]
Message-ID: <20030627.170907.71096768.davem@redhat.com> (raw)
In-Reply-To: <1230000.1056754041@[10.10.2.4]>

   From: "Martin J. Bligh" <mbligh@aracnet.com>
   Date: Fri, 27 Jun 2003 15:47:22 -0700

   --"David S. Miller" <davem@redhat.com> wrote (on Friday, June 27, 2003 14:44:26 -0700):
   
   > People DON'T understand.  I _WANT_ them to be able to
   > fall through the cracks.
   
   I fail to see your point here. If that's what you want, then just
   don't look at the bugme data.

bugme bugs persist, when I delete an email it doesn't get deleted
from the bugme database (at least when I go and view it).

Let me draw a diagram for you, say we have 3 contributors A B and
C.  They watch the mailing lists, analyze bugs, and work on new
features.  They work on what they want to, by the very nature of
open-source development.  When a bug hits a mailing list the
following might happen:

	A is overloaded, he deletes the email.
	B has a look, realizes he is not competent in this area
	and deletes the email.
	C analayzes and fixes the bug.

I want A and B to have never again have to deal with this bug
report.  There is zero point in having the capability to "delete"
the email if it persists in some database somewhere, it's not
deleted it's still in the backlog.

If nobody need fear their report get deleted by overload on
the developers, nobody need do anything but be lazy.  And that
system does not work, the contribution must be mutual for this
system to work.

This means that when developers are overloaded they can delete
your report and you'll resend it later.

I don't understand why people have no problem understanding that
this system works when it is in the context of lossy networking
protocols (IPV4) and the things that sit on top to ensure reliable
data delivery via retransmit (TCP), but when this idea is proposed
for things involving people and software development they fall to
fear and doubt.

  parent reply	other threads:[~2003-06-28  0:01 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 [this message]
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
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=20030627.170907.71096768.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=greearb@candelatech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    --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).