Re: [yaco-wgchair-tracker] Testdrive comments and concerns on the "Manage Workflow" tab
Ed Juskevicius <edj.etc@gmail.com> Wed, 30 March 2011 14:15 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 17A5328C131 for <yaco-wgchair-tracker@core3.amsl.com>; Wed, 30 Mar 2011 07:15:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.097
X-Spam-Level:
X-Spam-Status: No, score=-101.097 tagged_above=-999 required=5 tests=[AWL=1.201, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, 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 Ky2rjkZvnwLT for <yaco-wgchair-tracker@core3.amsl.com>; Wed, 30 Mar 2011 07:15:48 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by core3.amsl.com (Postfix) with ESMTP id 935CA3A6A34 for <yaco-wgchair-tracker@ietf.org>; Wed, 30 Mar 2011 07:15:48 -0700 (PDT)
Received: by vxg33 with SMTP id 33so1203418vxg.31 for <yaco-wgchair-tracker@ietf.org>; Wed, 30 Mar 2011 07:17:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=83He4BELDPxSt6aeuDn2sHI4eNfe2dcH91+XEt6ZP3I=; b=fGrp0ycrC+3IKeScwmAJnyWxL90vckEmw8zREvKtImzet1qZEZgfLqzv+VaCGA4Bk4 G5/qj1gor5L5BXh6EcSdLrBiSFUhnZpav4hJe6LYoza+nj6Y3uYwQffWG99nzOSOzLUi xa+K55ei9bR+XOZlXu0iqkATW8m9U8pbTUoMw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=N/RyhA21eh0GK8UyXsVUAreuCO6YGjF2dszGUn7PPI0HThsKdL4PmybHGN+IaZirU3 Zo77wtqn6Ob6bsCjEOXHY5HlCB8DVcRYxCD846QbMPVuPF33Hb3va3qYeAbffoxnym6j aQX0Wal1SAkfra8zXHhTGXhjK63logCSN9E1U=
MIME-Version: 1.0
Received: by 10.52.176.37 with SMTP id cf5mr1625461vdc.73.1301494647416; Wed, 30 Mar 2011 07:17:27 -0700 (PDT)
Received: by 10.52.164.200 with HTTP; Wed, 30 Mar 2011 07:17:27 -0700 (PDT)
In-Reply-To: <4D933A21.7070306@yaco.es>
References: <AANLkTimPDS2ss3hK45iWSNiiyJrXPrM4fCEqfKQfKVkC@mail.gmail.com> <4D933A21.7070306@yaco.es>
Date: Wed, 30 Mar 2011 10:17:27 -0400
Message-ID: <AANLkTik9ELOH+yMebf+_0Co9p6TCGkd7W+TvkoZuL4aA@mail.gmail.com>
From: Ed Juskevicius <edj.etc@gmail.com>
To: "Emilio A. Sánchez" <esanchez@yaco.es>
Content-Type: multipart/alternative; boundary="bcaec5015d3322e6cc049fb3d60d"
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 14:15:50 -0000
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>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 > https://www.ietf.org/mailman/listinfo/yaco-wgchair-tracker >
- [yaco-wgchair-tracker] Testdrive comments and con… Ed Juskevicius
- Re: [yaco-wgchair-tracker] Testdrive comments and… Emilio A. Sánchez
- Re: [yaco-wgchair-tracker] Testdrive comments and… Ed Juskevicius
- Re: [yaco-wgchair-tracker] Testdrive comments and… Emilio A. Sánchez