Re: [Tools-discuss] .ics files for interims?

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 15 May 2019 17:55 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE1B2120119 for <tools-discuss@ietfa.amsl.com>; Wed, 15 May 2019 10:55:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 01-un_8T6OEz for <tools-discuss@ietfa.amsl.com>; Wed, 15 May 2019 10:54:58 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 957CE120359 for <tools-discuss@ietf.org>; Wed, 15 May 2019 10:54:56 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id B3CEF38271; Wed, 15 May 2019 13:54:07 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 6D75EE3B; Wed, 15 May 2019 13:54:51 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 6B018B3D; Wed, 15 May 2019 13:54:51 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Ciavaglia\, Laurent \(Nokia - FR\/Paris-Saclay\)" <laurent.ciavaglia@nokia.com>
cc: Carsten Bormann <cabo@tzi.org>, tools-discuss <tools-discuss@ietf.org>
In-Reply-To: <HE1PR0701MB23807978A78527E7E59796B6F3090@HE1PR0701MB2380.eurprd07.prod.outlook.com>
References: <B115C907-1438-41E5-BCDF-2660759B94F3@tzi.org> <HE1PR0701MB2380EA45EE3514F4B800A8C9F3090@HE1PR0701MB2380.eurprd07.prod.outlook.com> <12481.1557928699@localhost> <HE1PR0701MB23807978A78527E7E59796B6F3090@HE1PR0701MB2380.eurprd07.prod.outlook.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Wed, 15 May 2019 13:54:51 -0400
Message-ID: <11415.1557942891@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/qlyrUctxKD3OJqKWhOxRmuRi_y0>
Subject: Re: [Tools-discuss] .ics files for interims?
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2019 17:55:02 -0000

"Ciavaglia, Laurent (Nokia - FR/Paris-Saclay)" wrote:
    >> "Ciavaglia, Laurent (Nokia - FR/Paris-Saclay)" wrote:
    >> > I would also be keen to have an .ics file available with the
    >> > virtual/interim meetings announcements.
    >>
    >> It's there.

    > LC: here I was meaning to have the .ics file as an attachment to the
    > e-mail generated when the meeting is announced. Then I can directly
    > click on it and include in my calendar application. Otherwise, I have
    > to switch to the datatracker to find the .ics.

So, shouldn't the attachment point to the agenda?
That way, you get the layer of indirection, which lets the chairs actually
make sure the link is correct.

    >> and if you look there, you see the webex URL.

    > LC: agreed. This is useful to have all links in the same place. But My
    > proposal was to automate creation of the interim/virtual meeting +
    > creation of the webex, i.e. to *generate* the webex link when on the
    > meeting request form.

Until the IETF is paying for (and getting via SLA) support from Webex, with
some serious commitment to full-functionality cross-platform, I'd rather that
we did no further integration with webex, API or not.
At this point, Cisco donates Webex to us, and we get no SLA. We can't report bugs.

    > LC: my ideal workflow would be to automatically generate the meeting
    > request from the final choice in the doodle poll. The only "manual"
    > input would then be the agenda content.

That would also be cool :-)
But it would be another proprietary integration.

I would volunteer for do a short demo for WG chairs of using Doodle better.
Many WG chairs are not aware of how it integrates with calendars, and so
often do not "pick" the meeting in doodle. (That clears up tentative values).
And I would support having doodle integration, if IETF were to become a
"business user" of doodle... That would require an RFP, etc.


--
Michael Richardson <mcr+IETF@sandelman.ca>;, Sandelman Software Works
 -= IPv6 IoT consulting =-