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

Robert Sparks <rjsparks@nostrum.com> Thu, 01 September 2011 21:05 UTC

Return-Path: <rjsparks@nostrum.com>
X-Original-To: iola-wgcharter-tool@ietfa.amsl.com
Delivered-To: iola-wgcharter-tool@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 619CF21F9771 for <iola-wgcharter-tool@ietfa.amsl.com>; Thu, 1 Sep 2011 14:05:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -95.191
X-Spam-Status: No, score=-95.191 tagged_above=-999 required=5 tests=[AWL=-7.289, BAYES_50=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_111=0.6, J_CHICKENPOX_12=0.6, J_CHICKENPOX_14=0.6, J_CHICKENPOX_15=0.6, J_CHICKENPOX_16=0.6, J_CHICKENPOX_17=0.6, J_CHICKENPOX_18=0.6, J_CHICKENPOX_19=0.6, J_CHICKENPOX_24=0.6, J_CHICKENPOX_44=0.6, J_CHICKENPOX_45=0.6, J_CHICKENPOX_46=0.6, J_CHICKENPOX_47=0.6, J_CHICKENPOX_48=0.6, MANGLED_TIME=2.3, MIME_QP_LONG_LINE=1.396, SPF_PASS=-0.001, USER_IN_WHITELIST=-100, WEIRD_PORT=0.001]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id F9qZAzIgdxcH for <iola-wgcharter-tool@ietfa.amsl.com>; Thu, 1 Sep 2011 14:05:46 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id EA3DD21F9770 for <iola-wgcharter-tool@ietf.org>; Thu, 1 Sep 2011 14:05:44 -0700 (PDT)
Received: from [] (pool-173-71-46-224.dllstx.fios.verizon.net []) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p81L7GLR039369 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 1 Sep 2011 16:07:17 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
From: Robert Sparks <rjsparks@nostrum.com>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-200--550896232
Date: Thu, 1 Sep 2011 16:07:16 -0500
References: <AD4BBA2D-C1F1-4DFA-AC87-A5660AD0F686@vigilsec.com>
To: iola-wgcharter-tool@ietf.org
Message-Id: <33829A92-3BAB-49AE-B87F-7CD68C93C181@nostrum.com>
X-Mailer: Apple Mail (2.1084)
Received-SPF: pass (nostrum.com: is authenticated by a trusted mechanism)
Cc: Ray Pelletier <rpelletier@isoc.org>, Russ Housley <housley@vigilsec.com>, Henrik Levkowetz <henrik@levkowetz.com>
Subject: [iola-wgcharter-tool] Fwd: Trial site available for WG Charter Tool
X-BeenThere: iola-wgcharter-tool@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion of the IOLA / WG Charter Tool Project <iola-wgcharter-tool.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iola-wgcharter-tool>, <mailto:iola-wgcharter-tool-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/iola-wgcharter-tool>
List-Post: <mailto:iola-wgcharter-tool@ietf.org>
List-Help: <mailto:iola-wgcharter-tool-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iola-wgcharter-tool>, <mailto:iola-wgcharter-tool-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Sep 2011 21:05:53 -0000

I tried to test this tool this afternoon, and quickly ran into a crash - the traceback is attached.

Some questions/observations to help with my next attempt to test:

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? 

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?

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

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

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).

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?


Begin forwarded message:

> From: Russ Housley <housley@vigilsec.com>
> Date: August 30, 2011 5:20:30 PM CDT
> To: IESG <iesg@ietf.org>
> Cc: Henrik Levkowetz <henrik@levkowetz.com>
> Subject: Fwd: Trial site available for WG Charter Tool
> Since ADs will be the users of this tool, I would like to have a few volunteers to make sure it does what we want.
> Russ
> Begin forwarded message:
>> From: Henrik Levkowetz <henrik@levkowetz.com>
>> Date: August 30, 2011 11:25:49 AM EDT
>> To: iola-wgcharter-tool@ietf.org, Ray Pelletier <rpelletier@isoc.org>
>> Subject: [iola-wgcharter-tool] Trial site available for WG Charter Tool
>> Hi,
>> The developer (Martin Qvist, IOLA) has now indicated that he's done with
>> the development of the WG Charter tool (as far as he can tell, from his
>> end of things).
>> There is a trial version of the tool available here:
>> http://beta.iola.dk:10003/
>> It would be helpful if we could get some testers to exercise the tool
>> now!
>> (There is one issue which I'll take up for discussion in a separate message;
>> and that's a possible issue with the specification rather than the code.)
>> Best regards,
>> 	Henrik