Node.js Foundation Technical Steering Committee (TSC) Meeting 2018-03-28

[mhdawson]

Time

UTC Wed 28-Mar-2018 15:00 (03:00 PM):

Timezone	Date/Time
US / Pacific	Wed 28-Mar-2018 08:00 (08:00 AM)
US / Mountain	Wed 28-Mar-2018 09:00 (09:00 AM)
US / Central	Wed 28-Mar-2018 10:00 (10:00 AM)
US / Eastern	Wed 28-Mar-2018 11:00 (11:00 AM)
London	Wed 28-Mar-2018 16:00 (04:00 PM)
Amsterdam	Wed 28-Mar-2018 17:00 (05:00 PM)
Moscow	Wed 28-Mar-2018 18:00 (06:00 PM)
Chennai	Wed 28-Mar-2018 20:30 (08:30 PM)
Hangzhou	Wed 28-Mar-2018 23:00 (11:00 PM)
Tokyo	Thu 29-Mar-2018 00:00 (12:00 AM)
Sydney	Thu 29-Mar-2018 02:00 (02:00 AM)

Or in your local time:

• http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Technical%20Steering%20Committee%20(TSC)+Meeting+2018-03-28&iso=20180328T15
• or http://www.wolframalpha.com/input/?i=03PM+UTC%2C+Mar+28%2C+2018+in+local+time

Links

• Minutes Google Doc: https://docs.google.com/document/d/1aaJbzIvyhBIINeBcQaWSivar5EqYShU5G9LiEjvDsEs/edit

Agenda

Extracted from tsc-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/node

• Collaborator nomination @BethGriggs #19376
• Nominate @mafintosh as a collaborator #19148
• Tracking Issue for Runtime Deprecation of Buffer constructor #19079

nodejs/TSC

• Tracking issue for updating TSC on Board Meetings #476
• Strategic Initiatives - Tracking Issue #423

Invited

• Anna Henningsen @addaleax (TSC)
• Сковорода Никита Андреевич @ChALkeR (TSC)
• Colin Ihrig @cjihrig (TSC)
• Daniel Bevenius @danbev (TSC)
• Evan Lucas @evanlucas (TSC)
• Franziska Hinkelmann @fhinkel (TSC)
• Gibson Fahnestock @gibfahn (TSC)
• Jeremiah Senkpiel @Fishrock123 (TSC)
• James M Snell @jasnell (TSC)
• Joyee Cheung @joyeecheung (TSC)
• Matteo Collina @mcollina (TSC)
• Michael Dawson @mhdawson (TSC)
• Myles Borins @MylesBorins (TSC)
• Ali Ijaz Sheikh @ofrobots (TSC)
• Rod Vagg @rvagg (TSC)
• Michaël Zasso @targos (TSC)
• Sakthipriyan Vairamani @thefourtheye (TSC)
• Trevor Norris @trevnorris (TSC)
• Rich Trott @Trott (TSC)

Observers

• Timothy Gu @TimothyGu (observer)

Notes

The agenda comes from issues labelled with tsc-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

Zoom Webinar, I've sent an email with the password.

Public participation

We stream our conference call straight to YouTube so anyone can listen to it live, it should start playing at https://www.youtube.com/c/nodejs+foundation/live when we turn it on. There's usually a short cat-herding time at the start of the meeting and then occasionally we have some quick private business to attend to before we can start recording & streaming. So be patient and it should show up.

Many of us will be on IRC in #node-dev on Freenode if you'd like to interact, we have a Q/A session scheduled at the end of the meeting if you'd like us to discuss anything in particular. @nodejs/collaborators in particular if there's anything you need from the TSC that's not worth putting on as a separate agenda item, this is a good place for that

[mcollina]

I won’t be able to attend as I am traveling.

[Trott]

I can't attend, but the buffer issue seems worth talking about. Specifically, we need to craft a concise statement about why we're doing this. I took on that action item but haven't done it yet. If someone else can take a try at making a draft statement, you'd be doing me a favor.

[rvagg]

won't be attending but I'm trying hard to find my way clear to finish up the OpenSSL PR, it's been in limbo but we need to get it locked down for Node 10. Shigeki has been working on 1.1.0 and 1.1.1 integration and TLS 1.3 got finalised this week so we're on track .. I think.

[TimothyGu]

Looking forward to joining my first TSC meeting!

[MylesBorins]

I plan to attend but I might be up very late prepping the security release.

[thefourtheye]

Unfortunately, I might miss this meeting. Sorry.

[Trott]

Moderation Team report for this week:

• There were some requests for self-moderation, some edited comments, and some deleted comments in a GitHub issue. Moderation repo issue 186.
• Received two empty messages to the CoC reporting email address. Ignored them because they were empty. But just FYI.

@nodejs/community-committee @nodejs/tsc @nodejs/moderation

[evanlucas]

I have a conflicting engagement and won't be able to make it today. Apologies

[ofrobots]

I won't be able to join as this time-slot conflicts with some toddler duties for me.

[Fishrock123]

Meeting link is invalid?

[TimothyGu]

@Fishrock123 There is a new email that went out with the correct link.

[fhinkel]

Sorry, scheduled the wrong thing, I've sent an update in the password email

…

On Wed, Mar 28, 2018 at 4:59 PM Jeremiah Senkpiel ***@***.***> wrote: Meeting link is invalid? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#513 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAGMscEJX42T3gXWo-TXoEBGV4eu5ODGks5ti6VagaJpZM4S7Ff0> .

[addaleax]

I’m sorry I won’t be able to join, but re: the buffer constructor deprecation, it would be great to get some more TSC eyes looking @ nodejs/node#19524

[ChALkeR]

Client join link: https://zoom.us/j/751854357
Web link: https://zoom.us/wc/join/751854357