Re: [mpowr] Mailing List Management
"James Kempf" <kempf@docomolabs-usa.com> Tue, 23 December 2003 17:56 UTC
Received: from optimus.ietf.org ([132.151.1.19])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28936
for <mpowr-archive@odin.ietf.org>; Tue, 23 Dec 2003 12:56:17 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
by optimus.ietf.org with esmtp (Exim 4.20) id 1AYql5-0000mu-5Z
for mpowr-archive@odin.ietf.org; Tue, 23 Dec 2003 12:55:51 -0500
Received: (from exim@localhost)
by www1.ietf.org (8.12.8/8.12.8/Submit) id hBNHtp7s003022
for mpowr-archive@odin.ietf.org; Tue, 23 Dec 2003 12:55:51 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
by optimus.ietf.org with esmtp (Exim 4.20) id 1AYql5-0000mf-1d
for mpowr-web-archive@optimus.ietf.org; Tue, 23 Dec 2003 12:55:51 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28890
for <mpowr-web-archive@ietf.org>; Tue, 23 Dec 2003 12:55:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12)
id 1AYql3-00071d-00
for mpowr-web-archive@ietf.org; Tue, 23 Dec 2003 12:55:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
id 1AYqkI-0006xG-00
for mpowr-web-archive@ietf.org; Tue, 23 Dec 2003 12:55:09 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
by ietf-mx with esmtp (Exim 4.12) id 1AYqkI-0006xB-00
for mpowr-web-archive@ietf.org; Tue, 23 Dec 2003 12:55:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
by optimus.ietf.org with esmtp (Exim 4.20)
id 1AYqkJ-0000jo-1w; Tue, 23 Dec 2003 12:55:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
by optimus.ietf.org with esmtp (Exim 4.20) id 1AYqkB-0000iq-PC
for mpowr@optimus.ietf.org; Tue, 23 Dec 2003 12:54:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28769
for <mpowr@ietf.org>; Tue, 23 Dec 2003 12:54:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12)
id 1AYqkA-0006ur-00
for mpowr@ietf.org; Tue, 23 Dec 2003 12:54:54 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
id 1AYqie-0006uI-00
for mpowr@ietf.org; Tue, 23 Dec 2003 12:53:20 -0500
Received: from key1.docomolabs-usa.com
([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
by ietf-mx with esmtp (Exim 4.12) id 1AYqid-0006uD-00
for mpowr@ietf.org; Tue, 23 Dec 2003 12:53:19 -0500
Message-ID: <2ccf01c3c97d$b5993ec0$5b6015ac@dclkempt40>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Alex Rousskov" <rousskov@measurement-factory.com>
Cc: "MPowr" <mpowr@ietf.org>
References: <011901c3c654$24fdc830$5b6015ac@dclkempt40>
<383969298.1071956717@localhost> <3FE86D59.8060201@txc.com>
<Pine.BSF.4.53.0312230933510.47938@measurement-factory.com>
<2ca901c3c97b$347b1db0$5b6015ac@dclkempt40>
<Pine.BSF.4.53.0312231037030.47938@measurement-factory.com>
Subject: Re: [mpowr] Mailing List Management
Date: Tue, 23 Dec 2003 09:53:45 -0800
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: mpowr-admin@ietf.org
Errors-To: mpowr-admin@ietf.org
X-BeenThere: mpowr@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpowr>,
<mailto:mpowr-request@ietf.org?subject=unsubscribe>
List-Id: Management Positions -- Oversight, Work and Results <mpowr.ietf.org>
List-Post: <mailto:mpowr@ietf.org>
List-Help: <mailto:mpowr-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpowr>,
<mailto:mpowr-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on
ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Alex,
> > I've had experience with disruptive participants on mailing lists, and
the
> > answer is, no it would not help.
> >
> > The problem is that when a disruptor appears, the good technical people
tend
> > to leave.
>
> Could the good technical people be quickly advised by more experienced
> IETFers (e.g., the Chair) to setup a simple filter? Sure, some e-mails
> will still get through, but if the good technical people care enough
> about the WG work, it seems like a small price to pay to stay involved
> in that work.
>
So I guess I don't see any difference between the chair sending out email
saying "filter this guy's email" and the chair removing the person from the
list, except from a theoretical standpoint. The net effect is the same:
nobody reads the disruptor's email. Also, I'm not sure I agree that everyone
should be forced into the inconvenience of having to modify their spam
filters just so that a single person can continue to post.
The other problem with this is that I would presume that the chairs and the
disruptor, with participation of the AD, would undergo some kind of private
discussion about the disruptor's behavior with the intent that the disruptor
could be readmitted to the list when they've cleaned up their act, so to
speak. The removal is not meant to permanently disable posting rights, after
all. If the problem is handled by having everyone put the disruptor's name
in the spam filter, then the chair has to send out an email saying "all
right, X has agreed to be a good boy/girl, you can take him out of your spam
filter now". Perhaps this kind of public humiliation would serve as a
deterrent, but I think it more likely that quiet negotiation and
reintroduction of the person into the WG community in a less intrusive way
would be preferable.
jak
_______________________________________________
mpowr mailing list
mpowr@ietf.org
https://www1.ietf.org/mailman/listinfo/mpowr
- [mpowr] Mailing List Management James Kempf
- RE: [mpowr] Mailing List Management Margaret.Wasserman
- Re: [mpowr] Mailing List Management Alex Rousskov
- Re: [mpowr] Mailing List Management Alex Conta
- Re: [mpowr] Mailing List Management James Kempf
- Re: [mpowr] Mailing List Management Alex Conta
- RE: [mpowr] Mailing List Management Alex Rousskov
- Re: [mpowr] Mailing List Management Spencer Dawkins
- Re: [mpowr] Mailing List Management Harald Tveit Alvestrand
- Re: [mpowr] Mailing List Management John C Klensin
- Re: [mpowr] Mailing List Management Alex Conta
- Re: [mpowr] Mailing List Management Alex Rousskov
- Re: [mpowr] Mailing List Management Alex Conta
- Re: [mpowr] Mailing List Management James Kempf
- Re: [mpowr] Mailing List Management Alex Rousskov
- Re: [mpowr] Mailing List Management James Kempf
- Re: [mpowr] Mailing List Management Melinda Shore
- Re: [mpowr] Mailing List Management Alex Rousskov
- Re: [mpowr] Mailing List Management James Kempf
- RE: [mpowr] Mailing List Management Margaret.Wasserman
- RE: [mpowr] Mailing List Management Margaret.Wasserman
- RE: [mpowr] Mailing List Management Alex Rousskov
- Re: [mpowr] Mailing List Management Alex Rousskov
- Re: [mpowr] Mailing List Management James Kempf
- RE: [mpowr] Mailing List Management John C Klensin
- Re: [mpowr] Mailing List Management Spencer Dawkins
- RE: [mpowr] Mailing List Management Margaret.Wasserman
- Re: [mpowr] Mailing List Management Alex Conta
- Re: [mpowr] Mailing List Management Alex Conta
- Re: [mpowr] Mailing List Management Spencer Dawkins
- RE: [mpowr] Mailing List Management John C Klensin
- RFC Editor doc approvals (RE: [mpowr] Mailing Lis… Harald Tveit Alvestrand
- Re: RFC Editor doc approvals (RE: [mpowr] Mailing… John C Klensin
- Re: RFC Editor doc approvals (RE: [mpowr] Mailing… Harald Tveit Alvestrand
- Re: RFC Editor doc approvals (RE: [mpowr] Mailing… Dave Crocker
- Re: [mpowr] Mailing List Management Harald Tveit Alvestrand
- Re: [mpowr] Mailing List Management Alex Rousskov
- Re: [mpowr] Mailing List Management Harald Tveit Alvestrand
- Re: [mpowr] Mailing List Management Alex Rousskov
- Re: [mpowr] Mailing List Management John C Klensin
- Re: Re: [mpowr] Mailing List Management Dave Crocker
- Re: [mpowr] Mailing List Management Alex Rousskov