Node.js Foundation Technical Steering Committee (TSC) Meeting 2019-02-13

[mhdawson]

Time

UTC Wed 13-Feb-2019 16:00 (04:00 PM):

Timezone	Date/Time
US / Pacific	Wed 13-Feb-2019 08:00 (08:00 AM)
US / Mountain	Wed 13-Feb-2019 09:00 (09:00 AM)
US / Central	Wed 13-Feb-2019 10:00 (10:00 AM)
US / Eastern	Wed 13-Feb-2019 11:00 (11:00 AM)
London	Wed 13-Feb-2019 16:00 (04:00 PM)
Amsterdam	Wed 13-Feb-2019 17:00 (05:00 PM)
Moscow	Wed 13-Feb-2019 19:00 (07:00 PM)
Chennai	Wed 13-Feb-2019 21:30 (09:30 PM)
Hangzhou	Thu 14-Feb-2019 00:00 (12:00 AM)
Tokyo	Thu 14-Feb-2019 01:00 (01:00 AM)
Sydney	Thu 14-Feb-2019 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+2019-02-13&iso=20190213T16
• or http://www.wolframalpha.com/input/?i=04PM+UTC%2C+Feb+13%2C+2019+in+local+time

Links

• Minutes Google Doc: https://docs.google.com/document/d/1ow99XN_btUNt-z-aTa7NCPbB4jKM3g8HCHGREAsJ1xk/edit

Agenda

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

nodejs/node

• process: improve nextTick performance #25461

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

[mhdawson]

I can't make it this week so @mcollina will be chairing.

[Trott]

I can't make it, but I'd propose adding the Buffer constructor deprecation discussion to the agenda. Gotta make a decision for Node.js 12.x and I have a feeling it will require more than one conversation to come to a decision.

nodejs/node#21351
nodejs/node#22584

[joyeecheung]

@Trott Maybe instead of putting it on the regular meeting agenda again, what may help moving this forward is to have a separate meeting with whoever interested in the topic. IIRC, this has been showing up in the regular meetings many times and we've never been able to come to any conclusions in TSC meetings and had to throw it back to the issue tracker, so discussing about it again in a meeting with a limited size of audience probably will not help making any progress.

[Trott]

@joyeecheung Good point. My real goal is to encourage folks to get up to speed on it (or be ready to abstain) because we're going to have to make a decision at some point and it will probably come sooner than everyone expects. You are right that there are better approaches I could be taking here!

[ChALkeR]

I will probably be late or won't make it, due to a one-time schedule conflict.
Upd: looks like the meeting ended already.

[thefourtheye]

No significant moderation activities last week.

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

[Trott]

Closing as there is a minutes PR.