Skip to content
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

Regular team video meeting? #11

Open
craigtaub opened this issue Jun 30, 2020 · 1 comment
Open

Regular team video meeting? #11

craigtaub opened this issue Jun 30, 2020 · 1 comment

Comments

@craigtaub
Copy link

craigtaub commented Jun 30, 2020

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.

  • 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.

  1. UTC/GMT - 4
  2. UTC/GMT + 2 (ish)
  3. 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

@Munter
Copy link
Member

Munter commented Jul 1, 2020

Here's a link displaying our timezones and meeting time slots: https://www.timeanddate.com/worldclock/meetingtime.html?iso=20200701&p1=263&p2=136&p4=268&p5=16&p6=69&p7=110&p8=235

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants