Re: [mpowr] Mailing List Management

Alex Rousskov <rousskov@measurement-factory.com> Tue, 23 December 2003 16:59 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27460 for <mpowr-archive@odin.ietf.org>; Tue, 23 Dec 2003 11:59:40 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYpsG-00070p-Up for mpowr-archive@odin.ietf.org; Tue, 23 Dec 2003 11:59:13 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hBNGxCVu026949 for mpowr-archive@odin.ietf.org; Tue, 23 Dec 2003 11:59:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYpsG-00070a-QM for mpowr-web-archive@optimus.ietf.org; Tue, 23 Dec 2003 11:59:12 -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 LAA27428 for <mpowr-web-archive@ietf.org>; Tue, 23 Dec 2003 11:59:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AYpsF-0005Ox-01 for mpowr-web-archive@ietf.org; Tue, 23 Dec 2003 11:59:11 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AYppB-0005Hx-00 for mpowr-web-archive@ietf.org; Tue, 23 Dec 2003 11:56:02 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AYppB-0005Hu-00 for mpowr-web-archive@ietf.org; Tue, 23 Dec 2003 11:56:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYppC-0006uA-1G; Tue, 23 Dec 2003 11:56:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYpoD-0006s2-Ni for mpowr@optimus.ietf.org; Tue, 23 Dec 2003 11:55:01 -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 LAA27269 for <mpowr@ietf.org>; Tue, 23 Dec 2003 11:54:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AYpoC-0005Cp-00 for mpowr@ietf.org; Tue, 23 Dec 2003 11:55:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AYpl1-00058i-00 for mpowr@ietf.org; Tue, 23 Dec 2003 11:51:44 -0500
Received: from measurement-factory.com ([206.168.0.5]) by ietf-mx with esmtp (Exim 4.12) id 1AYpl1-00058f-00 for mpowr@ietf.org; Tue, 23 Dec 2003 11:51:43 -0500
Received: from measurement-factory.com (localhost [127.0.0.1]) by measurement-factory.com (8.12.9/8.12.9) with ESMTP id hBNGpgk3050394; Tue, 23 Dec 2003 09:51:42 -0700 (MST) (envelope-from rousskov@measurement-factory.com)
Received: (from rousskov@localhost) by measurement-factory.com (8.12.9/8.12.9/Submit) id hBNGpgv9050393; Tue, 23 Dec 2003 09:51:42 -0700 (MST) (envelope-from rousskov)
Date: Tue, 23 Dec 2003 09:51:42 -0700 (MST)
From: Alex Rousskov <rousskov@measurement-factory.com>
To: Alex Conta <aconta@txc.com>
cc: MPowr <mpowr@ietf.org>
Subject: Re: [mpowr] Mailing List Management
In-Reply-To: <3FE86D59.8060201@txc.com>
Message-ID: <Pine.BSF.4.53.0312230933510.47938@measurement-factory.com>
References: <011901c3c654$24fdc830$5b6015ac@dclkempt40> <383969298.1071956717@localhost> <3FE86D59.8060201@txc.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, Alex Conta wrote:

> For instance, nobody forces you to read my message.
> If my message is disruptive to you, you could have:
> - ignore it, and further
> - configure a filter to send my messages on this thread, on this
>   list, in this WG, etc.... directly to the TRASH folder.

I had the same thought when reading this thread, but realized that
installing a filter or otherwise ignoring a message is not a complete
solution because it violates WG Chair responsibility to gauge
consensus. If one could ignore or filter only "consensus-unrelated"
messages, then we would have a perfect solution. Unfortunately,
ignoring/filtering based on sender or subject line does not guarantee
that all consensus-related messages will be read.

However, it looks like filtering is a solution for everybody else (but
the Chair). Participants do not have to gauge consensus so they can
ignore whatever they want (and they often do!).


Let's assume that everybody but the Chair are ignoring what they
consider disruptive postings. In most cases, this is likely to solve
the reported problem of disruptive postings blocking technical work.
The poor Chair will have to listen to the lonely/loony voice(s) of the
participant(s) being ignored and gauge consensus. In fact, the Chair
becomes a de facto moderator in this context!

This approach does not violate free speech. As you know, none of the
countries guaranteeing free speech was able to guarantee that the
speech will be heard or have any effect. With the Chair's implied
obligation to listen, we are actually doing slightly better than most
countries advertising their free speech laws!

Can somebody with a real-life disruptive experience comment on this
solution? Would it help in their specific cases?

Alex.

P.S. My understanding is that the Chair is not obligated to
     respond, only listen (to gauge consensus).

_______________________________________________
mpowr mailing list
mpowr@ietf.org
https://www1.ietf.org/mailman/listinfo/mpowr