Node.js Technical Steering Committee (TSC) Meeting 2020-10-01

[mhdawson]

Time

UTC Thu 01-Oct-2020 15:00 (03:00 PM):

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

Links

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

Agenda

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

nodejs/node

• Make recursive rmdir more strict #35250
• punycode: runtime deprecation #35092
• 2020-10-20, Version 15.0.0 (Current) #35014
• doc: drop minimum waiting time as hard guideline #33879
• Rename default branch from "master" to "main" or something similar #33864
• fs: simplify copy operations and more cleanups #31038

nodejs/admin

• Audit Google account access #389

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]

Please read the conversation at nodejs/node#35250 and comment there. It would be great if we had informed TSC opinions on it ahead of the meeting. I know it's unrealistic to expect everyone to arrive having considered the issue, but if a critical mass could, it would help us avoid the stalling-PR issue here.

[Trott]

Moderation team update: Blocked a user and deleted an issue. Details in https://github.com/nodejs/moderation/issues/347#issuecomment-699651964.

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

[Trott]

Can we invite @bcoe as a guest to provide context for nodejs/node#35250 and answer questions that may come up? (@mhdawson Are you able to send a calendar invite?)

[mhdawson]

Not a calendar invite but I can send the details to @bcoe

[mhdawson]

Details/password sent to @bcoe

[tniessen]

I have a conflicting meeting, might join late.

[MylesBorins]

We can remove #33416 from the agenda

[mhdawson]

@MylesBorins done.

[MylesBorins]

Hey all,

I have an internal planning meeting that will cause me to be ~30 minutes lates. My sincere apologies.

The npm team is in the process of doing the finishing touches on npm v7.0.0-rc.0 and I am expecting a PR to open against Node.js in the next hour or so. I would to have some time in this call to discuss the release get TSC approval to land 7.0.0 in node.js 15.x. This will be a Semver-Major change after the cutoff deadline.

We currently have a targeted release date of Oct 13th to cut v7.0.0, and plan to cut rc's in between to fix bugs as they are identified.

If the agenda is light and you get to this before the 30 minute mark please ping me and I'll drop from the planning call (twitter dm likely the fastest)

[Trott]

would to have some time in this call to discuss the release get TSC approval to land 7.0.0 in node.js 15.x. This will be a Semver-Major change after the cutoff deadline.

In case I'm late or miss the meeting: I am supportive of including npm 7 in 15.x.

I'm going to point out, because we so often forget, that the decision of what to include in a release is up to the Release WG and not the TSC. That said, it's probably good to on record as not opposing this, since the Release WG has always deferred to TSC on that.

[MylesBorins]

@Trott I was under the impression that TSC approval for Semver Major after cutoff was to the TSC. I'd personally be ok with us deferring to release for that. I am not finding any documented policy around this though.

[mhdawson]

My understanding was that in this case it was the TSC who approved Semver Major's after the cutoff as well.

[richardlau]

@Trott I was under the impression that TSC approval for Semver Major after cutoff was to the TSC. I'd personally be ok with us deferring to release for that. I am not finding any documented policy around this though.

It's briefly documented in https://github.com/nodejs/node/blob/master/doc/guides/releases.md#release-branch. It's not TSC approval -- it's no objections.

One month or less before the release date, commits must be cherry-picked into the two branches. To land SEMVER-MAJOR at this time requires no objections from the TSC.

[mhdawson]

@richardlau thanks for finding the wording, it's what I think makes sense. The TSC should be aware, and not have any concerns/objections.