-
Notifications
You must be signed in to change notification settings - Fork 144
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
Confirm/re-evaluate meeting times/schedule? #438
Comments
I'm ok with the current times, but being in EST it's easiest for me, we'll want the input from those at the far ends of the range. |
It would be doable for me to join at UTC 19:00 I'm in the EU / Central tz (21:00) and this timeframe has become impossible for me 😞 |
Similar for me, the later time is just a little bit too late for me to regularly join. |
I too am ok with the current times. It has been a busy end of year for me. I will be attending going forwards. |
I'm also EST, so currently both of the meeting times are fairly accommodating to me at the moment, but am flexible, assuming there are no work meeting conflicts. edit: this tool may help for finding out where we are geographically, and see where we overlap and see if that can help influence the decision |
A few proposals are to move the 3PM EST on Tuesdays
Darcy will setup a doodle to get input on those 2 timeslots. |
Link to the Doodle Calendar: https://doodle.com/poll/cy7ip6bizy3c9y5u Feel free to mark which timeslots work best for you (they should include the two existing times we've been using, as well as other times mentioned by @mhdawson & slots that work around existing Node.js/OpenJS Foundation calls bi-weekly on Wednesdays) |
Tuesdays are usually pretty booked for me so I voted for the Thursday time slots. |
@darcyclarke / @ljharb Currently the meeting times alternate every 2 weeks, between the following : I wasn't sure if the issue / doodle is aiming to:
I am fine with both ways, but was just curious how the replies to the doodle will be applied to the current schedule. |
@BethGriggs, @wesleytodd, @ruyadorno @nodejs/package-maintenance can you fill in the doodle so we can close on an updated time next week. |
Based on the doodle we agreed to move the Tuesday 9 AM time to Thursday at 1-2 ET as well as keeping the current Tuesday 3-4 time, that covers the two most popular times and has at least one time that everybody who responded can make. |
Meeting moved. |
During today's call, we talked briefly about whether the current meeting cadence/timing was meeting our needs. I have no personal opinion here - i'm happy to miss every other meeting for the sake of timezone equity :-) - but it seems useful to make sure that:
If these are currently being met, no changes are needed.
Thoughts?
The text was updated successfully, but these errors were encountered: