Re: [Pesci-discuss] For whom it may concern..
Thomas Narten <narten@us.ibm.com> Mon, 14 November 2005 13:40 UTC
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EbeZP-0001f7-1b; Mon, 14 Nov 2005 08:40:27 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EbeZN-0001f2-7c for pesci-discuss@megatron.ietf.org; Mon, 14 Nov 2005 08:40:25 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20987 for <pesci-discuss@ietf.org>; Mon, 14 Nov 2005 08:39:51 -0500 (EST)
Received: from e35.co.us.ibm.com ([32.97.110.153]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EbeqL-0004ON-KE for pesci-discuss@ietf.org; Mon, 14 Nov 2005 08:57:59 -0500
Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com [9.17.195.11]) by e35.co.us.ibm.com (8.12.11/8.12.11) with ESMTP id jAEDe7ij027896 for <pesci-discuss@ietf.org>; Mon, 14 Nov 2005 08:40:07 -0500
Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by westrelay02.boulder.ibm.com (8.12.10/NCO/VERS6.8) with ESMTP id jAEDdsge037982 for <pesci-discuss@ietf.org>; Mon, 14 Nov 2005 06:39:56 -0700
Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1]) by d03av02.boulder.ibm.com (8.12.11/8.13.3) with ESMTP id jAEDe44l014257 for <pesci-discuss@ietf.org>; Mon, 14 Nov 2005 06:40:04 -0700
Received: from cichlid.raleigh.ibm.com (sig-9-65-244-126.mts.ibm.com [9.65.244.126]) by d03av02.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id jAEDdv7V013575; Mon, 14 Nov 2005 06:40:02 -0700
Received: from cichlid.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by cichlid.raleigh.ibm.com (8.13.1/8.12.5) with ESMTP id jAEDdkkK009413; Mon, 14 Nov 2005 08:39:48 -0500
Message-Id: <200511141339.jAEDdkkK009413@cichlid.raleigh.ibm.com>
To: Pekka Savola <pekkas@netcore.fi>
Subject: Re: [Pesci-discuss] For whom it may concern..
In-Reply-To: Message from Pekka Savola <pekkas@netcore.fi> of "Fri, 11 Nov 2005 00:59:56 +0200." <Pine.LNX.4.64.0511110032110.899@netcore.fi>
Date: Mon, 14 Nov 2005 08:39:46 -0500
From: Thomas Narten <narten@us.ibm.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: pesci-discuss@ietf.org
X-BeenThere: pesci-discuss@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Process Evolution Study Committee of the IETF discussion <pesci-discuss.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pesci-discuss>, <mailto:pesci-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/pesci-discuss>
List-Post: <mailto:pesci-discuss@ietf.org>
List-Help: <mailto:pesci-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pesci-discuss>, <mailto:pesci-discuss-request@ietf.org?subject=subscribe>
Sender: pesci-discuss-bounces@ietf.org
Errors-To: pesci-discuss-bounces@ietf.org
Pekka Savola <pekkas@netcore.fi> writes: > (However, I believe the improvements made have resulted in tremendous > increase in *transparency* and the ability to figure out what's going > on; that certainly could have resulted in dramatic decrease of > complaints.) In my experience, transparency (as a side-effect) increases efficiency. Do not underestimate the importance of it being clear clear who has the token and what the token holder is expected to do. Compared to the pre-tracker days, this has had a significant impact. While I was an AD, it was not uncommon to see authors go directly to Tracker after a telechat and start dealing with IESG comments before I had been able to get around and send them mail saying what had happened. In those cases, one (perhaps small) bottleneck had been removed. IMO, there is significant potential here to develop improved tools to make this happen routinely. For example, if tracker was better about sending mail on certain events (like after a telechat, including the review comments). Or, if it was smart about sending reminders (document has been in "revised version needed" for > N weeks), or "New Version posted", check outstanding discuss comments (with followup reminders when this doesn't happen), etc. Thomas _______________________________________________ Pesci-discuss mailing list Pesci-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/pesci-discuss
- [Pesci-discuss] For whom it may concern.. Pekka Savola
- Re: [Pesci-discuss] For whom it may concern.. Leslie Daigle
- Re: [Pesci-discuss] For whom it may concern.. Pekka Savola
- Re: [Pesci-discuss] For whom it may concern.. JFC (Jefsey) Morfin
- Re: [Pesci-discuss] For whom it may concern.. Spencer Dawkins
- Re: [Pesci-discuss] For whom it may concern.. Spencer Dawkins
- Re: [Pesci-discuss] For whom it may concern.. Pekka Savola
- RE: [Pesci-discuss] For whom it may concern.. Margaret Wasserman
- RE: [Pesci-discuss] For whom it may concern.. Joel M. Halpern
- Re: [Pesci-discuss] For whom it may concern.. Harald Tveit Alvestrand
- RE: [Pesci-discuss] For whom it may concern.. Margaret Wasserman
- Re: [Pesci-discuss] For whom it may concern.. Pekka Savola
- RE: [Pesci-discuss] For whom it may concern.. Gray, Eric
- RE: [Pesci-discuss] For whom it may concern.. Harald Tveit Alvestrand
- Re: [Pesci-discuss] For whom it may concern.. Brian E Carpenter
- RE: [Pesci-discuss] For whom it may concern.. Ash, Gerald R (Jerry), ALABS
- Re: [Pesci-discuss] For whom it may concern.. Thomas Narten
- Re: [Pesci-discuss] For whom it may concern.. Pekka Savola
- Re: [Pesci-discuss] For whom it may concern.. Thomas Narten
- Re: [Pesci-discuss] For whom it may concern.. Brian E Carpenter