Express TC Meeting - 2016-03-23

[dougwilson]

Who

Invited:

• @expressjs/express-tc
• @mikeal (tsc mentor)
• @jasnell (tsc mentor)
• @wesleytodd (observer)
• @tunniclm (observer)
• @sjanuary (observer)
• @ritch (observer)
• @gabeio (observer)

When

March 23th, 2016 - 23:30 UTC (2016-03-23T23:30:00-0000; http://www.wolframalpha.com/input/?x=0&y=0&i=2016-03-23T23:30:00-0000+in+local+time)

Where

Google Hangouts:

Link for Participants: https://plus.google.com/hangouts/_/hoaevent/AP36tYfXMbG6d5y_pLRU6u-MOx3naD1gMFT2mdQFnRwgLTEgGM-OSQ?hl=en&authuser=0

Link for Observers: https://plus.google.com/events/cq1vt2vfc7vfcfo0de4brj9sjuo

Minutes

Google Doc: TBD

Agenda

• Express Governance document
• Express favicon/logo?
• Express PR review
• AppVeyor on generator

[LinusU]

@dougwilson the time inside the parentheses has the wrong date. I believe it should be 2016-03-23T18:30:00-0500; http://www.wolframalpha.com/input/?x=0&y=0&i=2016-03-23T18:30:00-0500+in+local+time

[dougwilson]

@LinusU, fixed, sorry about that!

[blakeembrey]

Sorry, I'm confused now. Eastern is currently in DST so it's UTC-4. If we're basing on Eastern time it was correct. If it's UTC, @LinusU is correct. I'd suggest changing the Eastern note if it's UTC - perhaps use UTC time as the primary source.

[dougwilson]

Hi @blakeembrey, sorry for any confusion but now even I'm confused. @LinusU pointed out that the date in the timestamp was wrong, because I copied it from the meeting on the 9th and forgot to change it. When I updated it, I also changed the offset to -0400 since the 23rd is on the other side of the daylight change from the 9th. The date @LinusU wrote still had the -0500 offset.

[blakeembrey]

Ah, all good. So Eastern time is fine and everyone else outside the US will be up an hour later? I read it as the time was wrong (pointing out DST), missed the date fact. Happy with it either way, just want it to be clear.

[dougwilson]

@blakeembrey, that's a good question and I didn't even think of it since the TC meeting that just passed had adjusted for the US daylight time and so I figured since there was no objects there, I'd just carry it towards this meeting. Most (all?) or Europe also observes daylight time, though they do not change until later this month, I believe.

[dougwilson]

And in case it helps, I have no objection to pinning the time to 23:30 UTC instead of 18:30 U.S. Eastern. I don't think the original poll for the ideal date/time took this difference into account, so sorry for this re-discussion of the time :)

[LinusU]

I'm sorry to say that I probably won't be able to attend this meeting :(

I would love it if a recording will be made available so that I can catch up after the fact.

[sjanuary]

I'm still on the observers list, but this time doesn't work for me at all unfortunately so please feel free to let someone else have the slot (IIRC they may be limited?) and I will keep on watching the recordings.

[hacksparrow]

Doug, can we make it 23:30 UTC? The proposed time is 4:00 am for me, which is pretty brutal 😁

[dougwilson]

@hacksparrow, sounds good :) Based on the number of people talking here, I've updated it to 23:30 UTC, since the original poll was not clear and the only one who has even gone through daylight time so far is the U.S. basically and even then, not all of us even live in a place that observes daylight time (where I live, daylight time was not recognized until pretty recently).

[hacksparrow]

👍

[crandmck]

OK, so just to confirm: the meeting will be @ 23:30 UTC, which is 4:30pm PDT.

[jasnell]

FYI: Status update on expressjs.com repo move: #8 (comment)