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-11-02 #1302

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

Node.js Technical Steering Committee (TSC) Meeting 2022-11-02 #1302

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

Comments

@mhdawson
Copy link
Member

mhdawson commented Oct 31, 2022

Time

UTC Wed 02-Nov-2022 15:00 (03:00 PM):

Timezone Date/Time
US / Pacific Wed 02-Nov-2022 08:00 (08:00 AM)
US / Mountain Wed 02-Nov-2022 09:00 (09:00 AM)
US / Central Wed 02-Nov-2022 10:00 (10:00 AM)
US / Eastern Wed 02-Nov-2022 11:00 (11:00 AM)
EU / Western Wed 02-Nov-2022 15:00 (03:00 PM)
EU / Central Wed 02-Nov-2022 16:00 (04:00 PM)
EU / Eastern Wed 02-Nov-2022 17:00 (05:00 PM)
Moscow Wed 02-Nov-2022 18:00 (06:00 PM)
Chennai Wed 02-Nov-2022 20:30 (08:30 PM)
Hangzhou Wed 02-Nov-2022 23:00 (11:00 PM)
Tokyo Thu 03-Nov-2022 00:00 (12:00 AM)
Sydney Thu 03-Nov-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

  • deps: vendor semver #45127
  • Adding a Version Checker #44942
  • Add Node.js threat model #45233

nodejs/TSC

  • Experimental Features - Security expectations #1299

nodejs/i18n

  • Crowdin docs update #714

nodejs/undici

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 31, 2022
@mhdawson
Copy link
Member Author

Lets also add this one to the agenda - nodejs/node#45223

@GeoffreyBooth
Copy link
Member

@mcollina is there a question regarding nodejs/node#43658 or did we just forget to remove the tsc-agenda label?

@mcollina
Copy link
Member

mcollina commented Nov 1, 2022

@mcollina is there a question regarding nodejs/node#43658 or did we just forget to remove the tsc-agenda label?

It can be removed. Unfortunately the memory increase still remains. It's probably worthwhile for the TSC to be aware that this is coming and if they are comfortable with and addition 10-15MB of every worker thread created, as well as main process.

@GeoffreyBooth
Copy link
Member

Unfortunately the memory increase still remains. It’s probably worthwhile for the TSC to be aware that this is coming and if they are comfortable with and addition 10-15MB of every worker thread created, as well as main process.

We don’t yet know what the memory increase will be, as the PR isn’t working yet. The question will be whether the increase is worth the benefit of isolating loaders code from application code, and also of isolating loaders code from Node internals (preventing monkey-patching). It’s also very possible that the final implementation doesn’t spawn any worker threads when no user loaders are passed, which would mean that the memory increase is opt-in.

@mhdawson
Copy link
Member Author

mhdawson commented Nov 2, 2022

Removed nodejs/node#43658 from agenda based on suggestion above.

@joyeecheung
Copy link
Member

Startup performance:

@mhdawson
Copy link
Member Author

mhdawson commented Nov 2, 2022

PR for minutes - #1303

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

4 participants