Re: Announcing times of interim meetings
Michael Richardson <mcr+ietf@sandelman.ca> Thu, 13 February 2020 10:45 UTC
Return-Path: <mcr@sandelman.ca>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7ACF1200F1 for <wgchairs@ietfa.amsl.com>; Thu, 13 Feb 2020 02:45:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, 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 ImkfzW5ZLZ9h for <wgchairs@ietfa.amsl.com>; Thu, 13 Feb 2020 02:45:39 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 88E991200EC for <wgchairs@ietf.org>; Thu, 13 Feb 2020 02:45:39 -0800 (PST)
Received: from dooku.sandelman.ca (unknown [217.138.36.139]) by relay.sandelman.ca (Postfix) with ESMTPS id 148FA1F459 for <wgchairs@ietf.org>; Thu, 13 Feb 2020 10:45:38 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 7E8C41A2B0B; Thu, 13 Feb 2020 11:45:36 +0100 (CET)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: wgchairs@ietf.org
Subject: Re: Announcing times of interim meetings
In-reply-to: <LNXP123MB2587D478FD7491B393F925E7EB1B0@LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM>
References: <LNXP123MB2587D478FD7491B393F925E7EB1B0@LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM>
Comments: In-reply-to <philip.eardley@bt.com> message dated "Wed, 12 Feb 2020 11:10:10 +0000."
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 25.2.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Thu, 13 Feb 2020 10:45:36 +0000
Message-ID: <24616.1581590736@dooku>
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/Kw6izFqCzsbhdDuZPCQJbBpIyTA>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Feb 2020 10:45:45 -0000
<philip.eardley@bt.com> wrote: > I've noticed that often interim meetings are only announced in one > timezone, which means there are a lot of people who have to translate > into their timezone (wasted effort and risk of errors). > I think it would be a good idea if Chairs & ietf-announce could include > several time zones. One good method could be to use > https://www.timeanddate.com/worldclock/fixedform.html which lets you > create a link that anyone can click to find their local time for the > meeting. Brian Haberman <brian@innovationslab.net> wrote: > Actually, it seems most logical to announce the time in UTC so that > everyone can have a common reference point, especially given the > variations in Daylight Savings time start/stop points. Two things to be aware of: 1) there is a ics feed of all virtual interim meetings https://datatracker.ietf.org/meeting/upcoming.ics I believe that this is driven directly by the data tracker inputs from when you push the virtual-interim meeting button request. Subscribe to it, then copy the things that are relevant to you into your own calendar. 2) While announcing a specific meeting in UTC is reasonable, it turns out that this does not perfectly work for everyone. The CELLAR meeting is anchored, for instance, to 9pm CET, because that's the time that the participants (mostly central european) want. So that means it wanders around in March and October if you aren't in CET. Here is the example of the CELLAR meeting: https://datatracker.ietf.org/doc/agenda-interim-2020-cellar-01-cellar-01/ I don't think we get markdown there yet: txt (no link highlights), or html (which requires another click). 1) have the date and time. 2) self-referential links the data, so that people can follow the link to the latest version. 3) link to etherpad. 4) link to conference software (webex, whereby, etc.) 5) the chair should loda the etherpad with the agenda beforehand. 6) even if the agenda just, "cue Kermit the Frog to sing" it still matters. Since not every system is accessible to everyone at every location {incompatible OS type, overly restrictive corporate firewall, not enough bandwidth, maybe you need for dual-monitors to effectively deal with github+conference screen+editor for proposed text changes}, it helps people decide if they will work at home or go to the office early, etc. Particularly for people who need to join the meeting from a mobile, having it all in one place really helps. -- Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works -= IPv6 IoT consulting =-
- Announcing times of interim meetings philip.eardley
- Re: Announcing times of interim meetings Brian Haberman
- Re: Announcing times of interim meetings julien.meuric
- Re: Announcing times of interim meetings Carsten Bormann
- Re: Announcing times of interim meetings Spencer Dawkins at IETF
- Re: Announcing times of interim meetings Michael Richardson
- Re: Announcing times of interim meetings Brian Haberman
- Re: Announcing times of interim meetings Robert Sparks
- Re: Announcing times of interim meetings Michael Richardson