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

Robert Sparks <rjsparks@nostrum.com> Tue, 22 January 2019 21:10 UTC

Return-Path: <rjsparks@nostrum.com>
X-Original-To: tools-development@ietfa.amsl.com
Delivered-To: tools-development@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 367DC1310F9 for <tools-development@ietfa.amsl.com>; Tue, 22 Jan 2019 13:10:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.979
X-Spam-Level:
X-Spam-Status: No, score=-1.979 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mji-3TaokCvC for <tools-development@ietfa.amsl.com>; Tue, 22 Jan 2019 13:10:20 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 48C211310FD for <tools-development@ietf.org>; Tue, 22 Jan 2019 13:10:20 -0800 (PST)
Received: from unescapeable.local ([47.186.39.7]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x0MLADqK009245 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 22 Jan 2019 15:10:14 -0600 (CST) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1548191415; bh=Fh6sLwzxVEg3qNQm6sl6r24gQqMd6NaizNbEH/puzIo=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=AP8vT3i5d8flZtNA0t2Z9kExD6czP9rxSNI6jIQcCqvpKU7dkvIfsQaDIdQjMHzPv RYU9yO9Wm0T2Y/k7Ghjyosofmy/Dd7Wrk4rJYAXNSTOFkRPVlUmxdkO5N5Q63X5VYz DF8cwdt50JZGMJiXZMblKiYT30IAVXBObrFLlXPw=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.39.7] claimed to be unescapeable.local
To: Alissa Cooper <alissa@cooperw.in>
Cc: IETF Tools Development <tools-development@ietf.org>
References: <72ace60b-32df-6b11-bbdb-c1eb2cba5c2c@nostrum.com> <2E1B3878-DFF3-488A-8DFF-22DD2483F456@cooperw.in>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <e22bf100-fe21-ea7c-a113-54858eae37b1@nostrum.com>
Date: Tue, 22 Jan 2019 15:10:13 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:60.0) Gecko/20100101 Thunderbird/60.4.0
MIME-Version: 1.0
In-Reply-To: <2E1B3878-DFF3-488A-8DFF-22DD2483F456@cooperw.in>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-development/CqleSEF7IEjftltpn7Drte1R0XI>
Subject: Re: [TOOLS-DEVELOPMENT] Next (and I think final) version of the Meeting application SoW
X-BeenThere: tools-development@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Tools Development list server <tools-development.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-development>, <mailto:tools-development-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-development/>
List-Post: <mailto:tools-development@ietf.org>
List-Help: <mailto:tools-development-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-development>, <mailto:tools-development-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jan 2019 21:10:22 -0000

On 1/22/19 2:55 PM, Alissa Cooper wrote:
> Have we done any serious investigation of whether we could use an off-the-shelf tool like Sched to meet the bulk
That's the crucial word.
> of our needs, rather than continuing to develop more bespoke functionality that we have to maintain over time for meeting scheduling and display?
No, but I don't think it would actually meet the bulk of our needs. We 
might be able to separate the "building a schedule" part of the app from 
the "managing materials, displayed agenda, and proceedings" part of the 
app, but doing so is likely as large as what we are proposing to do now.
>   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.
Sure. But there integrating the output of that grid into the meeting 
materials management stuff we have - are you proposing we don't do that 
part anymore, or switch to some other commercial conferencing system and 
only do what it lets you do with materials?
>
> I’m also curious who we expect to consume the improved meeting statistics.
AFAIK, only the IESG.
>   As far as I know, no one on the IESG makes use of the existing reports cited in the RFP.
Alexa -  who keeps asking for this report?
> 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.
>
> Thanks,
> Alissa
>
>> On Jan 17, 2019, at 2:13 PM, Robert Sparks <rjsparks@nostrum.com> 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
>> TOOLS-DEVELOPMENT@ietf.org
>> https://www.ietf.org/mailman/listinfo/tools-development