Revist the meeting times

[mhdawson]

@Trott correctly pointed out in todays meeting that with 3 new people joining and the Daylight savings time change we should update the spreadsheet with time availability and see if we should change the meeting times.

@nodejs/tsc I'll send the link to the spreadsheet through email. Please update your availability and we'll look to see if we should update the times in the next few weeks.

[ChALkeR]

I'll go over the dataset today a few hours after the meeting.

[ronag]

Maybe a good idea if nominated members are also taken into consideration?

[mhdawson]

@ChALkeR I've emailed the nominated members the link, lets give them 1 week to fill in and then go over the dataset. I also asked that they let you know if possible once they have so in that case you could assess the data earlier.

[Trott]

For the nominated folks: Note that there are two worksheets (tabs) in the spreadsheet: One for Wednesday (UTC) and one for Thursday (UTC). For a lot of people, it's mostly copy/paste from one to the other. (But of course, not everyone.)

[ChALkeR]

There are three rows that are not filled in yet (two for both days, one for Wednesday).
I updated the raw results in the spreadsheet, but those exclude the abovementioned rows for now.
Let's wait for those to get filled in.

Also, perhaps in the meantime we should revisit whether we do want a 3-slot or 2-slot based system.

The advantage of a 3-slot one is that it should ensure that for any two members, there should be a timeslot where they at least could meet. And for the 2-slot one, there would be members whose availability does not intersect at all (i.e. one person can't be present at timeslot 1 and the second person can't be present at timeslot 2).

On the other hand — 2-slot is easier to use. Also, we tend to cancel meetings often, and it might be that the intention for having a 3-timeslot system is defeated.

Thoughts?

[Trott]

I prefer 3 slots because it allows us to try to make it such that everyone is likely to attend ~2/3 of the meetings. With 2 slots, the differences get starker. There are people that can attend ~100% of the time and people who can only attend ~50% of the time.

[ChALkeR]

Currently, 15, 40, 45 (Wed 15:00, Thu 16:00, Thu 21:00) seems optimal.
Compared to the current set, that moves 14:00 slot to Wed 15:00, Thu 16:00 remains unchanged, Thu 20 moves one hour later to 21:00.
But we are still missing data from three people at least.

[mmarchini]

I've been sort of away these past three weeks and definitely missed this issue. Will update mine today.

[mcollina]

I have updated as well, sorry :(

[mhdawson]

@ChALkeR can you get the updated suggestions and then we'll move the meeting times based on that.

[mhdawson]

@ChALkeR ping

[ChALkeR]

Let's move to 15, 41, 45, the data hasn't been significantly updated in a while.

That's Wed 15:00, Thu 17:00, Thu 21:00 UTC.
Everything moves by +1 hour, and one moves from Thu to Wed.

[mcollina]

I just realized I had not considered daylight savings :(. My availability at Thu 17:00 is significantly low. Probably does not change things.

[mhdawson]

I think one moved by +2 hours, in any case schedule update, closing.

[ChALkeR]

With updated data optimal seems to be 15, 40, 45 or 14, 40, 45 (mostly equivalent).

That's Wed 15 (or 14), Thu 16, Thu 21.

Upd: Wed 14 seems somewhat better, so: Wed 14, Thu 16, Thu 21.

[ChALkeR]

@mhdawson is there still chance we could update that again to the above (Wed 14, Thu 16, Thu 21) ? =)