Re: Announcing times of interim meetings

Robert Sparks <rjsparks@nostrum.com> Thu, 13 February 2020 17:18 UTC

Return-Path: <rjsparks@nostrum.com>
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 4064912011D for <wgchairs@ietfa.amsl.com>; Thu, 13 Feb 2020 09:18:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.98
X-Spam-Level:
X-Spam-Status: No, score=-1.98 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] 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 gRwJw2VAx3JV for <wgchairs@ietfa.amsl.com>; Thu, 13 Feb 2020 09:18:11 -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 D188F120058 for <wgchairs@ietf.org>; Thu, 13 Feb 2020 09:18:11 -0800 (PST)
Received: from unescapeable.local ([47.186.30.41]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id 01DHI9vA075714 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 13 Feb 2020 11:18:11 -0600 (CST) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1581614291; bh=sz66/uBbQNXzKCJuy1A3mFCKoMnua4Zcwf3pLZFS/1c=; h=Subject:To:References:From:Date:In-Reply-To; b=AVTIH++cFDyAVFAuQ9myZcYQPMSQFTTkGInRQga4e/5vuLli0LyaT79S7NYkdfa2S vs4tOMJkP6rXKGWhl39fxol2YEvJU9o2xXn7qgsG12p7mo3JJrwDkQZlTkuM0M86CC QedcCi2w2O/kN922FVop59L63A64Gxz2ieAxVXRk=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.30.41] claimed to be unescapeable.local
Subject: Re: Announcing times of interim meetings
To: Brian Haberman <brian@innovationslab.net>, wgchairs@ietf.org
References: <LNXP123MB2587D478FD7491B393F925E7EB1B0@LNXP123MB2587.GBRP123.PROD.OUTLOOK.COM> <24616.1581590736@dooku> <bced44d8-3f45-1a6a-e68d-c8ebd0b94863@innovationslab.net>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <7a30adb7-4636-f41c-108e-0cc906b2b3ae@nostrum.com>
Date: Thu, 13 Feb 2020 11:18:09 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.4.2
MIME-Version: 1.0
In-Reply-To: <bced44d8-3f45-1a6a-e68d-c8ebd0b94863@innovationslab.net>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/YprFnohxLwQZIMvOvB9yPr1DgIc>
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 17:18:13 -0000

On 2/13/20 9:53 AM, Brian Haberman wrote:
>
> On 2/13/20 5:45 AM, Michael Richardson wrote:
>> 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.
>>
> Thanks for the pointer. I was not aware of this feed and I suspect most
> regular WG participants are not aware of it either.
also, it's on the top level menus (at Meetings->Upcoming).
>
>>      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.
> I don't see the relationship. The only requirement would be for the
> CELLAR chairs to *announce* their meeting time in UTC for each
> occurrence. If they anchor it to a time in a specific timezone, that's
> ok as long as the announcements state the UTC time.
>
> Regards,
> Brian
>