Skip to content

We should find a better time for our bi-weekly meetings #147

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

Closed
joesepi opened this issue Jun 10, 2022 · 2 comments
Closed

We should find a better time for our bi-weekly meetings #147

joesepi opened this issue Jun 10, 2022 · 2 comments
Assignees

Comments

@joesepi
Copy link
Member

joesepi commented Jun 10, 2022

Currently the time is very US centric.
Let's find a better time for other timezones.
Let's consider alternating timeslots as well?

Current time is as follows:

UTC Fri 10-Jun-2022 20:00 (08:00 PM):

Timezone Date/Time
US / Pacific Fri 10-Jun-2022 13:00 (01:00 PM)
US / Mountain Fri 10-Jun-2022 14:00 (02:00 PM)
US / Central Fri 10-Jun-2022 15:00 (03:00 PM)
US / Eastern Fri 10-Jun-2022 16:00 (04:00 PM)
EU / Western Fri 10-Jun-2022 21:00 (09:00 PM)
EU / Central Fri 10-Jun-2022 22:00 (10:00 PM)
EU / Eastern Fri 10-Jun-2022 23:00 (11:00 PM)
Moscow Fri 10-Jun-2022 23:00 (11:00 PM)
Chennai Sat 11-Jun-2022 01:30 (01:30 AM)
Hangzhou Sat 11-Jun-2022 04:00 (04:00 AM)
Tokyo Sat 11-Jun-2022 05:00 (05:00 AM)
Sydney Sat 11-Jun-2022 06:00 (06:00 AM)

Or in your local time:

@ruyadorno
Copy link
Member

After an internal polling with the recently active team members it seems that the ideal meeting time is going to be Thursdays 3pm UTC. I particularly like it since it's early enough that it provides a chance for European timezones to participate and late enough that early birds in the west coast can also participate.

In the meantime we can continue to explore the possibility of having an alternative time option to better accommodate more timezones.

cc @darcyclarke @joesepi @bcoe @olivier-martin-sf

@ruyadorno
Copy link
Member

Public calendar updated! The auto-generated issue should pick up the info from there so I believe there's nothing else to do here other than keeping an eye on how well the new timeslot is working out for everyone.

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

No branches or pull requests

2 participants