Node.js Foundation Technical Steering Committee (TSC) Meeting 2019-08-14

[mhdawson]

Time

UTC Wed 14-Aug-2019 15:00 (03:00 PM):

Timezone	Date/Time
US / Pacific	Wed 14-Aug-2019 08:00 (08:00 AM)
US / Mountain	Wed 14-Aug-2019 09:00 (09:00 AM)
US / Central	Wed 14-Aug-2019 10:00 (10:00 AM)
US / Eastern	Wed 14-Aug-2019 11:00 (11:00 AM)
London	Wed 14-Aug-2019 16:00 (04:00 PM)
Amsterdam	Wed 14-Aug-2019 17:00 (05:00 PM)
Moscow	Wed 14-Aug-2019 18:00 (06:00 PM)
Chennai	Wed 14-Aug-2019 20:30 (08:30 PM)
Hangzhou	Wed 14-Aug-2019 23:00 (11:00 PM)
Tokyo	Thu 15-Aug-2019 00:00 (12:00 AM)
Sydney	Thu 15-Aug-2019 01:00 (01: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-08-14&iso=20190814T15
• or http://www.wolframalpha.com/input/?i=03PM+UTC%2C+Aug+14%2C+2019+in+local+time

Links

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

Agenda

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

nodejs/node

• buffer: add Buffer.harden() method #28439
• process: improve nextTick performance #25461
• Building with full-icu by default #19214

nodejs/TSC

• Nominating @BethGriggs to the TSC #718
• Strategic Initiatives - Tracking Issue #423

nodejs/admin

• Tracking issue for update on CPC and Board Meetings #395

Invited

• Anna Henningsen @addaleax (TSC)
• Anatoli Papirovski @apapirovski (TSC)
• Сковорода Никита Андреевич @ChALkeR (TSC)
• Colin Ihrig @cjihrig (TSC)
• Daniel Bevenius @danbev (TSC)
• Franziska Hinkelmann @fhinkel (TSC)
• Jeremiah Senkpiel @Fishrock123 (TSC)
• Gabriel Schulhof @gabrielschulhof (TSC)
• Gireesh Punathil @gireeshpunathil (TSC)
• James Snell @jasnell (TSC)
• Joyee Cheung @joyeecheung (TSC)
• Matteo Collina @mcollina (TSC)
• Michael Dawson @mhdawson (TSC)
• Myles Borins @MylesBorins (TSC)
• Sam Roberts @sam-github (TSC)
• Michaël Zasso @targos (TSC)
• Sakthipriyan Vairamani @thefourtheye (TSC)
• Rich Trott @Trott (TSC)

Observers/Guests

Beth Griggs @BethGriggs (guest participant)

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

[sam-github]

The agenda looks quite similar to last week's agenda, weren't next-tick and full-icu already discussed?

[Trott]

The agenda looks quite similar to last week's agenda, weren't next-tick and full-icu already discussed?

Reviewing the minutes:

• nextTick was something that was determined to be moving in the issue tracker, but that we should leave it on the agenda for this week because it was also likely to run its course (which, by appearances at least, seems to be what happened).

• full-icu was discussed and supposed to be returned to GitHub for discussion, but literally no discussion from Node.js folks has happened there at all in that time. (There's one comment from a user but that's it.)

So I'd be inclined to leave both on the agenda. A path forward needs to be found for these things. (IMO, nextTick is probably easy--TSC members should read the thread and then we have a vote. full-icu is more fraught--will need input from Releasers, Build, maybe others.)

[mhdawson]

+1 to what @Trott said

[Trott]

Invite @cclauss to report on Python 3 stuff and make sure they aren't getting stalled somewhere that we can help?

[sam-github]

I pinged him, but don't know about his availability.

[cclauss]

If that would be of interest to the TSC then I would be available to attend for a discussion on our transition to Python 3 and where I believe that help is needed.

[mhdawson]

@cclauss if you can make it raising awareness would be good both for the TSC and anybody who might what the recording. I'll send you the password through internal slack tomorrow.

[cclauss]

Updated the original post for topics of today's discussion nodejs/node#25789

[addaleax]

I’m assuming we also want to have a brief conversation about tomorrow’s security release, in particular this seems like a good time to decide whether we want to do it in public as suggested in e.g. nodejs/build#1886

[mhdawson]

@addaleax agreed we should discuss that.

[targos]

Minutes: #745

[Trott]

Update from @nodejs/moderation?

[othiym23]

@nodejs/moderation has no activity to report. 👏

[sam-github]

Following the meeting, I had a conversation with @cclauss, and we came up with a bit of an overview of how node chooses python versions, but we also have a number of questions.

See nodejs/node#25789 (comment)