Node.js Foundation Technical Steering Committee (TSC) Meeting 2019-01-30

[mhdawson]

Time

UTC Wed 30-Jan-2019 21:00 (09:00 PM):

Timezone	Date/Time
US / Pacific	Wed 30-Jan-2019 13:00 (01:00 PM)
US / Mountain	Wed 30-Jan-2019 14:00 (02:00 PM)
US / Central	Wed 30-Jan-2019 15:00 (03:00 PM)
US / Eastern	Wed 30-Jan-2019 16:00 (04:00 PM)
London	Wed 30-Jan-2019 21:00 (09:00 PM)
Amsterdam	Wed 30-Jan-2019 22:00 (10:00 PM)
Moscow	Thu 31-Jan-2019 00:00 (12:00 AM)
Chennai	Thu 31-Jan-2019 02:30 (02:30 AM)
Hangzhou	Thu 31-Jan-2019 05:00 (05:00 AM)
Tokyo	Thu 31-Jan-2019 06:00 (06:00 AM)
Sydney	Thu 31-Jan-2019 08:00 (08:00 AM)

Or in your local time:

• http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Technical%20Steering%20Committee%20(TSC)+Meeting+2019-01-30&iso=20190130T21
• or http://www.wolframalpha.com/input/?i=09PM+UTC%2C+Jan+30%2C+2019+in+local+time

Links

• Minutes Google Doc: https://docs.google.com/document/d/10DH2Tsn5NdntAAoINdf365i2YrAXtvlGoBmi30qIfsQ/edit

Agenda

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

nodejs/TSC

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

Invited

• Anna Henningsen @addaleax (TSC)
• Anatoli Papirovski @apapirovski (TSC)
• Сковорода Никита Андреевич @ChALkeR (TSC)
• Colin Ihrig @cjihrig (TSC)
• Daniel Bevenius @danbev (TSC)
• Franziska Hinkelmann @fhinkel (TSC)
• Gabriel Schulhof @gabrielschulhof (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)
• Rich Trott @Trott (TSC)

Observers/Guests

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 link: https://zoom.us/j/611357642
Regular 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.

---

Invitees

Please use the following emoji reactions in this post to indicate your
availability.

• 👍 - Attending
• 👎 - Not attending
• 😕 - Not sure yet

[Trott]

Too early to talk about these?:

• buffer: runtime-deprecate Buffer constructor everywhere by default node#21351
• [WiP] buffer: runtime-deprecate buffer constructor in sync mode node#22584

We need to make a decision for the release in April.

And how about this?:

• process: remove unhandled rejection deprecation warning node#25747

I know we usually like to let conversation play out, but in this case, I wonder if it might be better to put a stake in the ground at this time or relatively soon.

[Trott]

For #651, do we have a short-term solution already and we're just trying to figure out the long-term solution? @gabrielschulhof @ofrobots

[ofrobots]

IMO, #651 shouldn't be on the TSC agenda. A short term solution is available and proposed. Discussion needs to continue on the issue for a longer term solution.

[ChALkeR]

I won't be present, not feeling well.

[Trott]

@mhdawson Since you're the one that put the tsc-agenda label on #651: Are you OK removing it?

[mhdawson]

I'll remove #651 as I think next steps are agreed for now.

[mhdawson]

Despite the light agenda I would like to still have the meeting and try to follow up on an issue that I've not received any responses on through the TSC mailing list.

I'm +1 for adding the 2 that @Trott mentioned as well. In terms of #21351 and #22584 I agree it's not too early and on #25747 I think some discussion might also help.

[rvagg]

No host? I guess we're skipping this one.

[targos]

@rvagg the meeting is tomorrow ;)

[rvagg]

Heh, ok then!

[Trott]

Turns out I probably can't make the meeting today, but if someone else is prepared to frame the Buffer constructor on unhandled rejection conversations, great.

[thefourtheye]

There were no significant moderation actions taken in the last week.

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

[Trott]

Minutes PR: #661