- From: Sean Turner via GitHub <sysbot+gh@w3.org>
- Date: Wed, 29 Jun 2022 17:19:24 +0000
- To: public-patcg@w3.org
We have used three meeting times (roughly)* for four meetings (excluding the 2021 TPAC): - A (4th) 0800 CEST / 0700 BST / 0600 UTC / 0200 EDT / 2300 PDT (previous day) / 1400 Singapore / 1600 AEST - B (1st/3rd): 2400 CET / 2300 BST / 2200 UTC / 1800 EST / 1500 PST / 0600 Singapore (next day) / 0800 AEST (next day) - C (2nd) : 1500 CEST / 1400 BST / 1300 UTC / 0900 EDT / 0600 PDT / 2100 Singapore / 2300 AEST My plan was to rotate through them. I see now that when picking this meeting's time, I went back to time B (1st/3rd meeting's time) when I should probably have gone to time C (2nd meeting's time). Going forward, I'll cycle through these times, i.e., in Sept/Oct we'll meet at time C, the next meeting will be time A, then time B, and so on. * With daylight saving time followed in some timezones and not others the times listed here might move and hour or here or there. -- GitHub Notification of comment by seanturner Please view or discuss this issue at https://github.com/patcg/meetings/issues/66#issuecomment-1170261418 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 29 June 2022 17:19:26 UTC