Re: [proto-team] PROTO - proceeding on adding PROTO shepherds to the tracker

Bill Fenner <fenner@research.att.com> Thu, 11 May 2006 19:21 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FeGil-0000A9-Ul; Thu, 11 May 2006 15:21:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FeGik-00008r-Kx for proto-team@ietf.org; Thu, 11 May 2006 15:21:10 -0400
Received: from mail-red.research.att.com ([192.20.225.110]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FeGij-0000ZN-EU for proto-team@ietf.org; Thu, 11 May 2006 15:21:10 -0400
Received: from bright.research.att.com (bright.research.att.com [135.207.20.189]) by mail-green.research.att.com (Postfix) with ESMTP id 494F584FC; Thu, 11 May 2006 15:21:09 -0400 (EDT)
Received: (from fenner@localhost) by bright.research.att.com (8.12.11.20060308/8.12.10/Submit) id k4BJL9u8018405; Thu, 11 May 2006 12:21:09 -0700
From: Bill Fenner <fenner@research.att.com>
Message-Id: <200605111921.k4BJL9u8018405@bright.research.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
To: mankin@psg.com
Subject: Re: [proto-team] PROTO - proceeding on adding PROTO shepherds to the tracker
Date: Thu, 11 May 2006 12:21:09 -0700
Versions: dmail (linux) 2.7/makemail 2.14
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: proto-team@ietf.org
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

A couple of comments:

   *  Candidate WG Document
      This document is under consideration for becoming a working group
      document.

      Possible next states: "Active WG Document", "I-D Exists", "Dead"

"I-D Exists" is only a synthesized state.  There are two databases;
the "I-D Database" and the "I-D Tracker database" (as you can see from
the csv data dumps); a document is in "I-D Exists" iff it is
in the I-D Database and not in the I-D Tracker database.

We've got a pending enhancement request to change this, but for now
this particular transition probably couldn't happen.


I'm a little uncomfortable with the change in the way the substate
field works.  The IESG tracker's substate set was chosen to apply
in nearly any state, and to at least partially make it clear who
was responsible for the next step.  I've got 2 main concerns:
1. Changing the way substates work may be a bigger implementation
   load - both backend work associating what substates are associated
   with what primary states, and frontend UI work to enable the
   right selections (e.g., one of the design goals of the tracker is
   to still function acceptably without javascript; I don't think
   you can easily implement "change to the right set of substates"
   without javascript.)
2. The set of substates seems fairly arbitrary, and doesn't necessarily
   actually convey more information.  I'd like to suggest instead
   that you consider if the "Note" field could suffice.


I think there's a missing transition from "Active WG Document" to
"In WG Last Call" - if the document is under active discussion
in the WG, then there's not necessarily a need for a pause at
"Awaiting Reviews".  Of course, since the states are all selectable
directly, this is just a convenience.

  Bill

_______________________________________________
proto-team mailing list
proto-team@ietf.org
https://www1.ietf.org/mailman/listinfo/proto-team