RE: [mpowr] Mailing List Management
Alex Rousskov <rousskov@measurement-factory.com> Tue, 23 December 2003 20:46 UTC
Received: from optimus.ietf.org ([132.151.1.19])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09034
for <mpowr-archive@odin.ietf.org>; Tue, 23 Dec 2003 15:46:14 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
by optimus.ietf.org with esmtp (Exim 4.20) id 1AYtPW-0000Ha-L7
for mpowr-archive@odin.ietf.org; Tue, 23 Dec 2003 15:45:46 -0500
Received: (from exim@localhost)
by www1.ietf.org (8.12.8/8.12.8/Submit) id hBNKjkLW001082
for mpowr-archive@odin.ietf.org; Tue, 23 Dec 2003 15:45:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
by optimus.ietf.org with esmtp (Exim 4.20) id 1AYtPW-0000HN-Gv
for mpowr-web-archive@optimus.ietf.org; Tue, 23 Dec 2003 15:45:46 -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 PAA09007
for <mpowr-web-archive@ietf.org>; Tue, 23 Dec 2003 15:45:44 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12)
id 1AYtPV-0002Ju-00
for mpowr-web-archive@ietf.org; Tue, 23 Dec 2003 15:45:45 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
id 1AYtNe-0002G8-00
for mpowr-web-archive@ietf.org; Tue, 23 Dec 2003 15:43:50 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
by ietf-mx with esmtp (Exim 4.12) id 1AYtLr-0002CD-00
for mpowr-web-archive@ietf.org; Tue, 23 Dec 2003 15:41:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
by optimus.ietf.org with esmtp (Exim 4.20)
id 1AYtLs-0000Am-Id; Tue, 23 Dec 2003 15:42:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
by optimus.ietf.org with esmtp (Exim 4.20) id 1AYtLi-0000AX-Qs
for mpowr@optimus.ietf.org; Tue, 23 Dec 2003 15:41:50 -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 PAA08848
for <mpowr@ietf.org>; Tue, 23 Dec 2003 15:41:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12)
id 1AYtLh-0002An-00
for mpowr@ietf.org; Tue, 23 Dec 2003 15:41:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
id 1AYtJw-00027I-00
for mpowr@ietf.org; Tue, 23 Dec 2003 15:40:01 -0500
Received: from measurement-factory.com ([206.168.0.5])
by ietf-mx with esmtp (Exim 4.12) id 1AYtJE-00022P-00
for mpowr@ietf.org; Tue, 23 Dec 2003 15:39:16 -0500
Received: from measurement-factory.com (localhost [127.0.0.1])
by measurement-factory.com (8.12.9/8.12.9) with ESMTP id hBNKdFk3060185;
Tue, 23 Dec 2003 13:39:15 -0700 (MST)
(envelope-from rousskov@measurement-factory.com)
Received: (from rousskov@localhost)
by measurement-factory.com (8.12.9/8.12.9/Submit) id hBNKdFmA060184;
Tue, 23 Dec 2003 13:39:15 -0700 (MST) (envelope-from rousskov)
Date: Tue, 23 Dec 2003 13:39:15 -0700 (MST)
From: Alex Rousskov <rousskov@measurement-factory.com>
To: Margaret.Wasserman@nokia.com
cc: mpowr@ietf.org
Subject: RE: [mpowr] Mailing List Management
In-Reply-To: <E320A8529CF07E4C967ECC2F380B0CF9027E46C3@bsebe001.americas.nokia.com>
Message-ID: <Pine.BSF.4.53.0312231318390.47938@measurement-factory.com>
References: <E320A8529CF07E4C967ECC2F380B0CF9027E46C3@bsebe001.americas.nokia.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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=none autolearn=no version=2.60
On Tue, 23 Dec 2003 Margaret.Wasserman@nokia.com wrote: > The problem with the "filter e-mail" approach is simple: it doesn't > work for new people. If our task were to eliminate 100% of what the Chair considers "disruptive" postings to 100% of participants, then you would be right. Since our task, I think, is to prevent serious disruptions, the problem you are implying is not a big deal (it does not create serious disruptions). > How will a new person know who to filter? Newbies should read the archives for the last month or so (at least). They can be advised by old timers as well. > Will the new person give up on a WG before he discovers that > everyone in the group is filtering a certain set of (sometimes) > disruptive posters? Possibly. Such a person is probably not very interested in a working group to start with (did not read the archives and got discouraged by 10 e-mails from the same participant). > Will new peoples' good ideas get filtered out if they share them in > response to the wrong person? The Chair will not filter out any ideas and can advise accordingly. The above can only happen if somebody filters based on subject alone, (which is their right to do and they get the effect they wanted). > It is important that we have constructive and orderly mailing lists, > especially in an environment where we often say that the "real work" > is done via e-mail. Agreed. > We wouldn't tolerate clearly disruptive behaviour (threats, personal > invective, repeated off-topic or out-of-scope comments, etc.) in a > face-to-face meeting, so why would we be willing to tolerate this > behaviour on our mailing lists? Hm... We wouldn't? I wonder how you would deal with such behavior in a face-to-face meeting. Call the police? Since we cannot define what disruptive is, we should be very careful with making any formal rules with this undefined term. Immediate suspension does not sound like a "very careful" approach to me. Furthermore, the filtering suggestion does not tolerate disruptive behaviour. It makes it invisible to all but the Chair. > Freedom of speech does not give people the right to use our > resources (mail servers, disk space, etc.) to send their messages. > Our mailing lists exist for the purpose of conducting constructive > work within the IETF, and we should be able to revoke the posting > privileges (and _yes_, I do mean "privileges") of people who disrupt > our work. Yes, but the argument seems to be revolving around _how_ such "privileges" can be revoked, not whether they can be revoked. Alex. _______________________________________________ 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