You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We had discussed this in several places (slack, offline...) and I think make sense to create a proper issue to find a good time slot that works for most of us (cc: @nodejs/build).
Currently the Meetings are every few weeks (3 weeks if I remember well) in different days and timezones (Tuesdays as Wednesdays). Here are the last ones as example: #3500 and #3479.
I think currently one of them is quite out of the Americas/Europe timezone and the other one is quite early for Americas. Do we want to change them? What works best for you?
Taking into account a recent post on the build mailing list it makes sense to stop using the 2200 UTC slot now since that that is usually the most difficult one. The one in that slot that you referenced had three declines in it. And while the 1200UTC one is quite early (0800) for those in Eastern time, I would likely be unable to make it in the hour after that due to another recurring meeting (Two hours later might be ok though if that was desired)
+1 for dropping/moving the UTC 10pm Wednesday meeting -- those just are not happening. The last few I joined at that time were just @mhdawson and myself and the slot is inconvenient for both of us.
Seems like we have agreed on the change. Should we use UTC Wed 12:00 (12:00 PM)?, so both meetings take place at the same time but on different weekdays?
UTC Wed 12:00 (12:00 PM)
UTC Tue 12:00 (12:00 PM)
I think we can create a PR to implement this change and confirm if everyone agrees. I am not sure where this change needs to be made.
Wednesday afternoon is quite horrible for me with calls so chances are I'd miss many of them if that's when it was held. Also if it's fixed in UTC then regardless of which option I choose I'm going to have a definite regular conflict for six months of the year due to time zone differences.
I've just voted for 1200 and 1500UTC (which will work for 50% of the year!) which evens it out at 18% for all options other than 2PM which has 25%, but that slot would completely exclude me.
What was the reason for moving it from Tuesday to Wednesday?
Activity
sxa commentedon Sep 27, 2023
Taking into account a recent post on the build mailing list it makes sense to stop using the 2200 UTC slot now since that that is usually the most difficult one. The one in that slot that you referenced had three declines in it. And while the 1200UTC one is quite early (0800) for those in Eastern time, I would likely be unable to make it in the hour after that due to another recurring meeting (Two hours later might be ok though if that was desired)
richardlau commentedon Sep 27, 2023
+1 for dropping/moving the UTC 10pm Wednesday meeting -- those just are not happening. The last few I joined at that time were just @mhdawson and myself and the slot is inconvenient for both of us.
MoLow commentedon Sep 27, 2023
+1, times were not optimal for me either
mhdawson commentedon Sep 29, 2023
+1, neither time works for me right now.
UlisesGascon commentedon Oct 19, 2023
Seems like we have agreed on the change. Should we use UTC Wed 12:00 (12:00 PM)?, so both meetings take place at the same time but on different weekdays?
I think we can create a PR to implement this change and confirm if everyone agrees. I am not sure where this change needs to be made.
targos commentedon Oct 19, 2023
UTC 12:00 doesn't seem ideal. Close to lunch break in EU, very early in NA.
UlisesGascon commentedon Oct 23, 2023
@nodejs/build I created a poll with the UTC times to see what time works better for the team. Please vote 🙏
https://poll-maker.com/poll4974500x0229494a-152
sxa commentedon Oct 23, 2023
Wednesday afternoon is quite horrible for me with calls so chances are I'd miss many of them if that's when it was held. Also if it's fixed in UTC then regardless of which option I choose I'm going to have a definite regular conflict for six months of the year due to time zone differences.
UlisesGascon commentedon Oct 31, 2023
Seems like UTC 2 PM is the best slot based on the poll results. Should we do the change?
MoLow commentedon Oct 31, 2023
+1
anonrig commentedon Oct 31, 2023
+1 to UTC 2PM
sxa commentedon Oct 31, 2023
I've just voted for 1200 and 1500UTC (which will work for 50% of the year!) which evens it out at 18% for all options other than 2PM which has 25%, but that slot would completely exclude me.
What was the reason for moving it from Tuesday to Wednesday?
targos commentedon Oct 31, 2023
It's not moving from Tuesday to Wednesday. IIUC the proposal is to move the time, but keep alternating between Tuesdays and Wednesdays.
sxa commentedon Oct 31, 2023
Gotcha - I'd misinterpreted the earlier comment. I'll get to 50% of them then :-)
UlisesGascon commentedon Nov 7, 2023
@mhdawson do you know how to update the calendar and the issue generation? I am not sure where we need to do the change 🤔
mhdawson commentedon Nov 14, 2023
To make sure I understand it should be UTC at 2PM UTC alternating between Tuesday and Wednesday every three weeks?
If so I can go ahead and update the calendar to reflect that.
mhdawson commentedon Nov 17, 2023
@UlisesGascon calendar is updated. Let me know if it does not look updated to you, otherwise we should be good to go.
UlisesGascon commentedon Nov 19, 2023
I can see the changes in the online version https://calendar.google.com/calendar/u/0/embed?src=nodejs.org_nr77ama8p7d7f9ajrpnu506c98@group.calendar.google.com 👍.
I will close the issue then.
Thanks a lot @mhdawson!