[yaco-wgchair-tracker] Testdrive comments and concerns on the "Manage Workflow" tab

Ed Juskevicius <edj.etc@gmail.com> Wed, 30 March 2011 12:36 UTC

Return-Path: <edj.etc@gmail.com>
X-Original-To: yaco-wgchair-tracker@core3.amsl.com
Delivered-To: yaco-wgchair-tracker@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6DB4C28C177 for <yaco-wgchair-tracker@core3.amsl.com>; Wed, 30 Mar 2011 05:36:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.282
X-Spam-Level:
X-Spam-Status: No, score=-103.282 tagged_above=-999 required=5 tests=[AWL=0.016, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iEHl50Ai8+Sk for <yaco-wgchair-tracker@core3.amsl.com>; Wed, 30 Mar 2011 05:36:54 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 48A8928C172 for <yaco-wgchair-tracker@ietf.org>; Wed, 30 Mar 2011 05:36:54 -0700 (PDT)
Received: by vws12 with SMTP id 12so1106158vws.31 for <yaco-wgchair-tracker@ietf.org>; Wed, 30 Mar 2011 05:38:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to:cc :content-type; bh=UYu+XCQAgec+OHdkqlJNEsZQF0ZnFqEIkzHDptOF+Cs=; b=vje8x7ACk8FKLYE4gpVvW52ubvdtP0JqsFJxra1oRgXIeu+dNCi2ad1/giJ/ODQTyP D411r3KZrjHODCW+XpHi2Y6l9C1FZpZPZp9WhjQ+KxY1gObuGEA8cslQWCNQSjml0hpY XoeP6SLJO9cSCVr88sg9ewLXnG+WPH5gMmpw0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=McioehpdI8El2jZWs+CZVR6nSgOnOX+Ipv+qR8E29JOLAIZktKYUqPr8BBBigqpxWV NOkZ7P9pjLf1dCF+9zFnzwy0hwPXSCfbM0WRqdUHVf0b8k/cXZtRSOK/pmoCueyFRNoA qZQc2hsFeRpiVkwE0Tltxgiz84cYXsed1Mukc=
MIME-Version: 1.0
Received: by 10.52.176.37 with SMTP id cf5mr1463768vdc.73.1301488712633; Wed, 30 Mar 2011 05:38:32 -0700 (PDT)
Received: by 10.52.164.200 with HTTP; Wed, 30 Mar 2011 05:38:32 -0700 (PDT)
Date: Wed, 30 Mar 2011 08:38:32 -0400
Message-ID: <AANLkTimPDS2ss3hK45iWSNiiyJrXPrM4fCEqfKQfKVkC@mail.gmail.com>
From: Ed Juskevicius <edj.etc@gmail.com>
To: =?ISO-8859-1?Q?Emilio_A=2E_S=E1nchez?= <esanchez@yaco.es>
Content-Type: multipart/alternative; boundary=bcaec5015d33654bf1049fb274eb
Cc: yaco-wgchair-tracker@ietf.org
Subject: [yaco-wgchair-tracker] Testdrive comments and concerns on the "Manage Workflow" tab
X-BeenThere: yaco-wgchair-tracker@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of the Yaco / WG Chairs' and Authors' Tracker Project <yaco-wgchair-tracker.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/yaco-wgchair-tracker>, <mailto:yaco-wgchair-tracker-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/yaco-wgchair-tracker>
List-Post: <mailto:yaco-wgchair-tracker@ietf.org>
List-Help: <mailto:yaco-wgchair-tracker-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yaco-wgchair-tracker>, <mailto:yaco-wgchair-tracker-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Mar 2011 12:36:56 -0000

Hello.  I have several comments and suggestions about the current Beta code
for the Datatracker Extensions for WG Chairs, after seeing the demonstration
of the tool during the WG Chairs lunch in Prague today.

Comments / Suggestions on the "Manage Workflow" tab:
(for example at: http://beta.wgchairs.yaco.es/wg/alto/management/workflows/
 )


   1. It is a good idea to list all of the possible states (as defined in
   RFC 6174) for documents related to IETF WGs.  I like this.
   2. The above being said, not everyone will memorize the definitions of
   each of the different states (as described in RFC6174)
      - I suggest this page be modified to provide definitions of each of
      the WG document states, or easy access to the state definitions BEFORE
      allowing the Chairs to say they don't want to use some of these states in
      their WGs.
      -
   3.  Next point:  Two of the states (viz. "WG Document" and "Submitted to
   IESG for Publication") appear on the list of possible states (which is
   good), however WG Chairs should not be allowed to decide these two states
   will not be used in their WGs.
      - Section 7 of RFC6175 specifies that the Datatracker will
      automatically move I-Ds into the "WG Document" state and then
later into the
      "Submitted to the IESG for Publication" state when certain things happen.
      - Therefore, the above two states are supposed to be used to describe
      the state of some I-Ds in ALL working groups, whether the Chairs put
      documents (manually) into those states or not.  They are to be automatic
      state transitions.
      -
      - I suggest you hard code a check mark in the "Check Box" that is
      current to the left of both of these two states, and then do not
let anyone
      remove those two check marks.  People who attempt to remove these check
      marks should be presented with a message to explain why these
two states are
      applicable to *all* WGs.
      -
   4. Next point:  The list of possible states is organized alphabetically.
   RFC6174 contains a state diagram showing typical or 'usual" state
   transitions for I-Ds through all of the states, for WGs that decied to use
   all of the states.
      - I suggest the states be re-ordered to more closely resemble how an
      I-D might traverse the state diagram, from top to bottom.
      - I suggest the list be re-ordered to read as follows:
         - Call For Adoption by WG Issued
         - Adopted by A WG
         - Adopted for WG Info Only
         - WG Document
         - Parked WG Document
         - Dead WG Document
         - In WG Last Call
         - Waiting for WG Chair Go-Ahead
         - WG Consensus: Waiting for Writeup
         - Sent to IESG for Publication
      -  If possible, it would be good to include a pointer to the state
      diagram in Section 4.1 of RFC6174
      -

Regards,

Ed  J.