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 2023-06-07 #1396

Closed
mhdawson opened this issue Jun 5, 2023 · 7 comments
Closed

Node.js Technical Steering Committee (TSC) Meeting 2023-06-07 #1396

mhdawson opened this issue Jun 5, 2023 · 7 comments
Assignees

Comments

@mhdawson
Copy link
Member

mhdawson commented Jun 5, 2023

Time

UTC Wed 07-Jun-2023 19:00 (07:00 PM):

Timezone Date/Time
US / Pacific Wed 07-Jun-2023 12:00 (12:00 PM)
US / Mountain Wed 07-Jun-2023 13:00 (01:00 PM)
US / Central Wed 07-Jun-2023 14:00 (02:00 PM)
US / Eastern Wed 07-Jun-2023 15:00 (03:00 PM)
EU / Western Wed 07-Jun-2023 20:00 (08:00 PM)
EU / Central Wed 07-Jun-2023 21:00 (09:00 PM)
EU / Eastern Wed 07-Jun-2023 22:00 (10:00 PM)
Moscow Wed 07-Jun-2023 22:00 (10:00 PM)
Chennai Thu 08-Jun-2023 00:30 (12:30 AM)
Hangzhou Thu 08-Jun-2023 03:00 (03:00 AM)
Tokyo Thu 08-Jun-2023 04:00 (04:00 AM)
Sydney Thu 08-Jun-2023 05:00 (05: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-gyp

  • DISCUSSION: Release handling #2860

nodejs/node

  • module: make CJS load from ESM loader #47999

nodejs/TSC

  • CLI tools behind a Nodejs namespace #1178

nodejs/admin

  • Archive nodejs/help in favour of a Help Section on Discussions #802

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 Jun 5, 2023
@anonrig
Copy link
Member

anonrig commented Jun 5, 2023

Recent changes from the performance initiative:

  • I opened a back-port for Ada v2.5 to LTS (which comes with 100% performance boost)
  • Khafra started writing mimesniff which will be included in the next release of Ada. https://github.com/ada-url/mimesniff
  • Vinicious opened a pull request for improving the performance of legacy main resolve in module resolution: src,lib: reducing C++ calls of esm legacy main resolve node#48325
  • I opened a pull request for adding NDEBUG=1 to clang flags. Feedback is appreciated. build: add -DNDEBUG=1 to clang flags node#48271
  • Libuv 1.45.0 - 800% faster filesystem ops got merged into Node and will be included in the next release
  • Khavil did some amazing work on improving & reducing the compilation time of Node.js
  • I started focusing on ESM loader performance. Currently reducing the URL invocations.

@mhdawson
Copy link
Member Author

mhdawson commented Jun 5, 2023

@anonrig thanks for the update !

@RafaelGSS
Copy link
Member

I'd like to mention https://github.com/nodejs-private/node-private/issues/420 in this meeting if possible

@gireeshpunathil
Copy link
Member

I cannot make it to this meeting - 12.30 AM for me.

I have made my opinion for nodejs/admin#802 in the issue; if it comes for voting pls register -1 from me.

@richardlau
Copy link
Member

I can't make it to this meeting either. I added nodejs/node-gyp#2860 to the agenda. @rvagg had sent an email last December about not having the time to maintain node-gyp that @mhdawson forwarded to the rest of the TSC in January.

This is specifically about the Javascript wrapper around gyp(-next) (which is its own separate project written in Python).

@GeoffreyBooth
Copy link
Member

I can attend today but only for the first half, in case we want to discuss #1397 or nodejs/node#47999 or anything else I’m involved in.

@mhdawson
Copy link
Member Author

mhdawson commented Jun 7, 2023

PR for minutes - #1398

@mhdawson mhdawson closed this as completed Jun 7, 2023
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