-
Notifications
You must be signed in to change notification settings - Fork 134
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-05-31 #1394
Comments
@mcollina @aduh95 do you want to discuss nodejs/node#47999 in this meeting? I should be able to attend (though we shouldn’t discuss it without @aduh95). |
I would not be able to attend because I'm in Amsterdam for JSNation. |
FWIW I'm not sure discussing this PR at this stage is worth it, I expect it to change quite a bit before it's ready to land. The mid-term goal is to offer an alternative for loading CJS differently, using the ESM loader, and more importantly aims to change how users can hook into the CJS loading mechanism: using the ESM loader hook API instead of monkey-patching. IF that alternative catches up, and the ecosystem shows interest, we can discuss making it the default, but until then the plan would be to hide it behind a (runtime? buildtime?) flag. Matteo did say on the PR that he tagged it for visibility, which I assume means he also thinks there's not much to discuss in the meeting, and rather it's something that should be on the TSC radar – and I agree with that. |
got a clash that I cannot resolve, so will not be able to make it |
PR for minutes - #1395 |
Time
UTC Wed 31-May-2023 15:00 (03:00 PM):
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/TSC
nodejs/admin
Invited
Antoine du Hamel @aduh95 (voting member)
Anatoli Papirovski @apapirovski (voting member)
Ruben Bridgewater @BridgeAR (voting member)
Colin Ihrig @cjihrig (voting member)
Danielle Adams @danielleadams (voting member)
Geoffrey Booth @GeoffreyBooth (voting member)
Gireesh Punathil @gireeshpunathil (voting member)
James Snell @jasnell (voting member)
Joyee Cheung @joyeecheung (voting member)
Chengzhong Wu @legendecas (voting member)
Matteo Collina @mcollina (voting member)
Michael Dawson @mhdawson (voting member)
Moshe Atlow @MoLow (voting member)
Rafael Gonzaga @RafaelGSS (voting member)
Darshan Sen @RaisinTen (voting member)
Richard Lau @richardlau (voting member)
Robert Nagy @ronag (voting member)
Ruy Adorno @ruyadorno (voting member)
Michaël Zasso @targos (voting member)
Tobias Nießen @tniessen (voting member)
Rich Trott @Trott (voting member)
Beth Griggs @BethGriggs (regular member)
Ben Noordhuis @bnoordhuis (regular member)
Сковорода Никита Андреевич @ChALkeR (regular member)
Shelley Vohr @codebytere (regular member)
Daniel Bevenius @danbev (regular member)
Franziska Hinkelmann @fhinkel (regular member)
Gabriel Schulhof @gabrielschulhof (regular member)
Brian White @mscdex (regular member)
Myles Borins @MylesBorins (regular member)
Rod Vagg @rvagg (regular member)
Tiancheng Timothy Gu @TimothyGu (regular member)
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.
The text was updated successfully, but these errors were encountered: