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

[mhdawson]

Time

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

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

Links

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

Agenda

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

nodejs/node

• Backporting util/types, path/posix and path/win32 to v15 proposal #35788
• Rename default branch from "master" to "main" or something similar #33864

nodejs/TSC

• More visibility for TSC on performance issues #940

nodejs/admin

• Audit Google account access #389

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]

Should we extend an invitation to @ExE-Boss or are the issues around nodejs/node#35788 sufficiently clear and/or uncontroversial?

[Trott]

Moderation Team Report:

Blocked spam commenter: https://github.com/nodejs/moderation/issues/387
Blocked spam commenter: https://github.com/nodejs/moderation/issues/388
Deleted drive-by issue: https://github.com/nodejs/moderation/issues/347#issuecomment-716729325

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

[Qard]

I'd like to mention nodejs/node#34895 again as it is currently blocked on TSC approvals.

[mhdawson]

It's probably too late to invite @ExE-Boss now, so lets discuss nodejs/node#35788 today and invite him to the next meeting if necessary.

[tniessen]

Scheduling conflict but will be able to join for the first part.

[mhdawson]

PR for minutes: #946