You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@whatwg/html-triage: The currently-scheduled meeting time of 01:00 Berlin / 16:00 San Francisco has now become 09:00 Tokyo, due to the change around daylight-savings time (which we don’t have at all in Japan).
I’m personally not able to attend at 09:00 Tokyo time, but could attend still at 08:00 Tokyo time instead — which now works out to midnight Berlin / 15:00 San Francisco.
I’m not essential for these meetings, so I don’t want others involved to need to disrupt their own schedules to accommodate mine — but if that slot works does work fine too for others, I propose we shift the APAC/America-friendly meeting time to that slot instead (and I guess then also plan to later flip it back after the daylight-savings switch again in the Spring).
@domenic has indicated he’d be OK with the new time (and noted that it works out slightly better for non-Tokyo people too).
The text was updated successfully, but these errors were encountered:
@whatwg/html-triage: The currently-scheduled meeting time of 01:00 Berlin / 16:00 San Francisco has now become 09:00 Tokyo, due to the change around daylight-savings time (which we don’t have at all in Japan).
I’m personally not able to attend at 09:00 Tokyo time, but could attend still at 08:00 Tokyo time instead — which now works out to midnight Berlin / 15:00 San Francisco.
I’m not essential for these meetings, so I don’t want others involved to need to disrupt their own schedules to accommodate mine — but if that slot works does work fine too for others, I propose we shift the APAC/America-friendly meeting time to that slot instead (and I guess then also plan to later flip it back after the daylight-savings switch again in the Spring).
@domenic has indicated he’d be OK with the new time (and noted that it works out slightly better for non-Tokyo people too).
The text was updated successfully, but these errors were encountered: