Re: [mpowr] Mailing List Management

Alex Conta <aconta@txc.com> Wed, 24 December 2003 00:52 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA22110 for <mpowr-archive@odin.ietf.org>; Tue, 23 Dec 2003 19:52:11 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYxFW-0000hg-5i for mpowr-archive@odin.ietf.org; Tue, 23 Dec 2003 19:51:42 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hBO0pg7N002698 for mpowr-archive@odin.ietf.org; Tue, 23 Dec 2003 19:51:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYxFW-0000hR-0s for mpowr-web-archive@optimus.ietf.org; Tue, 23 Dec 2003 19:51:42 -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 TAA22095 for <mpowr-web-archive@ietf.org>; Tue, 23 Dec 2003 19:51:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AYxFU-0007WX-00 for mpowr-web-archive@ietf.org; Tue, 23 Dec 2003 19:51:40 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AYxDb-0007VJ-00 for mpowr-web-archive@ietf.org; Tue, 23 Dec 2003 19:49:44 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AYxBv-0007To-00 for mpowr-web-archive@ietf.org; Tue, 23 Dec 2003 19:47:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYxBw-0000bz-NY; Tue, 23 Dec 2003 19:48:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYxBn-0000bY-3E for mpowr@optimus.ietf.org; Tue, 23 Dec 2003 19:47: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 TAA22014 for <mpowr@ietf.org>; Tue, 23 Dec 2003 19:47:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AYxBj-0007Sn-00 for mpowr@ietf.org; Tue, 23 Dec 2003 19:47:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AYx9n-0007QC-00 for mpowr@ietf.org; Tue, 23 Dec 2003 19:45:47 -0500
Received: from transfire.txc.com ([208.5.237.254] helo=pguin2.txc.com) by ietf-mx with esmtp (Exim 4.12) id 1AYx8H-0007O7-00 for mpowr@ietf.org; Tue, 23 Dec 2003 19:44:14 -0500
Received: from txc.com ([172.18.253.134]) by pguin2.txc.com (8.11.2/8.11.2) with ESMTP id hBO0iB020543; Tue, 23 Dec 2003 19:44:11 -0500
Message-ID: <3FE8E154.9040601@txc.com>
Date: Tue, 23 Dec 2003 19:44:04 -0500
From: Alex Conta <aconta@txc.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031208
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: James Kempf <kempf@docomolabs-usa.com>
CC: Alex Rousskov <rousskov@measurement-factory.com>, MPowr <mpowr@ietf.org>
Subject: Re: [mpowr] Mailing List Management
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>
In-Reply-To: <2ca901c3c97b$347b1db0$5b6015ac@dclkempt40>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms000603050907090706030305"
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

James Kempf wrote:

>[...] 
> 
> The problem is that when a disruptor appears, the good technical people tend
> to leave. [...]

I have never seen this happen, and it is hard to imagine such dynamics: 
  people's interest is the work in a WG, how can it be the mailing list? 
Can you point to an Email archive that would show this?

> Unfortunately, this does require a
> judgement call on the part of the chair and the AD, and its possible that
> they might judge wrong. 

If I think of analogies to daily life, it is nightmarish.

> That's why it is necessary to have an appeals
> process for people who feel they've been treated unfairly. 

The appeal will be innefective, because the incentive is to uphold the 
decisions.

> From the
> experience I've had and talking with other WG chairs who have had similar
> experiences, I feel that the risk of losing a WG to mailing list disruption
> is much higher than having an autocratic chair that shuts someone out just
> because they have a different technical opinion. Actually, I've never seen
> an instance of the latter, and I know of at least two cases of the former.

I am confused. How could you see the latter, since the rule is not yet 
in effect.

> So I believe that allowing the WG chair and AD to remove mailing list
> participants with the particpant allowed to appeal to the IESG if they feel
> treated unfairly is the right way to go. I believe that both WG chairs
> should agree if there are co-chairs for the WG, and the AD should be
> consulted.

If this consultation is to take place, why not to leave the decision to 
the ADs, as it is today?

> However, I'm still undecided about whether the WG chairs should be allowed
> to remove someone if the AD doesn't respond quickly enough, as John Klensin
> has proposed. On the one hand, I see the need for speed, having experienced
> the problems a lag can cause when an AD is busy elsewhere. 

What lag? Can you be more explicit? I asked this before, and no one 
explained why it is necessary to have a quick action?

> On the other, I
> believe the risk is much higher that a WG chair may make a wrong judgement
> call if AD approval is not required.
> 

I would feel more comfortable if the WG chair would make a proposal and 
the decision would be taken by the ADs.

We could attach a time limit for the ADs action, to resolve the issue of 
  IESG not acting, although I think the no action, is caused by the 
uncomfort to take such decisions.

Alex C.

>             jak
>