Node.js Technical Steering Committee (TSC) Meeting 2022-11-09

[mhdawson]

Time

UTC Wed 09-Nov-2022 22:00 (10:00 PM):

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

Links

• Minutes Google Doc: https://docs.google.com/document/d/1-vP2Dh0VnZZ_6AcNPn2i0yUppPATcMQOfW--qCbKBPM/edit

Agenda

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

nodejs/node

• Request for large-runners on Github CI #45345
• async_hooks: add migration note #45335
• doc: add Node.js Threat Model #45223
• deps: vendor semver #45127
• Inclusion in WinterCG Runtime Keys Proposal #166

nodejs/TSC

• Experimental Features - Security expectations #1299

nodejs/i18n

• Crowdin docs update #714

nodejs/undici

• Stable Fetch #1737

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)
• Geoffrey Booth @GeoffreyBooth (TSC)
• Gireesh Punathil @gireeshpunathil (TSC)
• James Snell @jasnell (TSC)
• Joyee Cheung @joyeecheung (TSC)
• Chengzhong Wu @legendecas (TSC)
• Matteo Collina @mcollina (TSC)
• Michael Dawson @mhdawson (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

[mcollina]

No need to talk about nodejs/undici#1737

[aduh95]

Let's not forget nodejs/tooling#166 (the label was added after the automation ran, so it's not currently on the agenda but it should)

[mhdawson]

@aduh95 added manually to the agend so we don't forget.

[GeoffreyBooth]

Also we should talk about adjusting the meeting schedule now that everyone has updated the spreadsheet.

[Trott]

I think it's too late to change it now, but FYI, this meeting is at the wrong time. It is supposed to be at UTC 9pm. It looks like the job that creates these meetings might have a bug that makes it prejudicial for a particular time zone.

[Trott]

I think it's too late to change it now, but FYI, this meeting is at the wrong time. It is supposed to be at UTC 9pm. It looks like the job that creates these meetings might have a bug that makes it prejudicial for a particular time zone.

The Google Calendar event is similarly at the wrong time because the time is set as Eastern Time rather than UTC. Since both this issue and the calendar are off by one hour, at least people looking to watch the stream won't be watching at a different time from the meeting, so there's that.

[mhdawson]

PR for minutes - #1305

[mhdawson]

@Trott the tools creates the meeting from the Calendar. So whatever the calendar says is when the meeting will be. It's probably because I scheduled the meeting and whatever I schedule is in ET and I would have realized it should have been changed but dit not.

[mhdawson]

Just looked at the calendar and I think I can change the timezone, so when we do the next set of updates I'll see if I can set them in UTC instead of ET.

[Trott]

Minutes PR: #1305

[GeoffreyBooth]

FYI per our discussion in this meeting I reached out to @mcollina but his opinion on the async_hooks docs note was unchanged. Based on new comments added to nodejs/node#45335 since the meeting I think we should put it back on the agenda, for a meeting that I, @mcollina, @jasnell, @cjihrig and @Qard can attend.