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
A first video call with @boneskull and myself (at the OpenJS collab summit) proved to be incredibly productive. We both felt it would be worth trying to put together a semi(?) regular meeting with all @mochajs/core members.
I don't think we should force anyone to attend, but definitely encourage everyone in the core team.
However as you can see from below, with the variation of time zones it might be tricky to get everyone together at the same time.
Mochajs/core team locations + time zones
These are the locations and timezones I am aware of, if any are missed or an incorrect timezone, please flag.
Washington, USA (UTC/GMT -4)
London, UK (UTC/GMT +1)
Basel, Switzerland (UTC/GMT +2)
Netherlands (UTC/GMT +2)
Copenhagen, Denmark (UTC/GMT +2)
Israel (UTC/GMT +3)
Seoul, South Korea (UTC/GMT +9)
Timezone groups
Seem to be 3 main groups of timezones from what I can see.
UTC/GMT - 4
UTC/GMT + 2 (ish)
UTC/GMT + 9
Daylight savings
Worth noting that some locations are in daylight savings, which I do not believe applies to all of them. So any arrangements might not work permanently.
Scenarios with all timezones
Having a 8am call in Washington I believe is 9pm in Seoul.
Having a 7am call in Seoul is 6pm in Washington, but midnight in Copenhagen and 1am in Israel.
Some ideas
A. Duplicate meetings
first a meeting with timezone groups 1+2, then a meeting with timezones group 2+3.
very prescriptive and likely only useful once we have proven value from any meetings.
duplicate discussions in separate places is bad.
B. Have a meeting once but hold it late/early for someone
if the late/early person is comfortable, then why not.
having the entire team together could prove incredibly useful
C. Have an agenda-based meeting once, not all members attend each time
Similar to A except those in a certain time zone group will not attend a given meet
this could work if we organise agendas around who is available when (e.g someone in timezone group 2 has ownership of agenda X, so ensure thats covered in that meet)
would take several meetings to cover everything, but that seems fine
on the bad side: there might be several members who never manage to speak on a call, but considering there isn't anything in place right now perhaps thats fine
D. JFDI
someone creates a "Doodle" (or something similar) with a time set, and ppl decide themselves whether they can/want to attend.
ideally get an attendance of at least 3
report back after on how it went and if others want to try another one.
Anyway those are my ideas, probably not great but wondering what other people are thinking.
Thanks
The text was updated successfully, but these errors were encountered:
Hey all
A first video call with @boneskull and myself (at the OpenJS collab summit) proved to be incredibly productive. We both felt it would be worth trying to put together a semi(?) regular meeting with all @mochajs/core members.
I don't think we should force anyone to attend, but definitely encourage everyone in the core team.
However as you can see from below, with the variation of time zones it might be tricky to get everyone together at the same time.
Mochajs/core team locations + time zones
These are the locations and timezones I am aware of, if any are missed or an incorrect timezone, please flag.
Timezone groups
Seem to be 3 main groups of timezones from what I can see.
Daylight savings
Worth noting that some locations are in daylight savings, which I do not believe applies to all of them. So any arrangements might not work permanently.
Scenarios with all timezones
Some ideas
A. Duplicate meetings
B. Have a meeting once but hold it late/early for someone
C. Have an agenda-based meeting once, not all members attend each time
D. JFDI
Anyway those are my ideas, probably not great but wondering what other people are thinking.
Thanks
The text was updated successfully, but these errors were encountered: