Node.js Technical Steering Committee (TSC) Meeting 2021-03-11

[mhdawson]

Time

UTC Thu 11-Mar-2021 14:00 (02:00 PM):

Timezone	Date/Time
US / Pacific	Thu 11-Mar-2021 06:00 (06:00 AM)
US / Mountain	Thu 11-Mar-2021 07:00 (07:00 AM)
US / Central	Thu 11-Mar-2021 08:00 (08:00 AM)
US / Eastern	Thu 11-Mar-2021 09:00 (09:00 AM)
EU / Western	Thu 11-Mar-2021 14:00 (02:00 PM)
EU / Central	Thu 11-Mar-2021 15:00 (03:00 PM)
EU / Eastern	Thu 11-Mar-2021 16:00 (04:00 PM)
Moscow	Thu 11-Mar-2021 17:00 (05:00 PM)
Chennai	Thu 11-Mar-2021 19:30 (07:30 PM)
Hangzhou	Thu 11-Mar-2021 22:00 (10:00 PM)
Tokyo	Thu 11-Mar-2021 23:00 (11:00 PM)
Sydney	Fri 12-Mar-2021 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+2021-03-11&iso=20210311T1400
• or https://www.wolframalpha.com/input/?i=02PM+UTC%2C+Mar+11%2C+2021+in+local+time

Links

• Minutes Google Doc: https://docs.google.com/document/d/1kiUVEOXILGMOrJOZxRXgrZzsOAxIbDW_-0y8xlLfu8k/edit

Agenda

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

nodejs/node

• deps: switch openssl to quictls/openssl #37601
• deps: add Yarn 1.22.5 #37277
• fs: remove permissive rmdir recursive #37216
• TLS: improve compliance with shutdown standard, remove hacks #36111
• Rename default branch from "master" to "main" or something similar #33864

nodejs/TSC

• Charter Undici WG #975
• any interest in an RFC process? #962
• Apple Silicon plan #886

nodejs/admin

• Nodejs-he team #519

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 team report:

• Blocked disruptive user and deleted disruptive content: https://github.com/nodejs/moderation/issues/420
• Blocked disruptive user, https://github.com/nodejs/moderation/issues/421
• Blocked disruptive user: https://github.com/nodejs/moderation/issues/422
• Blocked disruptive user: https://github.com/nodejs/moderation/issues/423

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

[aduh95]

There are a number of open PR in the nodejs/node repo that are waiting for more approval from TSC members to land: https://github.com/nodejs/node/pulls?q=is%3Apr+is%3Aopen+label%3A%22review+wanted%22++label%3Asemver-major. Since the v16 semver cutoff is getting close, I think it would be worth mentioning it in the meeting.

[ronag]

#36816 can be removed from agenda

[cclauss]

I would like to see nodejs/node#36691 landed before we reach the v16 semver cutoff.

We worked very hard to ensure that Node.js was Python 3 compatible before the demise of Python 2 on 1/1/2020. I see no reason why we cannot make Node.js v16 leverage Python 3 only. Node-gyp and Gyp-next have already dropped support for legacy Python. The testing platforms that do not yet have Python 3 on them are just too out-of-date to be relevant anymore.

[richardlau]

I would like to see nodejs/node#36691 landed before we reach the v16 semver cutoff.

We worked very hard to ensure that Node.js was Python 3 compatible before the demise of Python 2 on 1/1/2020. I see no reason why we cannot make Node.js v16 leverage Python 3 only. Node-gyp and Gyp-next have already dropped support for legacy Python. The testing platforms that do not yet have Python 3 on them are just too out-of-date to be relevant anymore.

cc FYI @nodejs/releasers. FWIW I'm working towards unblocking nodejs/node#36691 on the build infra side in nodejs/build#2507.

[mhdawson]

@ronag thanks, removed

[mhdawson]

We cancelled this week as we did not have enough people this time.

[Trott]

• any interest in an RFC process? #962

I read through some prior art on this this week and have been thinking through a proposal for something lightweight that is intended to resolve some of the problems surfaced in that issue. More soon.

[Trott]

We cancelled this week as we did not have enough people this time.

Because low meeting attendance is one of three metrics specified in the TSC Charter that can trigger automatic removal from the TSC, I'm going to document the six people who were there today: @Trott @BethGriggs @mhdawson @jasnell @mcollina @cjihrig

[richardlau]

We cancelled this week as we did not have enough people this time.

Because low meeting attendance is one of three metrics specified in the TSC Charter that can trigger automatic removal from the TSC, I'm going to document the six people who were there today: @Trott @BethGriggs @mhdawson @jasnell @mcollina @cjihrig

I don't know how attendance is currently quantified, but it might be easier in cases like this one to still have a minutes doc with the attendees filled in so that it's simpler to search attendances (e.g. by grepping through the minutes)?