Re: [mpowr] Mailing List Management
Alex Conta <aconta@txc.com> Fri, 19 December 2003 20:11 UTC
Received: from optimus.ietf.org ([132.151.1.19])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24037
for <mpowr-archive@odin.ietf.org>; Fri, 19 Dec 2003 15:11:54 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
by optimus.ietf.org with esmtp (Exim 4.20) id 1AXQxr-0001nv-T7
for mpowr-archive@odin.ietf.org; Fri, 19 Dec 2003 15:11:12 -0500
Received: (from exim@localhost)
by www1.ietf.org (8.12.8/8.12.8/Submit) id hBJKBBFO006935
for mpowr-archive@odin.ietf.org; Fri, 19 Dec 2003 15:11:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
by optimus.ietf.org with esmtp (Exim 4.20) id 1AXQxr-0001nm-KB
for mpowr-web-archive@optimus.ietf.org; Fri, 19 Dec 2003 15:11:11 -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 PAA23938
for <mpowr-web-archive@ietf.org>; Fri, 19 Dec 2003 15:11:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12)
id 1AXQxo-00006l-00
for mpowr-web-archive@ietf.org; Fri, 19 Dec 2003 15:11:08 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
id 1AXQxf-00004d-00
for mpowr-web-archive@ietf.org; Fri, 19 Dec 2003 15:11:07 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
by ietf-mx with esmtp (Exim 4.12) id 1AXQxf-00004Y-00
for mpowr-web-archive@ietf.org; Fri, 19 Dec 2003 15:10:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
by optimus.ietf.org with esmtp (Exim 4.20)
id 1AXQxh-0001lN-67; Fri, 19 Dec 2003 15:11:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
by optimus.ietf.org with esmtp (Exim 4.20) id 1AXQwz-0001kL-8f
for mpowr@optimus.ietf.org; Fri, 19 Dec 2003 15:10:17 -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 PAA23794
for <mpowr@ietf.org>; Fri, 19 Dec 2003 15:10:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12)
id 1AXQww-00001f-00
for mpowr@ietf.org; Fri, 19 Dec 2003 15:10:14 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
id 1AXQwu-00001X-00
for mpowr@ietf.org; Fri, 19 Dec 2003 15:10:13 -0500
Received: from transfire.txc.com ([208.5.237.254] helo=pguin2.txc.com)
by ietf-mx with esmtp (Exim 4.12) id 1AXQwu-00001S-00
for mpowr@ietf.org; Fri, 19 Dec 2003 15:10:12 -0500
Received: from txc.com ([172.17.0.134])
by pguin2.txc.com (8.11.2/8.11.2) with ESMTP id hBJKA8014580;
Fri, 19 Dec 2003 15:10:08 -0500
Message-ID: <3FE35B1F.2000308@txc.com>
Date: Fri, 19 Dec 2003 15:10:07 -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: MPowr <mpowr@ietf.org>
Subject: Re: [mpowr] Mailing List Management
References: <011901c3c654$24fdc830$5b6015ac@dclkempt40>
In-Reply-To: <011901c3c654$24fdc830$5b6015ac@dclkempt40>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature";
micalg=sha1; boundary="------------ms080901020205030905090501"
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
jak, I am very sympathetic with your experience. But, I fundamentally disagree with this proposal. Please see further comments - sorry if they are repetition of what was already said before on this topic: James Kempf wrote: > Margaret's draft proposes letting WG chairs manage mailing list membership, > rather than requiring the IESG to do it as is currently the case. From my > experience as a WG chair, I can say that there is nothing as effective in > derailing a WG as a disruptive mailing list participant, and once such a > disruption occurs, it is often difficult to get any good technical work out > of the WG because the really good technical people simply leave. I am sorry, I cannot agree with such a brute force solution. As IETF has gained over the years such a large international Email attendance, with a unequaled diversity of backgrounds, traditions, educations, opinions, interests, ideas, etc... it should put no barriers to the free expression of ideas, or opinions pertaining to the topics of a WG work. IETF is an OPEN standard, and that is a BIG difference with the other competing SDOs, which have more or even more stringent rules about their mailing lists. Freedom of speech, and free access is one of the characteristics that makes IETF OPEN. Taking away the freedom of speech should have the very high threshold, if not higher than that of today's. > I've also > been told by other WG chairs who have tried that the IESG is extremely > reluctant to remove someone from a mailing list, even if the evidence of > disruption is quite apparent. Hm, that's a browny point for IESG. On the other hand, I think IESG should have helped you resolve the crisis in the WG by other means. Have you asked for other type of help from IESG, other than stopping Email access? This sounds like a typical technical conflict resolution problem, for which there is a science and professionals, who would be glad to help. > I suspect that is why this proposal was a > crowd pleaser when brought up at the plenary in Minneapolis. > > However, there have been some concerns expressed. Scott Bradner mentioned > the potential of a liability problem, and Alex Contra mentioned the problem > of chair abuse. It is Alex Conta. There were other earlier voices on the "solutions" list. Please check. > The latter would presumably be when a chair designates as > "disruptive" someone who is honestly but persistently expressing an opinion > on technical matters that is contrary to what the chair believes should be > part of the WG's documents. Clearly, there's a boundary here between > disruption and honest disagreement, but the boundary is not always clear. > That's is exactly the reason why, if we do anything now, that should be to raise the threshold even higher. > Suppose that in order to join an IETF WG mailing list, a person would have > to agree to a mailing list "Code of Conduct" by clicking through a page that > describes it. The "Code of Conduct" could be checked by lawyers to make sure > it can be defensible legally, as would the signup procedure. And it would > mean that the mailing list would need to be hosted somewhere that could > support a more elaborate signup procedure than today. I wonder what would you put in the code of conduct regarding a technical controversy, or regarding technical content disagreement? > Then, when a WG chair > believes that a participant is being disruptive, (s)he would send three > email messages privately to the particpant, cc'ing the AD, with specific > evidence, in the form of emails, posting statistics (for people who are > spamming the list), etc., requesting the participant to cease. If the three > email messages don't work, the WG chair would then discuss the matter with > the AD and, with the AD's approval (sent as an email message to the WG > chair), the chair would send email to the participant that his/her posting > privileges were being revoked for a three month period. The participant > could appeal to the IESG if (s)he felt that (s)he was being treated > unfairly. > > Comments? > In my opinion, the reluctance of IESG to grant requests of shutting off people from the mailing list, who are within the boundaries of technical content, is wise. Alex > 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