-
Notifications
You must be signed in to change notification settings - Fork 166
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
Regular Meeting frequency/time update #3503
Comments
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. |
+1, times were not optimal for me either |
+1, neither time works for me right now. |
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. |
UTC 12:00 doesn't seem ideal. Close to lunch break in EU, very early in NA. |
@nodejs/build I created a poll with the UTC times to see what time works better for the team. Please vote 🙏 |
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. |
+1 |
+1 to UTC 2PM |
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. |
It's not moving from Tuesday to Wednesday. IIUC the proposal is to move the time, but keep alternating between Tuesdays and Wednesdays. |
Gotcha - I'd misinterpreted the earlier comment. I'll get to 50% of them then :-) |
@mhdawson do you know how to update the calendar and the issue generation? I am not sure where we need to do the change 🤔 |
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. |
@UlisesGascon calendar is updated. Let me know if it does not look updated to you, otherwise we should be good to go. |
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! |
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?
The text was updated successfully, but these errors were encountered: