-
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 - November 2016 #70
Comments
I'm flying to Tokyo on the 3rd for NodeFest, so the timezone is probably gonna make me skip this one |
Anyone else who plans to attend please respond to the Doodle in the next 24 hours, at which point we'll finalize. Top selections at the moment seem to be: |
The vote is for next Wednesday, 11/9 at 3pm US Pacific so updating the original post accordingly. Also added part of agenda: |
I'll most likely not be able to make it as it's 6am in Tokyo at that time. But it depends on my jetlag ;) |
It's 11pm in Denmark and I have class early morning the following day, so I won't attend either. |
Agenda/Task:
|
(I can technically do that myself, but feel free to do the formalities.) |
@Fishrock123 oh, please do it yourself then. It always takes a while for us, because we don't have the privileges. |
I did the thing. |
I there an issue with the hangouts link or is it just me. It tells me I'm not authorized to start the video call |
Looks like I've got the wrong time. I think the link that converts the to your local time was off by an hour for me. |
Fixed, Daylight Savings Time confusion. Talk to you in about an hour. |
Is the streaming issue from last time fixed (youtube shows "live stream is starting soon") |
Works now for me. |
Notes at #74. Thanks! |
Date/Time
Wednesday November 9, 3:00 PM US Pacific
Click for your local time.
Note that US Daylight Savings Time ends on Sunday November 6.
Join/Watch
If you are primarily observing please use the YouTube channel; Hangouts limits the number of connections. You can interact from YouTube via chat.
Minutes
Agenda
/cc @nodejs/diagnostics @nodejs/post-mortem
The text was updated successfully, but these errors were encountered: