- From: Gregg Kellogg <gregg@greggkellogg.net>
- Date: Tue, 6 Sep 2022 09:23:16 -0700
- To: Pierre-Antoine Champin <pierre-antoine@w3.org>
- Cc: Linked JSON <public-linked-json@w3.org>
- Message-Id: <AE64B81A-BE60-49A6-829A-CA8270CF3BC5@greggkellogg.net>
Done. Updates will be sent, as usual, when the details of the next meeting are set up. The calendar can be found at https://www.w3.org/groups/cg/json-ld/calendar <https://www.w3.org/groups/cg/json-ld/calendar>. Gregg Kellogg gregg@greggkellogg.net > On Sep 6, 2022, at 8:07 AM, Gregg Kellogg <gregg@greggkellogg.com> wrote: > > Yes, it should be updated to Boston time: EDT/EST. > > Gregg Kellogg > > Sent from my iPad > >> On Sep 6, 2022, at 2:55 AM, Pierre-Antoine Champin <pierre-antoine@w3.org> wrote: >> >> Hi all, >> >> I just noticed that the time of our bi-weekly meeting [1] is defined in UTC, which causes it to not follow the time-change for countries applying Daylight Saving Time. In practice, that means that the call will occur one hour earlier after the DST change (roughly end of October, depending on your country). >> >> Traditionally, W3C meetings are defined in East-Coast Time (i.e. Boston time), so that >> - it does not change for people in the US >> - it only changes for a few weeks for people in western Europe >> - I must confess I have no idea how it impacts people from other parts of the world... >> >> I suggest to align with this practice, if only to avoid creating conflicts with other W3C calls. >> >> Anyone objecting? >> >> pa >> >> [1] https://www.w3.org/groups/cg/json-ld/calendar >> >> <OpenPGP_0x9D1EDAEEEF98D438.asc> >> <OpenPGP_signature>
Received on Tuesday, 6 September 2022 16:23:31 UTC