[rgchairs] Re: 65th IETF - WG/RG/BOF Scheduling

Allison Mankin <mankin@psg.com> Tue, 17 January 2006 16:09 UTC

Received: from localhost.cnri.reston.va.us ([] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EytOr-0001xW-Ee; Tue, 17 Jan 2006 11:09:37 -0500
Received: from odin.ietf.org ([] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EytOq-0001wu-C6; Tue, 17 Jan 2006 11:09:36 -0500
Received: from ietf-mx.ietf.org (ietf-mx []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27087; Tue, 17 Jan 2006 11:08:11 -0500 (EST)
Message-Id: <200601171608.LAA27087@ietf.org>
Received: from psg.com ([] ident=mailnull) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EytWy-0005nN-TH; Tue, 17 Jan 2006 11:18:02 -0500
Received: from localhost ([] helo=psg.com) by psg.com with esmtp (Exim 4.60 (FreeBSD)) (envelope-from <mankin@psg.com>) id 1EytOn-0006Xj-R3; Tue, 17 Jan 2006 16:09:33 +0000
To: Henrik Levkowetz <henrik@levkowetz.com>
Date: Tue, 17 Jan 2006 08:09:33 -0800
From: Allison Mankin <mankin@psg.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: wgchairs@ietf.org, rgchairs@irtf.org, bofchairs@ietf.org
Subject: [rgchairs] Re: 65th IETF - WG/RG/BOF Scheduling
X-BeenThere: rgchairs@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IRTF research group chairs list <rgchairs.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rgchairs>, <mailto:rgchairs-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/rgchairs>
List-Post: <mailto:rgchairs@lists.ietf.org>
List-Help: <mailto:rgchairs-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rgchairs>, <mailto:rgchairs-request@lists.ietf.org?subject=subscribe>
Sender: rgchairs-bounces@lists.ietf.org
Errors-To: rgchairs-bounces@lists.ietf.org

Hi, Henrik,

I've taken agenda@ietf.org off the cc list so we don't keep generating
tickets for them while we discuss the tool design.  Or should we move
to tools-discuss?  I think this mail will get to the tool developer.

> Also, I have lists of conflicts from previous years, which I use as a
> base for the request this time.  I'd love to be able to just type
> in the list, but the tool forces me to use the drop-down list.  A bit
> awkward.

The purpose of this tool (I understand) is so that simple initial machine
processing can be done on the WG chairs' scheduling inputs, before the
human brain (the brilliant Marcia!) NP-complete effort of making the 
actual schedule.

Having seen a lot of the Chairs' unstructured requests, I know they are
very varied, even to the form of the lists for conflict avoidance:
misspellings, shorter names than the real short names, SIP/PING
instead of both names, descriptive terms.  It's understandable
but hard to use.

What I'm wondering is whether at IETF 65, the session will come
up pre-configured with the previous conflict list, and allow the chairs
to edit that...

> The tool forces me to skip that and list first-priority conflicts
> before I may list second-priority conflicts.  Is that necessary?

I agree, you should not have to do this.   Something for the fix list, IMO.


Rgchairs mailing list