Re: [TOOLS-DEVELOPMENT] Next (and I think final) version of the Meeting application SoW

Alissa Cooper <> Tue, 22 January 2019 20:55 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 186781310F5 for <>; Tue, 22 Jan 2019 12:55:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key) header.b=tNiDCQ98; dkim=pass (2048-bit key) header.b=AwaMJggn
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id SPqYhY7RNIup for <>; Tue, 22 Jan 2019 12:55:39 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 78DD81310F1 for <>; Tue, 22 Jan 2019 12:55:39 -0800 (PST)
Received: from compute7.internal (compute7.nyi.internal []) by mailout.nyi.internal (Postfix) with ESMTP id 8919A20B49; Tue, 22 Jan 2019 15:55:38 -0500 (EST)
Received: from mailfrontend1 ([]) by compute7.internal (MEProxy); Tue, 22 Jan 2019 15:55:38 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm2; bh=h pOOikkYvdqOTrA/KhRbEBLTFvuEbHpJGhXU2dNXhGI=; b=tNiDCQ98Y1gm9TEB3 vWJv5OjuGwzltld7Q/WYwb9q5DmoHDy6VLS08YHLITMDBiLpVww+/Ep0pMir+hq1 i+IR0HTygTddNzCTs/whCvIzwGssbq62HAfZZVNXiVJLHE0sJBSXbrIw40WqN7Lm vwxOAANEdDAjahJ2n5zkqzI8pPCZ6xhxxwU99GjhQ4uYYNmO4b6NByB3rQ7z+S0j KpOIzYBmTF6C4IvrptzswoWuN07vpbgoGL9HkGM26/iG42YCBYzsoyvSmtBa3yU7 bDlGyjbbM3CX3FqSH/mJ8SqugXXIOs1+icv0vaTT4MBaCafZo2btmcAbuZwgG1F6 zsZFQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=hpOOikkYvdqOTrA/KhRbEBLTFvuEbHpJGhXU2dNXh GI=; b=AwaMJggnTS6IJf/GiP3jdKN47GhwbGvjGu6Xp0Lm2zkPhqXmYEexPnp5C SukgSQ+B63jxa3kwq5pOviZ/jH+PmOz1Wxs9xk7tIqTjF9nxUe5+My0LSPYu4Rnj DD4JSQrJj3uUvpjsVsFznQw0wmuJgHOCbwivxQkJpRfpzuVpqMJrIUrg2eqBJV54 2npFpomZOTLIVBeHZ1+nbm4EVt4WxR/4Pb9VekLaAozejr4SzAgH7F9WPMMZF82u sbyc5Kf+ZyNFqD2lGqv4fWundgIQfgnYi7WeTogfUsDEw4hNAVvEfY7vL7ZksNVK x1k/DI94R/QYsqxDTcZCt2tqIRNiQ==
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrheekgddugeefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfquhhtnecuuegrihhlohhuthemucef tddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpegtggfuhfgjff fgkfhfvffosehtqhhmtdhhtdejnecuhfhrohhmpeetlhhishhsrgcuvehoohhpvghruceo rghlihhsshgrsegtohhophgvrhifrdhinheqnecuffhomhgrihhnpehivghtfhdrohhrgh enucfkphepudejfedrfeekrdduudejrdelvdenucfrrghrrghmpehmrghilhhfrhhomhep rghlihhsshgrsegtohhophgvrhifrdhinhenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:SYNHXPhFfysslE0XGRedslS9ACCWORa9UH7XC4uXV51mHT2D_dz2sQ> <xmx:SYNHXC-cQGizS_7wqcErzBypN2Ul6z-80r50wXTM25lZqOlSH2FoLQ> <xmx:SYNHXFhl6bibpD1E7jsUVcImT97c-ldY5-g-eMFjSyNX_GOuMD8hvA> <xmx:SoNHXHsfqc86mHrJF7qG5jy2lPnZH68iDfLg-u9LIbLa1jBoPGTMZw>
Received: from (unknown []) by (Postfix) with ESMTPA id 87FFDE4803; Tue, 22 Jan 2019 15:55:37 -0500 (EST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Alissa Cooper <>
In-Reply-To: <>
Date: Tue, 22 Jan 2019 15:55:36 -0500
Cc: IETF Tools Development <>
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <>
To: Robert Sparks <>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <>
Subject: Re: [TOOLS-DEVELOPMENT] Next (and I think final) version of the Meeting application SoW
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Tools Development list server <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 22 Jan 2019 20:55:42 -0000

Have we done any serious investigation of whether we could use an off-the-shelf tool like Sched to meet the bulk of our needs, rather than continuing to develop more bespoke functionality that we have to maintain over time for meeting scheduling and display? I know we think the IETF is a special flower, but in many ways it isn’t, e.g., we have a bunch of tracks and sessions that need to be de-conflicted based on certain criteria and fit into a grid.

I’m also curious who we expect to consume the improved meeting statistics. As far as I know, no one on the IESG makes use of the existing reports cited in the RFP. Generally I find the datatracker statistics kind of hard to consume for a number of reasons, so I would hesitate to add more functionality there without a compelling justification.


> On Jan 17, 2019, at 2:13 PM, Robert Sparks <> wrote:
> I've incorporated comments from Russ, and at his suggestion renamed the file using a schema we can follow with the remaining SoWs to cause them to group nicely in Finder.
> I believe this is ready to go out for IDIQ bids.
> RjS
> <sow_2019_meeting_v2.pdf><sow_2019_meeting_v2.docx>_______________________________________________
> TOOLS-DEVELOPMENT mailing list