[proto-team] Re: [IRSG] Adding IETF tracker support for IAB and IRTF document shepherds
Allison Mankin <mankin@psg.com> Wed, 10 May 2006 18:03 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
by megatron.ietf.org with esmtp (Exim 4.43)
id 1Fdt2Q-0000Hc-NU; Wed, 10 May 2006 14:03:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.43) id 1Fdt2Q-0000HX-0l
for proto-team@ietf.org; Wed, 10 May 2006 14:03:54 -0400
Received: from psg.com ([147.28.0.62])
by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fdt2N-0001Jo-Oi
for proto-team@ietf.org; Wed, 10 May 2006 14:03:53 -0400
Received: from localhost ([127.0.0.1] helo=psg.com)
by psg.com with esmtp (Exim 4.60 (FreeBSD))
(envelope-from <mankin@psg.com>)
id 1Fdt2J-000MxC-HR; Wed, 10 May 2006 18:03:47 +0000
To: "John R Levine" <johnl@iecc.com>
Date: Wed, 10 May 2006 11:03:47 -0700
From: Allison Mankin <mankin@psg.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: irsg@ISI.EDU, rpelletier@isoc.org, henrik@levkowetz.com,
proto-team@ietf.org
Subject: [proto-team] Re: [IRSG] Adding IETF tracker support for IAB and
IRTF document shepherds
X-BeenThere: proto-team@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Process and Tools Team <proto-team.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/proto-team>,
<mailto:proto-team-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:proto-team@ietf.org>
List-Help: <mailto:proto-team-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/proto-team>,
<mailto:proto-team-request@ietf.org?subject=subscribe>
Errors-To: proto-team-bounces@ietf.org
Message-Id: <E1Fdt2Q-0000Hc-NU@megatron.ietf.org>
John,
We slipped. It also needs a next state of In RG Last Call,
at least.
Thanks for noticing this.
What other states would RGs find useful? This is very
bare bones, to provide very simple tracking and transparency
for the drafts.
For instance, would you like to have
RG Document Awaiting Reviews
I'd propose some text like:
This document needs reviews (possibly a certain number of reviews,
at a minimum) before the publication process can proceed
Possible next states: "Active WG Document", "Parked WG Document",
"In RG Last Call", "In IRSG Evaluation", "Dead"
Permitted sub-states: "0 reviews", "1 reviews", "2 reviews", "3
reviews", "4 reviews", "5 reviews", "Awaiting MIB Doctor Review",
*** More special review states ***
(R-xxx)
Some questions on this: would this be used for internal RG required
reviews if you have them, as well as the required IRSG reviews? Is it
reasonal to overload it if that happens? Would it be reasonable to
leave the extra numbers there because of the potential for change?
The tracker is very simplistic and we don't want to keep remodeling
it. If you have the potential to use it for internal required
reviews, do you want to have distinct states?
_______________________________________________
proto-team mailing list
proto-team@ietf.org
https://www1.ietf.org/mailman/listinfo/proto-team
- [proto-team] Adding IETF tracker support for IAB … Allison Mankin
- [proto-team] Re: Adding IETF tracker support for … David Meyer
- Re: [proto-team] Re: Adding IETF tracker support … Allison Mankin
- [proto-team] Re: Adding IETF tracker support for … Henrik Levkowetz
- Re: [proto-team] Re: Adding IETF tracker support … Henrik Levkowetz
- Re: [proto-team] Re: Adding IETF tracker support … David Meyer
- [proto-team] Adding IETF tracker support for IAB … Allison Mankin
- [proto-team] Adding IETF tracker support for IAB … Allison Mankin
- [proto-team] Re: [IRSG] Adding IETF tracker suppo… Allison Mankin
- [proto-team] Re: [IRSG] Adding IETF tracker suppo… John R Levine