-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
io.js TC Meeting 2015-03-18 #1187
Comments
Can't make it this time, scheduling conflicts. +1 to all 3 agenda items though :) |
Maybe we should set the time to be an hour before on these once everyone switches over to DST? That way it's not an hour later for everyone. |
the time has only changed for people in Pacific, -1 to changing the time and reinforcing the SF-centric nature of ALL THE THINGS |
Huh? It's changed for people here on the east coast too, and by the sounds of it from @bnoordhuis, also in europe? (When does it switch in Australia?) Edit: I suppose this is invalid once UTC switches to DST, if they still do that. |
Sorry no, I was confused by the DST change in the Americas. DST doesn't kick in locally until next week. |
https://m.youtube.com/watch?v=br0NW9ufUUw On Wednesday, March 18, 2015, Ben Noordhuis [email protected]
|
@rvagg I don't think the notes from here were PR'd yet? |
UTC Wed 18-Mar-15 19:00:
Or in your local time:
Please allow time for cat-herding before broadcast starts.
Public YouTube feed: http://www.youtube.com/watch?v=tQwVcuYCiZ4
Google Plus Event page: https://plus.google.com/events/cneon2drmol62u4drm8aegjnrkk
Invited: @bnoordhuis (TC), @piscisaureus (TC), @indutny (TC), @isaacs (TC), @trevnorris (TC), @chrisdickinson (TC, streams), @cjihrig (TC), @mikeal (website), @rvagg (build), @domenic (observer)
Agenda and minutes doc, editable by TC, commentable by everyone else: https://docs.google.com/document/d/1It6PTEBQ7OjW8P88hCLoXvcWKA3Q8dY2eYEHIF6FvS4 (written in markdown so we can put it straight into the repo)
Agenda so far: lifted from issues marked with _tc-agenda_, please label, or ask to have issues labelled if they need to be elevated to TC discussion.
Also #1131 but I've asked to postpone that one for now.
The text was updated successfully, but these errors were encountered: