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

"Emilio A. Sánchez" <esanchez@yaco.es> Wed, 30 March 2011 19:18 UTC

Return-Path: <esanchez@yaco.es>
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 C5B033A6BBC for <yaco-wgchair-tracker@core3.amsl.com>; Wed, 30 Mar 2011 12:18:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.078
X-Spam-Level:
X-Spam-Status: No, score=-0.078 tagged_above=-999 required=5 tests=[AWL=1.739, BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
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 FKsxdJdbVZSo for <yaco-wgchair-tracker@core3.amsl.com>; Wed, 30 Mar 2011 12:18:00 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 8279F3A6BB3 for <yaco-wgchair-tracker@ietf.org>; Wed, 30 Mar 2011 12:17:59 -0700 (PDT)
Received: by wwa36 with SMTP id 36so1348414wwa.13 for <yaco-wgchair-tracker@ietf.org>; Wed, 30 Mar 2011 12:19:38 -0700 (PDT)
Received: by 10.227.131.9 with SMTP id v9mr1795426wbs.6.1301512777837; Wed, 30 Mar 2011 12:19:37 -0700 (PDT)
Received: from [192.168.11.210] (38.Red-80-36-82.staticIP.rima-tde.net [80.36.82.38]) by mx.google.com with ESMTPS id bs4sm224027wbb.52.2011.03.30.12.19.33 (version=SSLv3 cipher=OTHER); Wed, 30 Mar 2011 12:19:36 -0700 (PDT)
Message-ID: <4D93824A.9090308@yaco.es>
Date: Wed, 30 Mar 2011 21:19:38 +0200
From: =?ISO-8859-1?Q?=22Emilio_A=2E_S=E1nchez=22?= <esanchez@yaco.es>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.14) Gecko/20110223 Thunderbird/3.1.8
MIME-Version: 1.0
To: Ed Juskevicius <edj.etc@gmail.com>
References: <AANLkTimPDS2ss3hK45iWSNiiyJrXPrM4fCEqfKQfKVkC@mail.gmail.com> <4D933A21.7070306@yaco.es> <AANLkTik9ELOH+yMebf+_0Co9p6TCGkd7W+TvkoZuL4aA@mail.gmail.com>
In-Reply-To: <AANLkTik9ELOH+yMebf+_0Co9p6TCGkd7W+TvkoZuL4aA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: yaco-wgchair-tracker@ietf.org
Subject: Re: [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 19:18:01 -0000

    Hi,

    All the changes required have been commited [1] and applied in the 
beta server.

    In summary:

    * Added state definitions
    * Freeze states applicable to *all* WGs. In this point I included 
the 'Call For Adoption By WG Issued' cause you need it to enter a draft 
in your WG workflow.
    * Re-order state list
    * Added a link to the state diagram

    Regards,

[1] http://trac.tools.ietf.org/tools/ietfdb/ticket/644

El 30/03/11 16:17, Ed Juskevicius escribió:
> Good stuff here too.
> Thank You!
> Regards,
> Ed  J.
> -------------------
>
> On Wed, Mar 30, 2011 at 10:11 AM, "Emilio A. Sánchez" <esanchez@yaco.es
> <mailto:esanchez@yaco.es>> wrote:
>
>        Hi,
>
>     El 30/03/11 14:38, Ed Juskevicius escribió:
>
>         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.
>
>
>        Fine, I'll add the definitions from RFC6174
>
>            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.
>
>
>        That makes sense.
>
>                   * 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.
>
>
>        I think that probably it's better if we gray out these states and
>     disable their checkbox so they can not be unchecked. And probably
>     add a message explaining why they can not be throw out at the top of
>     the page.
>
>            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:
>                         o Call For Adoption by WG Issued
>                         o Adopted by A WG
>                         o Adopted for WG Info Only
>                         o WG Document
>                         o Parked WG Document
>                         o Dead WG Document
>                         o In WG Last Call
>                         o Waiting for WG Chair Go-Ahead
>                         o WG Consensus: Waiting for Writeup
>                         o Sent to IESG for Publication
>
>
>        Fine, I'll change the order of the states.
>
>                   *   If possible, it would be good to include a pointer
>         to the
>
>                     state diagram in Section 4.1 of RFC6174
>
>
>        Of course, without problem.
>
>
>         Regards,
>         Ed  J.
>
>
>        Best,
>     _______________________________________________
>     yaco-wgchair-tracker mailing list
>     yaco-wgchair-tracker@ietf.org <mailto:yaco-wgchair-tracker@ietf.org>
>     https://www.ietf.org/mailman/listinfo/yaco-wgchair-tracker
>
>