[mpowr] Re: Quality Control and that nasty A word

"James Kempf" <kempf@docomolabs-usa.com> Wed, 17 December 2003 16:33 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18530 for <mpowr-archive@odin.ietf.org>; Wed, 17 Dec 2003 11:33:46 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AWebt-0001oV-Ge for mpowr-archive@odin.ietf.org; Wed, 17 Dec 2003 11:33:18 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hBHGXHCf006970 for mpowr-archive@odin.ietf.org; Wed, 17 Dec 2003 11:33:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AWebt-0001oL-An for mpowr-web-archive@optimus.ietf.org; Wed, 17 Dec 2003 11:33: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 LAA18508 for <mpowr-web-archive@ietf.org>; Wed, 17 Dec 2003 11:33:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AWebs-0005S8-00 for mpowr-web-archive@ietf.org; Wed, 17 Dec 2003 11:33:16 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AWebp-0005RU-00 for mpowr-web-archive@ietf.org; Wed, 17 Dec 2003 11:33:15 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AWebp-0005Qh-00 for mpowr-web-archive@ietf.org; Wed, 17 Dec 2003 11:33:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AWebd-0001nh-8i; Wed, 17 Dec 2003 11:33:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AWebT-0001nJ-BP for mpowr@optimus.ietf.org; Wed, 17 Dec 2003 11:32: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 LAA18481 for <mpowr@ietf.org>; Wed, 17 Dec 2003 11:32:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AWebI-0005Pr-00 for mpowr@ietf.org; Wed, 17 Dec 2003 11:32:40 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AWeas-0005PY-00 for mpowr@ietf.org; Wed, 17 Dec 2003 11:32:14 -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 1AWear-0005P4-00 for mpowr@ietf.org; Wed, 17 Dec 2003 11:32:14 -0500
Message-ID: <004701c3c4bb$501e5740$5b6015ac@dclkempt40>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Alex Conta" <aconta@txc.com>
Cc: "Dave Crocker" <dcrocker@brandenburg.com>, "MPowr" <mpowr@ietf.org>, <solutions@alvestrand.no>
References: <20031209220238.172C19B30A@newdev.harvard.edu> <p06100601bbfd472cc28e@[216.43.25.67]> <028201c3c0fb$332bd220$666015ac@dclkempt40> <165181922.20031215084442@brandenburg.com> <030a01c3c330$cf260dd0$5b6015ac@dclkempt40> <p0610070cbc03a6fb3741@[216.43.25.67]> <041c01c3c34d$7050d6b0$5b6015ac@dclkempt40> <209066081.20031215141412@brandenburg.com> <04ac01c3c363$48b42510$5b6015ac@dclkempt40> <p06100707bc041a2434e6@[216.43.25.67]> <004e01c3c3f1$af209a70$5b6015ac@dclkempt40> <319857739.20031216121114@brandenburg.com> <02c601c3c420$45177a70$5b6015ac@dclkempt40> <3FDFB128.8040107@txc.com>
Date: Wed, 17 Dec 2003 08:32:07 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [mpowr] Re: Quality Control and that nasty A word
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.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> > As mentioned earlier, new proposed WG charters are starting to have
quality
> > assurance plans. Suppose the IESG were to require that a charter contain
a
> > QA plan before the charter is approved. Thus, the WG is taking
> > responsibility for quality by proposing the QA plan, the IESG is judging
> > whether the plan is likely to succeed (from their presumably broader
> > experience) by approving the charter or suggesting changes, and the
chair
> > has the responsibility for carrying the QA plan out, with the authority
> > (relevance, etc.) granted to him/her by the WG through the charter.
>
> As long as the chair can be also a developer, this process is
> fundamentally weak, and prone to play just as a tool for promoting
> the chair's, and chairs friends' work.
>

Sorry, Alex, but I don't understand what this has to do with figuring out a
mechanism whereby QA can be effective, while, at the same time, reducing
IESG workload and ensuring that the responsibility for QA rests with the WG.

> > [...]
> > Would this satisfy your concerns?
> >
> >                 jak
>
> Not mine. Sorry for jumping in.
>

Could you explain a little more? What exactly do you mean by the chair being
a "developer"? If you read Margaret's draft (which I presume you did, since
you're commenting on this thread) then you know that she has proposed that
chairs are no longer allowed to be authors or editors of drafts, except for
a limited period during which they are in transition between one role and
another. So, if that's what you mean by being a "developer", that particular
concern would be covered if that part of Margaret's draft is instituted. As
for the chair's friends, it is up to the IESG to pick someone who can
abstract themselves from purely partisan concerns and act as a moderator in
the tussles that inevitably arise during standardization. If the chair does
not fufill that role, then it is the responsibility of the WG to appeal to
the AD to remove the chair.

Perhaps there needs to be a statement to this effect in 2026bis?

            jak


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