-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adjust regular meeting schedule to accommodate the other side of the globe #31
Comments
The 11pm pacific time works for me. |
Works for me |
I'm going to be out on PTO in this week, but @Rob--W may be able to help. The zoom meeting doesn't need any specific changes, the room can be used at any time. If there is a calendar invite I may not have access to that. Looking at schedules this would take it into the evening for Tomislav, but there at least isn't anything in his calendar. For me personally the time works. |
8 AM PDT is 5 PM CEST, Works for me. Are we going to continue with 8 AM PDT this week, and alternate between the two time slots from then on? From the next meeting onwards, we should announce the time and date of the upcoming meeting at the end of the meeting (or earlier), and publish it in the minutes. |
Sounds like a plan :)
I think this is a great suggestion. @xeenon, any concerns with this plan? |
Sorry for the delay folks, the plan sgtm. |
What's the final time? I hope there is a UTC version because converting from things like PDT is hard for me (I don't know if they're using daylight saving time). |
The notes from the last meeting include a link to a website that converts to local time zones: https://www.worldtimebuddy.com/?qm=1&lid=8,100,12,30&h=8&date=2021-7-22&sln=23-24&hf=1 |
It seems like this website doesn't support adding my own timezone, it only provides 4 fixed timezones. |
Go to the home page and add your location / time zone and PDT. The link includes UTC, so if you know your time zone relative to UTC, then you can compute the time yourself. Otherwise you can use your search engine to search for something like "11 pm PDT in CEST" (CEST is my time zone). At least DuckDuckGo and Google will show the result. Thursday 11 PM PDT becomes (Friday) 8 AM CEST, in my case. |
So the next meeting is at 6 am on July 25 in UTC+0 and the next one is 3 pm on Aug 5 in UTC+0? |
Do we want to have a registry or a document where members can check in
ahead of time to indicate their intention to attend or not?
Unfortunately I can't make the next meeting due to personal conflicts but
am happy to continue to attend at both time slots.
…On Sun, 11 Jul 2021 at 15:39, Jack Works ***@***.***> wrote:
So the next meeting is at 6 am on July 25 in UTC+0 and the next one is 3
pm on Aug 5 in UTC+0?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#31 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACIPPNOVLJHCXUP7TJWT4TTXGUJPANCNFSM47TKIW6Q>
.
|
The meeting schedule has been posted at https://github.com/w3c/webextensions/blob/main/_minutes/README.md (via #42). This document lists the next two meetings. After each meeting, minutes (meeting notes) will be published along with another entry in the schedule. |
I don't think we need something like this right now, but it may be useful in the future as we continue to evolve and we get a better sense of individuals' concerns. Does that sound reasonable? |
Duringour 2021-06-24 meeting we briefly discussed the fact that our current meeting schedule takes place during the middle of the night for people living in in timezones between +7 UTC and -9 UTC.
In order to accommodate people in these timezones, the suggestion was put forward that we alternate between the current recurring meeting time (8 AM Pacific) and another time.
If possible, I would like the chairs and editors to be able to attend both meetings. Chairs are in PDT/PST while the editors are in CEST and IST. Given this, it looks like our best (only?) option may be 11 PM Pacific.
The text was updated successfully, but these errors were encountered: