Skip to content
This repository has been archived by the owner on Nov 9, 2017. It is now read-only.

CTC Meeting Times for 2017 #49

Closed
Trott opened this issue Dec 18, 2016 · 14 comments · Fixed by #52
Closed

CTC Meeting Times for 2017 #49

Trott opened this issue Dec 18, 2016 · 14 comments · Fixed by #52

Comments

@Trott
Copy link
Member

Trott commented Dec 18, 2016

@nodejs/ctc

Feedback so far (please correct if I've misinterpreted you!):

Yes (13): @Trott @bnoordhuis @addaleax @rvagg @thefourtheye @thealphanerd @targos @cjihrig @evanlucas @ChALkeR @indutny @jasnell @mscdex
No (0):
Abstain (0):
Not yet commented (7): @chrisdickinson @Fishrock123 @mhdawson @misterdjules @ofrobots @shigeki @trevnorris

We need to get at least one more meeting time into the rotation IMO. The current rotation between two times means that Rod and Sakthipriyan (and probably Shigeki too) are basically guaranteed to miss at least half our meetings. By adding one more meeting time, we can make it (at least in theory) so that everyone can attend more than half the meetings. The downside is that it would need to be a meeting time that many people would find very difficult.

In other words, we'd trade having a small number of people who can't make ~50% of the meetings for a larger number of people who can't make ~33% of the meetings. I think that's a worthwhile trade. Spread the inconvenience out more equitably and all that.

Ben made some persuasive arguments for 05:00 UTC. Looking at the data in the spreadsheet we all filled out, it does seem that is the most equitable time.*

Here is how that plays out across some relevant time zones, along with the two existing times:

UTC SF NY DE/NL Moscow Chennai JP Sydney
05:00 9 PM 12 AM (midnight) 6 AM 8 AM 10:30 AM 2 PM 4 PM
16:00 8 AM 11 AM 5 PM 7 PM 9:30 PM 1 AM 3 AM
20:00 12 PM (noon) 3 PM 9 PM 11 PM 1:30 AM 5 AM 7 AM

I'm up for giving this rotation a try for three or six months and see how it works. What does everyone else think?

* To calculate "equitable", I checked the standard deviation of preferences for everyone across the three resulting meeting times. Adding 05:00 to the existing two meeting times resulted in the lowest standard deviation of any possible third time, which means that it results in a set of meeting times that are the closest to equally convenient/inconvenient for everyone.

@ChALkeR
Copy link
Member

ChALkeR commented Dec 18, 2016

My schedule for 2017 would probably change, and I don't yet know how exactly would it look.
I will update my row in the «meeting time options» table accordingly when I will have more information.

Upd: I expect all three proposed time slots to be green for me, though.

@bnoordhuis
Copy link
Member

I'm +1 on the proposed times.

@Trott
Copy link
Member Author

Trott commented Dec 21, 2016

In email, I confirmed that the new time works for @rvagg and @thefourtheye. And @ChALkeR and @bnoordhuis have left favorable comments here.

It would be good to get feedback from others who are not in the Americas. So that would be @addaleax @shigeki @targos

@addaleax
Copy link
Member

I’m pretty certain I’d be missing most of or all of the meetings at UTC 05:00, but I agree that it’s worthwhile if it enables others to attend more frequently. So, +1 from me.

@targos
Copy link
Member

targos commented Dec 22, 2016

+1

@Trott
Copy link
Member Author

Trott commented Dec 26, 2016

If I'm reading this right, it has a +1 or similar from 7 of the 20 CTC folks and no comment so far from others. I'll put this on the agenda for this week's meeting to hopefully make it official. If anyone has concerns about trying out this third meeting time, please comment!

List of people this has a +1 or +1-ish from: @Trott @rvagg @thefourtheye @ChALkeR @bnoordhuis @addaleax @targos

@MylesBorins
Copy link

I'm +1 on adding the new time. Would you be able to put a list of votes at the top @Trott?

@Trott
Copy link
Member Author

Trott commented Dec 27, 2016

Would you be able to put a list of votes at the top @Trott?

Sure, done.

@evanlucas
Copy link

I think it makes sense to add an additional meeting time. +1 from me.

@ofrobots
Copy link

+1 as well

@indutny
Copy link
Member

indutny commented Dec 28, 2016

+1

2 similar comments
@jasnell
Copy link
Member

jasnell commented Dec 28, 2016

+1

@mscdex
Copy link

mscdex commented Dec 28, 2016

+1

@mhdawson
Copy link
Member

mhdawson commented Jan 3, 2017

+1

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

Successfully merging a pull request may close this issue.