Node.js Technical Steering Committee (TSC) Meeting 2021-02-04

[mhdawson]

Time

UTC Thu 04-Feb-2021 16:00 (04:00 PM):

Timezone	Date/Time
US / Pacific	Thu 04-Feb-2021 08:00 (08:00 AM)
US / Mountain	Thu 04-Feb-2021 09:00 (09:00 AM)
US / Central	Thu 04-Feb-2021 10:00 (10:00 AM)
US / Eastern	Thu 04-Feb-2021 11:00 (11:00 AM)
EU / Western	Thu 04-Feb-2021 16:00 (04:00 PM)
EU / Central	Thu 04-Feb-2021 17:00 (05:00 PM)
EU / Eastern	Thu 04-Feb-2021 18:00 (06:00 PM)
Moscow	Thu 04-Feb-2021 19:00 (07:00 PM)
Chennai	Thu 04-Feb-2021 21:30 (09:30 PM)
Hangzhou	Fri 05-Feb-2021 00:00 (12:00 AM)
Tokyo	Fri 05-Feb-2021 01:00 (01:00 AM)
Sydney	Fri 05-Feb-2021 03:00 (03:00 AM)

Or in your local time:

• https://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Technical%20Steering%20Committee%20(TSC)+Meeting+2021-02-04&iso=20210204T1600
• or https://www.wolframalpha.com/input/?i=04PM+UTC%2C+Feb+04%2C+2021+in+local+time

Links

• Minutes Google Doc: https://docs.google.com/document/d/14Dp1eLfRoOBJOw4RbH0d3qJeB7cBlFvBWTHyZWEdi8U/edit

Agenda

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

nodejs/node

• TLS: improve compliance with shutdown standard, remove hacks #36111
• Rename default branch from "master" to "main" or something similar #33864

nodejs/docker-node

• Publish packages to GitHub Registry #1410

nodejs/TSC

• any interest in an RFC process? #962
• Apple Silicon plan #886

nodejs/security-wg

• Potential stagnation of open issues on h1 bounty program #654

Invited

• Anatoli Papirovski @apapirovski (TSC)
• Beth Griggs @BethGriggs (TSC)
• Ruben Bridgewater @BridgeAR (TSC)
• Сковорода Никита Андреевич @ChALkeR (TSC)
• Colin Ihrig @cjihrig (TSC)
• Shelley Vohr @codebytere (TSC)
• Daniel Bevenius @danbev (TSC)
• Franziska Hinkelmann @fhinkel (TSC)
• Gabriel Schulhof @gabrielschulhof (TSC)
• Gireesh Punathil @gireeshpunathil (TSC)
• James Snell @jasnell (TSC)
• Joyee Cheung @joyeecheung (TSC)
• Mary Marchini @mmarchini (TSC)
• Matteo Collina @mcollina (TSC)
• Michael Dawson @mhdawson (TSC)
• Myles Borins @MylesBorins (TSC)
• Michaël Zasso @targos (TSC)
• Tobias Nießen @tniessen (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]

Moderation updates:

• Blocked user and deleted issue: https://github.com/nodejs/moderation/issues/347#issuecomment-765176612
• Blocked spam user and hid comments: https://github.com/nodejs/moderation/issues/409
• Blocked a bot: https://github.com/nodejs/moderation/issues/410

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

[Trott]

One thing I want to make sure @nodejs/tsc is aware of: N-API is being renamed NODE-API.

I support changing the name N-API to something else, but the new term does have an obvious downside. The term "Node API" already has a straightforward meaning. Applying it to a specific API is more vague than descriptive.

That said, I don't know that I have better ideas. (Native Bindings API? Addon API? ABI Stability API?)

At least two TSC members (Michael Dawson and Gabriel) were involved in picking the new name, and James opened the issue for changing the name in the first place. so I'm sure there's some support on the TSC for it. And I'm sure most of us know this is happening. (TSC was @-mentioned in that issue.) But I wouldn't be surprised if a handful of us didn't know this was happening. Because renaming an API is a significant change with long-term ramifications, I want to make sure all other TSC folks are aware early so that any concerns can be aired now rather than at the very last minute.

I don't know if this needs to be put on the agenda for the meeting, but this seems like the place to at least bring it up.

[mhdawson]

PR for minutes: #968