-
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 2022-06-29 #1249
Comments
It would be very useful for the TSC to discuss (in the context of the the string formatting discussion) the impact on maintainers of moving things to core from npm and how the project can ensure it does it ethically and in a community friendly way. |
V8 Currency: currently unable to update to >=10.3 due to multiple issues:
|
@mhdawson we can remove nodejs/node#43017 from the agenda now. |
Just noting that issues #43382 and #43413 are related and should be discussed together. |
PR for minutes - #1250 |
Time
UTC Wed 29-Jun-2022 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/node
.git-blame-ignore-revs
file #43017nodejs/i18n
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.
The text was updated successfully, but these errors were encountered: