Re: Quality Control and that nasty A word (was: Re: [mpowr] Re: [Solutions] Further work on WG (chair) roles - MPOWR WG proposal)
"James Kempf" <kempf@docomolabs-usa.com> Tue, 16 December 2003 18:04 UTC
Received: from optimus.ietf.org ([132.151.1.19])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25800
for <mpowr-archive@odin.ietf.org>; Tue, 16 Dec 2003 13:04:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
by optimus.ietf.org with esmtp (Exim 4.20) id 1AWJYA-0005j3-El
for mpowr-archive@odin.ietf.org; Tue, 16 Dec 2003 13:04:02 -0500
Received: (from exim@localhost)
by www1.ietf.org (8.12.8/8.12.8/Submit) id hBGI42Pn022003
for mpowr-archive@odin.ietf.org; Tue, 16 Dec 2003 13:04:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
by optimus.ietf.org with esmtp (Exim 4.20) id 1AWJYA-0005io-94
for mpowr-web-archive@optimus.ietf.org; Tue, 16 Dec 2003 13:04:02 -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 NAA25772
for <mpowr-web-archive@ietf.org>; Tue, 16 Dec 2003 13:03:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12)
id 1AWJY8-0004U6-00
for mpowr-web-archive@ietf.org; Tue, 16 Dec 2003 13:04:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
id 1AWJY7-0004Ty-00
for mpowr-web-archive@ietf.org; Tue, 16 Dec 2003 13:04:00 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
by ietf-mx with esmtp (Exim 4.12) id 1AWJY7-0004Tv-00
for mpowr-web-archive@ietf.org; Tue, 16 Dec 2003 13:03:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
by optimus.ietf.org with esmtp (Exim 4.20)
id 1AWJY8-0005iA-GG; Tue, 16 Dec 2003 13:04:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
by optimus.ietf.org with esmtp (Exim 4.20) id 1AWJXH-0005he-Fk
for mpowr@optimus.ietf.org; Tue, 16 Dec 2003 13:03:07 -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 NAA25745
for <mpowr@ietf.org>; Tue, 16 Dec 2003 13:03:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12)
id 1AWJXF-0004Sn-00
for mpowr@ietf.org; Tue, 16 Dec 2003 13:03:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
id 1AWJXE-0004Sf-00
for mpowr@ietf.org; Tue, 16 Dec 2003 13:03:05 -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 1AWJXE-0004Sa-00
for mpowr@ietf.org; Tue, 16 Dec 2003 13:03:04 -0500
Message-ID: <01c501c3c3fe$e61bd8c0$5b6015ac@dclkempt40>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Pete Resnick" <presnick@qualcomm.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>
<p06100708bc04edc5ce9d@[216.43.25.67]>
Subject: Re: Quality Control and that nasty A word (was: Re: [mpowr] Re:
[Solutions] Further work on WG (chair) roles - MPOWR WG proposal)
Date: Tue, 16 Dec 2003 10:03:24 -0800
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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.7 required=5.0 tests=AWL, NO_OBLIGATION autolearn=no
version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Pete,
By "immediate situation" I meant the situation of how the QA process is
handled. By "accountability" I meant how alleged abuses are handled.
Your point about appeal is about "accountability", not about "immediate
situation". These are two different processes, and it would be well not to
confuse them.
I agree with you about "accountability", I don't agree about how to
structure the "immediate situation".
jak
----- Original Message -----
From: "Pete Resnick" <presnick@qualcomm.com>
To: "James Kempf" <kempf@docomolabs-usa.com>
Cc: "Dave Crocker" <dcrocker@brandenburg.com>om>; "MPowr" <mpowr@ietf.org>rg>;
<solutions@alvestrand.no>
Sent: Tuesday, December 16, 2003 9:55 AM
Subject: Re: Quality Control and that nasty A word (was: Re: [mpowr] Re:
[Solutions] Further work on WG (chair) roles - MPOWR WG proposal)
> On 12/16/03 at 8:28 AM -0800, James Kempf wrote:
>
> >So doesn't the fact that the IESG can say "no" make it a hierarchy?
>
> No, it doesn't. For example:
>
> >I fail to see any difference in the immediate situation between an
> >Area Director returning a document to a working group after AD
> >Review and saying "fix this or I'm not going to submit it to the
> >IESG" and a division director saying "fix these bugs or I'm not
> >going to release the software".
>
> Because the development team can't appeal the division director's
> decision, and the development team members cannot initiate the
> process to fire the division director. And moreover, the development
> team cannot decide (with the rest of the departments) to restructure
> the corporation and get rid of the division director.
>
> Also, the division director is under no obligation to negotiate with
> the development team if the development team disagrees with the
> division director. The division director has no responsibility to try
> to resolve disputes, even if it is a nice thing to do.
>
> >Of course, there are differences in accountability. The division
> >director is only accountable to his VP while the AD is accountable
> >to the community. As I've said in other emails, *that* means that
> >should WG chairs be given more - it you don't like the word
> >"authority" call it something else, maybe "X stuff" - then there
> >needs to be a similar accountability mechanism for them.
> [emphasis added]
>
> First of all, *what* means that chairs should be given more
> authority? I don't see how that follows from anything you've said.
> (And I *do* think we're talking about authority here; no need to call
> it "X stuff".)
>
> Second of all, accountability is *not* the only difference between
> the division director and the AD; the entire set of responsibilities
> is similarly different.
>
> >No sane person is going to take the responsibility to do something
> >without the authority to get it done.
>
> You've said that twice now and I'm still at a loss to know what
> you're talking about. It sounds like a catch phrase. What
> responsibility have we given (or do we want to give) to an AD or to a
> WG chair for which we haven't given them the authority to get it
> done? An AD has the responsibility to review documents coming out of
> working groups. Chairs have the responsibility to make sure that
> consensus is reached on all open document issues. We're talking about
> giving chairs the responsibility to collect technical reviews early
> in the process and to do a technical writeup at the end of the
> process. Yes, for all of these responsibilities, the ADs and chairs
> should know that the community has the authority to overrule them.
> But how does that equate to not having the authority to get those
> things done? Does the prospect of appeal or recall prevent ADs from
> pushing back on WGs? Does the prospect of appeal or recall prevent a
> chair from invoking 2026 to say, "Let's try to bring this set of open
> issues from the review to consensus"?
>
> >One argument some have made against giving the WG chairs more X
> >stuff is that we don't get very good people as WG chairs.
>
> Straw man. I've certainly never said that.
>
> >If they aren't given the X stuff to match their responsibility,
> >we'll get even worse.
>
> So effectively you're saying that power is the only reward for which
> good chairs will work. I've not found that to be the case.
>
> pr
> --
> Pete Resnick <http://www.qualcomm.com/~presnick/>
> QUALCOMM Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102
>
_______________________________________________
mpowr mailing list
mpowr@ietf.org
https://www1.ietf.org/mailman/listinfo/mpowr
- [Mpowr] RE: [Solutions] Further work on WG (chair… Margaret.Wasserman
- [mpowr] Re: [Solutions] Further work on WG (chair… Pete Resnick
- [mpowr] RE: [Solutions] Further work on WG (chair… Margaret.Wasserman
- [mpowr] Re: [Solutions] Further work on WG (chair… Ted Hardie
- [mpowr] RE: [Solutions] Further work on WG (chair… Margaret.Wasserman
- [mpowr] Re: [Solutions] Further work on WG (chair… James Kempf
- [mpowr] RE: [Solutions] Further work on WG (chair… Scott Bradner
- [mpowr] RE: [Solutions] Further work on WG (chair… Scott Bradner
- [mpowr] Re: [Solutions] Further work on WG (chair… Pete Resnick
- [mpowr] Re: [Solutions] Further work on WG (chair… Henrik Levkowetz
- [mpowr] Re: [Solutions] Further work on WG (chair… Melinda Shore
- [mpowr] RE: [Solutions] Further work on WG (chair… Margaret.Wasserman
- [mpowr] RE: [Solutions] Further work on WG (chair… john.loughney
- [mpowr] RE: [Solutions] Further work on WG (chair… john.loughney
- [mpowr] Re: [Solutions] Further work on WG (chair… Keith Moore
- [mpowr] Re: [Solutions] Further work on WG (chair… James Kempf
- [mpowr] Re: [Solutions] Further work on WG (chair… Dave Crocker
- [mpowr] Re: [Solutions] Further work on WG (chair… Dave Crocker
- [mpowr] Re: [Solutions] Further work on WG (chair… Pete Resnick
- Re: [mpowr] Re: [Solutions] Further work on WG (c… James Kempf
- Re: [mpowr] Re: [Solutions] Further work on WG (c… Pete Resnick
- Re: [mpowr] Re: [Solutions] Further work on WG (c… James Kempf
- Re: [mpowr] Re: [Solutions] Further work on WG (c… Pete Resnick
- Quality Control and that nasty A word (was: Re: [… James Kempf
- Re: [mpowr] Re: [Solutions] Further work on WG (c… Steve Coya
- Re: [mpowr] Re: [Solutions] Further work on WG (c… Dave Crocker
- Re: [mpowr] Re: [Solutions] Further work on WG (c… Keith Moore
- Re: Quality Control and that nasty A word (was: R… Pete Resnick
- [mpowr] Re: Quality Control and that nasty A word Lucy E. Lynch
- Re: Quality Control and that nasty A word (was: R… James Kempf
- [mpowr] Re: Quality Control and that nasty A word James Kempf
- Re: Quality Control and that nasty A word (was: R… James Kempf
- Re: Quality Control and that nasty A word (was: R… Dave Crocker
- [mpowr] Re: Quality Control and that nasty A word James Kempf
- Re: [mpowr] Re: Quality Control and that nasty A … Pekka Savola
- [mpowr] Troops versus superpower Alex Rousskov
- [mpowr] Re: Quality Control and that nasty A word Alex Conta
- Re: [Solutions] Re: [mpowr] Re: Quality Control a… Alex Conta
- Re: [Solutions] Re: [mpowr] Re: Quality Control a… David Meyer
- Re: [Solutions] Re: [mpowr] Re: Quality Control a… Alex Rousskov
- Re: [Solutions] Re: [mpowr] Re: Quality Control a… David Meyer
- Re: [Solutions] Re: [mpowr] Re: Quality Control a… Alex Conta
- Re: [Solutions] Re: [mpowr] Re: Quality Control a… Alex Rousskov
- Re: [Solutions] Re: [mpowr] Re: Quality Control a… David Meyer
- Re: [Solutions] Re: [mpowr] Re: Quality Control a… David Meyer
- Re: Quality Control and that nasty A word (was: R… Dave Crocker
- Re: Quality Control and that nasty A word (was: R… Dave Crocker
- [mpowr] Re: [Solutions] Further work on WG (chair… Alex Conta
- Re: [mpowr] Re: [Solutions] Further work on WG (c… Alex Conta
- [mpowr] Re: Quality Control and that nasty A word Alex Conta