Node.js Technical Steering Committee (TSC) Meeting 2022-02-03

[mhdawson]

Time

UTC Thu 03-Feb-2022 14:00 (02:00 PM):

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

Or in your local time:

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

Links

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

Agenda

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

nodejs/node

• Managing feature requests #41113
• docs: Clarification around real world risks and use cases of VM module #40718
• Rename default branch from "master" to "main" #33864

nodejs/TSC

• Handling unintended breaking changes #1156
• Invite TSC members in the Google Calendar event for meetings #1133
• vote: future of primordials #1104
• Looking for feedback: Pointer compression in Node.js #790

nodejs/admin

• Update the GItHub management policy for Moderation #656

nodejs/next-10

• Next 10 - Mini summit - Modern HTTP and Documentation #108

Invited

• Antoine du Hamel @aduh95 (TSC)
• Anatoli Papirovski @apapirovski (TSC)
• Beth Griggs @BethGriggs (TSC)
• Ruben Bridgewater @BridgeAR (TSC)
• Сковорода Никита Андреевич @ChALkeR (TSC)
• Colin Ihrig @cjihrig (TSC)
• Danielle Adams @danielleadams (TSC)
• Franziska Hinkelmann @fhinkel (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)
• Darshan Sen @RaisinTen (TSC)
• Richard Lau @richardlau (TSC)
• Robert Nagy @ronag (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.

---

Invitees

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

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

[Trott]

Moderation Team:

• Blocked user: Rename async_hooks.md to VAR5_async_hooks.md node#41705 (comment)
• Blocked user: https://github.com/nodejs/moderation/issues/534
• Blocked user: https://github.com/nodejs/moderation/issues/535

@nodejs/tsc @nodejs/moderation

[mmarchini]

Too early for me, so will share some updates on the Future of build toolchains strategic initiative here:

• Wrote drafts of a preliminary analysis of cmake, gn and bazel based on the information from Strategic initiative: future of Node.js build toolchain #901 and other issues. PRs with those drafts available at https://github.com/nodejs/build-toolchain-next
• Closed Strategic initiative: future of Node.js build toolchain #901, future discussions will continue on the initiative repository
• Also looking at what the first steps should be for native modules toolchain (hopefully we can deal with that before changing things in core, or at least in parallel with it)
• Wondering if we should form a team/WG to tackle this initiative, since it's a huge effort both to plan and implement any solutions in this space. Call for volunteers? (@mhdawson can you call this last item out as part of the announcements at the beginning of the meeting?)

[mcollina]

We should have a private section to go through HackerOne.

[mhdawson]

Wondering if we should form a team/WG to tackle this initiative, since it's a huge effort both to plan and implement any solutions in this space. Call for volunteers? (@mhdawson can you call this last item out as part of the announcements at the beginning of the meeting?)

will do

[mhdawson]

PR for minutes - #1161

[joyeecheung]

Regarding the snapshot compression setting that we talked about in the meeting - I checked t the code base and apparently we have been overriding the default in our own gyp settings and always turning on the compression, so nothing needs to be done for the upstream change.