Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Node.js Technical Steering Committee (TSC) Meeting 2022-10-12 #1291

Closed
mhdawson opened this issue Oct 10, 2022 · 7 comments
Closed

Node.js Technical Steering Committee (TSC) Meeting 2022-10-12 #1291

mhdawson opened this issue Oct 10, 2022 · 7 comments
Assignees

Comments

@mhdawson
Copy link
Member

mhdawson commented Oct 10, 2022

Time

UTC Wed 12-Oct-2022 15:00 (03:00 PM):

Timezone Date/Time
US / Pacific Wed 12-Oct-2022 08:00 (08:00 AM)
US / Mountain Wed 12-Oct-2022 09:00 (09:00 AM)
US / Central Wed 12-Oct-2022 10:00 (10:00 AM)
US / Eastern Wed 12-Oct-2022 11:00 (11:00 AM)
EU / Western Wed 12-Oct-2022 16:00 (04:00 PM)
EU / Central Wed 12-Oct-2022 17:00 (05:00 PM)
EU / Eastern Wed 12-Oct-2022 18:00 (06:00 PM)
Moscow Wed 12-Oct-2022 18:00 (06:00 PM)
Chennai Wed 12-Oct-2022 20:30 (08:30 PM)
Hangzhou Wed 12-Oct-2022 23:00 (11:00 PM)
Tokyo Thu 13-Oct-2022 00:00 (12:00 AM)
Sydney Thu 13-Oct-2022 02:00 (02:00 AM)

Or in your local time:

Links

Agenda

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

nodejs/node

  • net: add autoDetectFamily option #44731

nodejs/TSC

  • Re-charter the Ecosystem Security WG #1081

Invited

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
@mhdawson mhdawson self-assigned this Oct 10, 2022
@Trott
Copy link
Member

Trott commented Oct 11, 2022

  • doc: deprecate url.parse() #44919

This landed and can be removed from the agenda. (I'll remove it from the minutes doc and edit this issue to remove it as well.)

@GeoffreyBooth
Copy link
Member

GeoffreyBooth commented Oct 11, 2022

What’s the decision to be made for nodejs/node#44731?

@Trott
Copy link
Member

Trott commented Oct 12, 2022

What’s the decision to be made for nodejs/node#44731?

Our meeting notes from our last meeting say: "on as FYI, discuss in the tracker, please comment in the tracker"

I believe the decision that was asked for at some point was "Can/should we land happy eyeballs in 19.x?" And I believe the answer was "Yes, please." However, there are problems with tests and such. I'm not 100% sure it needs to be on the TSC agenda, but I would prefer it stay and be visible and TSC members actively work to help fix the test issues and anything else blocking it.

I don't think it will be anything to talk about at length during tomorrow's meeting.

@aduh95
Copy link
Contributor

aduh95 commented Oct 12, 2022

I believe the decision that was asked for at some point was "Can/should we land happy eyeballs in 19.x?"

I think the plan was to land it in v18.x before it goes LTS, but yeah that seems unlikely at this point given the state of the PR and there there are no remaining scheduled releases on the v18.x line before it goes LTS. It would need to first land in v19.x, and then it can be backported in the next minor release of v18.x.

@mcollina
Copy link
Member

there is no need for it to be on the agenda

@joyeecheung
Copy link
Member

Progress on startup performance:

@mhdawson
Copy link
Member Author

PR for minutes - #1292

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants