Re: [iola-wgcharter-tool] Fwd: Trial site available for WG Charter Tool

Martin Qvist <> Fri, 02 September 2011 09:22 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D49B721F8C0B for <>; Fri, 2 Sep 2011 02:22:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.276
X-Spam-Status: No, score=-3.276 tagged_above=-999 required=5 tests=[AWL=0.323, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id PiA26WGPOj5r for <>; Fri, 2 Sep 2011 02:22:42 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id DEDE021F8B9C for <>; Fri, 2 Sep 2011 02:22:41 -0700 (PDT)
Received: by bkar4 with SMTP id r4so3143156bka.31 for <>; Fri, 02 Sep 2011 02:24:16 -0700 (PDT)
Received: by with SMTP id h3mr465170bkt.402.1314955455841; Fri, 02 Sep 2011 02:24:15 -0700 (PDT)
Received: from Martins-MacBook.local ( []) by with ESMTPS id f15sm490532bke.2.2011. (version=SSLv3 cipher=OTHER); Fri, 02 Sep 2011 02:24:15 -0700 (PDT)
Message-ID: <>
Date: Fri, 02 Sep 2011 11:24:13 +0200
From: Martin Qvist <>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
References: <> <>
In-Reply-To: <>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [iola-wgcharter-tool] Fwd: Trial site available for WG Charter Tool
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion of the IOLA / WG Charter Tool Project <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 02 Sep 2011 09:22:42 -0000


On 01/09/2011 23:07, Robert Sparks wrote:
> 1) It was not obvious where the tool was - Henrik pointed me to the new
> "Working Groups" link under
> the secretariat portion of the left navigation bar. Is that the only
> point of entry?

No, the main entry point is the "WG Records" entry under Other Documents 
in the main menu. This is also the place you can search through the WG 

The thought behind separating normal WG info (what's found under /wg/) 
and the WG records (what's found under /wgrecord/) was to separate 
normal (active) WG work from the history and chartering processes of a 
WG. If you prefer we could merge the two more, e.g. under /wg/, or 
perhaps just put in some buttons for rechartering etc.

> 2) I tried to create a new group from scratch leading to the attached
> crash - The crash happened before it
> asked me for charter text - was that going to be on the next page? On
> the page that it did provide me, it asked
> several questions that seem to be out of place (or at least fairly
> high-impedence) - asking for a mailing list,
> the subscription link, and the archive link separately. It's also asking
> for chairs/advisors/etc at the very beginning.
> In the normal case for a brand new working group, that's information
> that will come later. Is it the expectation that
> the initial form will have lots of empty fields when submitted - if so,
> would it make more sense to design an initial
> form that captured what would normally be populated, and an edit form
> that let you add these other things as they
> became available?

It was a bug in the urls field. It's fixed now. The submission of a 
charter text is done after the group is created (via submission of a 
.txt file). I made it this way because the RFC indicated that you should 
be able to create a WG with no other information than a name and an acronym.

The rest of the fields are optional (in fact the create and edit info 
pages run the same code). I guess we could make a special page for 
creation which has fewer fields. Which fields do you think it should 

> 3) How do you start an action on an existing working group? Is that
> integrated into the existing working group pages
> in any way? (It's really not obvious that you should hit the "create WG"
> button if you're wanting to start a charter update
> effort.)

No, the idea was to go through WG Records (in Other Documents), then 
search for the WG, and then change state accordingly (to e.g. Informal 
IESG Review). This starts the rechartering process. But you're right, 
there should be a "Recharter" button or some connection on the regular 
view under /wg/.

> 4) You might consider offering a way to edit a charter version online
> instead of only through a file upload.

Sure, I could do that. Would you like both options, or only online?

> 5) I tried to take the AUN group that's there through to approved so I
> could start a recharter effort on that
> (to see if I could get a charter-ietf-aun-01-00). But I can't see how
> it's possible to do that. Can you describe the path
> for me? (This might be the same answer as for 3).

The revision would be set when you upload a new charter text. Until that 
happens the WG Record shows charter-ietf-aun-01 even though it might be 
in state Informal IESG Review.

> 6) Is there anything that the tool does when a charter is marked as in
> the approved state other than just capturing
> that state? Does it touch any other tables/create or update the
> published wg charter/etc. or is it expected that is still
> manual secretariat action?

There are two ways to "go" to an approved state. One way is to approve a 
ballot (on the ballot page). This copies the most recent proposed 
charter, e.g. revision 02-04, to an approved revision, e.g. 03, and sets 
that state of the charter to approved. The other way is to just set the 
state to approved. This does not copy the proposed charter, in the above 
case the active charter would remain revision 02. I made this option for 
when a rechartering process is abandoned.