-
Notifications
You must be signed in to change notification settings - Fork 133
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 2020-04-23 #852
Comments
Didn't nodejs/docker-node#1238 get discussed last time? |
@sam-github yes but we agreed to leave on the agenda in case the discussion stalled out and there was an ask to the TSC |
Removing nodejs/admin#492 as we discussed last time and no further discussion is needed. |
Those in favour of keeping Yarn in v14 landed the release PR in docker-node, so I closed the issue and removed the label |
Added |
Moderation report: No activity this week. @nodejs/moderation @nodejs/tsc @nodejs/community-committee |
Hello, strategic initiative folks! Sorry for the late notice, but care to put an update in a comment here if you have a few minutes? Thanks! Modules @MylesBorins |
No update. |
No update from me. |
|
There are two prototypes for including more of the bootstrap process into the startup snapshot, with different designs: nodejs/node#32761 and nodejs/node#32984 . Both are blocked by a V8 issue and there is a WIP in the upstream to fix it . I wrote a design doc about the differences in these design options in these two PRs, as well as some potential options not yet explored. (For this work to land, each of the points in there could take one of the options available on their own). It would be helpful if people interested can give feedback about these options in the doc. |
Crashing on unhandledRejection come to be again in: nodejs/node#33021. This is going to be contentious (again), and it might end up for a vote at some point. Take a look. |
No updates from me either. Will probably start working again on the V8 8.3 update PR next week. |
If nodejs/node#33021 goes to a vote, and this PR is vetoed, we should discuss what to do with the current deprecation warning as well. |
QUIC Strategic initiative update is: been getting some excellent feedback and review and have been continuing work accordingly. No significant update for this week however. |
I do have an update for the private section of the call today. |
PR for minutes: #854 |
Time
UTC Thu 23-Apr-2020 21:00 (09: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
nodejs/docker-node
nodejs/TSC
nodejs/admin
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.
Many of us will be on IRC in #node-dev on Freenode if you'd like to interact, we have a Q/A session scheduled at the end of the meeting if you'd like us to discuss anything in particular. @nodejs/collaborators in particular if there's anything you need from the TSC that's not worth putting on as a separate agenda item, this is a good place for that.
Invitees
Please use the following emoji reactions in this post to indicate your
availability.
The text was updated successfully, but these errors were encountered: