-
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
Diag WG meeting times? #158
Comments
I would greatly appreciate an earlier schedule. The reason I rarely attend is that it always happens at a time I ought to be sleeping. |
A time that was mentioned several time is 5pm GMT/9am PST |
I would prefer 7pm GMT if possible. 5pm sort of works but is not ideal. |
Our next meeting will still be at 1PM PST or we'll update the time before that? |
Let's do this week's meeting at 1 PM PST, and we'll close discussion on how to modify the schedule. |
Both times work for me provide there are no conflicts with other wg meetings |
Are the issues for the meetings gone or am I just not seeing them today @mike-kaufman. When wil this week's take place? |
sorry, this wed @ 1PM PST. |
Let's discuss at this week's diag meeting.
|
Issue #167 is for WG meeting on 2018-02-21. |
Discussed at WG meeting. Proposal is we move Diagnostics WG meeting to 11 AM PST/7PM GMT bi-weekly. There will be periodic but infrequent conflicts with the moderation committee. Please thumbs-up/thumbs-down this post if you agree/disagree. /cc @nodejs/diagnostics |
ping @nodejs/diagnostics. Final opportunity to vote on the WG meeting time. Please thumbs-up/thumbs-down this post if you have an opinion. :) |
@mhdawson - I'm not sure I have correct perms to update the time on the node.js calendar - can you do this? |
@mike-kaufman I've updated the calendar. |
current meetings are at 1PM PST/9PM GMT. There's an open question on if this time works for ppl around the world. We're open to considering different times and/or alternating.
There's a proposal to alternate bi-weekly meetings between 9AM PST and 1PM PST.
Please chime in here if the above times don't work.
The text was updated successfully, but these errors were encountered: