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

[mhdawson]

Time

UTC Wed 04-Apr-2018 17:00 (05:00 PM):

Timezone	Date/Time
US / Pacific	Wed 04-Apr-2018 10:00 (10:00 AM)
US / Mountain	Wed 04-Apr-2018 11:00 (11:00 AM)
US / Central	Wed 04-Apr-2018 12:00 (12:00 PM)
US / Eastern	Wed 04-Apr-2018 13:00 (01:00 PM)
London	Wed 04-Apr-2018 18:00 (06:00 PM)
Amsterdam	Wed 04-Apr-2018 19:00 (07:00 PM)
Moscow	Wed 04-Apr-2018 20:00 (08:00 PM)
Chennai	Wed 04-Apr-2018 22:30 (10:30 PM)
Hangzhou	Thu 05-Apr-2018 01:00 (01:00 AM)
Tokyo	Thu 05-Apr-2018 02:00 (02:00 AM)
Sydney	Thu 05-Apr-2018 03:00 (03: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-04-04&iso=20180404T17
• or http://www.wolframalpha.com/input/?i=05PM+UTC%2C+Apr+04%2C+2018+in+local+time

Links

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

Agenda

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

nodejs/node

• Tracking Issue for Runtime Deprecation of Buffer constructor #19079
• buffer: do deprecation warning outside node_modules #19524
• crypto: add support for AES-CCM #18138
• stream: 'readable' have precedence over flowing #18994

nodejs/TSC

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

nodejs/modules

• Upstream changes to ESM in nodejs/node #42

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

https://zoom.us/j/441168935
Same password as usual

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

[addaleax]

Tracking Issue for Runtime Deprecation of Buffer constructor #19079

Once again, it would be cool if I could remind people that nodejs/node#19524 could really use some TSC review, otherwise it might just not happen (not an outcome I would mind, but this general approach is what we decided on, I think…)

[bmeck]

I'd like to add a small agenda item to discuss if we can unblock Zones which was blocked a long while ago due to signals from Node before we had as good documentation on process / decisions. Just want to give a small 10minute presentation and see if blocking it based upon having Error handling is still true since Promises are becoming more used and have similar concerns.

CC: @trevnorris

[benjamingr]

@bmeck the fact zones is blocked is well documented and due to the same reason domains are deprecated. This decision has been revisited twice already like here: #340 - what chanced since last time?

[gibfahn]

This decision has been revisited twice already like here: #340 - what chanced since last time?

I don't know the history, but given the last comment in that thread, revisiting seems reasonable:

#340 (comment)

[mcollina]

I think a short presentation would be nice. It’s important to note that the diagnostics wg is looking at modeling the async context as well, and I see providing a context local storage implementation a need for the platform.

The concerns about error handling and performance remains.

[trivikr]

The nomination of @mafintosh was announced during the meeting on 2018-03-28 (#513) and he will be onboarded by @jasnell as per update in nodejs/node/issues/19148
This can be removed from agenda.

[Trott]

This can be removed from agenda.

You are no doubt correct that it does not need to be on the agenda. However, for very good reasons, no one is permitted to remove an agenda item except the person who added it in the first place. So @mcollina has to remove it. Otherwise, we'll have to spend 7 seconds on it during the meeting. (Might not be the worst use of time to celebrate an onboarding.)

[mcollina]

@Trott done!

[Trott]

Adding nodejs/node#19524. I anticipate a call for a vote and a need to act quickly, so please review that PR if you have not done so already.

[trivikr]

@Trott That's why I listed it as an observation and didn't tag anyone for action item.
Thanks for tagging @mcollina

[Trott]

Adding nodejs/node#18138 to the agenda. It needs a second TSC reviewer besides @jasnell. Adding it to the agenda solely to identify someone who can review it soon-ish. If a TSC member reviews it between now and the meeting, it can be removed from the agenda.

[mcollina]

Adding nodejs/node#18994 for the same reason.

[mhdawson]

@bmeck are you ready to have it on today's agenda or should we plan for next week?

[fhinkel]

Sorry, can't make it today. Last minute scheduling conflict