-
Notifications
You must be signed in to change notification settings - Fork 78
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
Restore Diagnostics Meeting usual frequency #581
Comments
Yeah, sorry about that. I had planned on taking the other time slot and then moved to another timezone for a few months where that's the middle of the night. 😅 |
That's fine! The first timezone is now good for you? |
For now...I'll be on the move again in September, so we'll see how it goes. I'd just not worry too much about accommodating me for now. 😅 |
+1 |
ping @nodejs/diagnostics |
Let's have a chat on this one at the next meeting. |
The next one is another weirdly-timed one, so maybe just decide here? I see no objections though and this has been open for awhile, so maybe just restore it? |
@mhdawson could you do it for us? |
@RafaelGSS, since the issue is already open for this week, I changed it for the next one. I believe I moved it to the righ time. Can you take a look and confirm? |
All good! |
Since #507.
We've had no meeting in the second timezone (10.30 PM UTC) so far, which means that we are having a single meeting per month. I'd like suggest to restore all the meetings to the original timing (example: #574).
We're getting good attendance and might make sense to call more frequently (every 2 weeks at the same time)
The text was updated successfully, but these errors were encountered: