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

CTC Meeting Times for 2017 #49

@Trott

Description

@Trott

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions