-
Notifications
You must be signed in to change notification settings - Fork 2
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
Find a better meeting time #27
Comments
Sorry, we missed the meeting yesterday because our calendar all misunderstood the time as 02:00 UTC+8🤣 I think we can use all of them. e.g. slot 1 this time, slot 2 next time and slot 3 next time after next time. |
I vote for 3 |
A rotating schedule works, I think. But let's have the folks joining from Asia weigh in before deciding. |
any updates about this? |
React with 👍 to this comment for Option 3 😄 |
It comes to my attention that US DST will be ending in November. How are we going to address this matter? Do we still shift the time by one hour to match the US time zones, or use a fixed time zone (e.g. UTC or China standard time) as a reference for future meetings? |
I believe that a fixed timezone would make the meeting start at 7AM on the west coast, which is much harder to make than an 8AM start, but not impossible. If we kept it at a fixed time in the US, so that it moved an hour later for those using fixed timezones, how much of a hardship would that be for those folks? |
Being on US west cost I'd prefer option 2 or 3 for fixed meeting. In my experience rotating schedule or is probably the easiest way to resolve scheduling, though it would create a different headache with agenda. Trying to find meeting time for all three continents is always the problem of midnight for one side vs 6 AM for the other, as Europe, US, and Asia are nearly equal number of hours apart from one another. For rotating meeting with two slots it might be possible to group US East + Europe and US West + Asia. |
The new meeting schedule is a 3-way rotation, rotating between the following slots:
@jasnell will be updating the shared Google Calendar with these times. |
The current bi-weekly meeting time is very hostile to folks in time zones in Asia (it's at 0100). It only really works well for US folks unfortunately.
This is a really hard problem because US east coast and China have pretty much no time overlap at all. I think to accommodate the most people, the best slots would be one of these:
These are all obviously not great for either US west coast, or China time zones, but I don't think we can do any better without introducing a rotating schedule.
WDYT?
The text was updated successfully, but these errors were encountered: