-
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
Meetings notes for 2022-06-01 #1236
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,78 @@ | ||
# Node.js Technical Steering Committee (TSC) Meeting 2022-06-01 | ||
|
||
## Links | ||
|
||
* **Recording**: <https://youtu.be/CHatybnLvOk> | ||
* **GitHub Issue**: <https://github.com/nodejs/TSC/issues/1234> | ||
* **Minutes Google Doc**: <https://docs.google.com/document/d/1kH33Sr17DFZMD3DqEPtxM23_co0ghzg58xY7CDAn2LE/edit> | ||
|
||
## Present | ||
|
||
* Matteo Collina @mcollina (TSC) | ||
* Antoine du Hamel @aduh95 (TSC) | ||
* Beth Griggs @BethGriggs (TSC) | ||
* Joyee Cheung @joyeecheung (TSC) | ||
* Darshan Sen @RaisinTen (TSC) | ||
* Gireesh Punathil @gireeshpunathil (TSC) | ||
* Richard Lau @richardlau (TSC) | ||
|
||
## Agenda | ||
|
||
### Announcements | ||
|
||
OpenJS World is next week | ||
We are renaming the branch of nodejs/node to main | ||
|
||
### CPC and Board Meeting Updates | ||
|
||
\*Extracted from **tsc-agenda** labeled issues and pull requests from the **nodejs org** prior to the meeting. | ||
|
||
### nodejs/node | ||
|
||
* Revert the change of network interfaces family from string to integer [#43054](https://github.com/nodejs/node/pull/43054). Also issue “Revert the change of network interfaces family from String to Integer [#43014](https://github.com/nodejs/node/issues/43014)”. | ||
* Antoine is getting some blockers, currently we have to make a choice. Please chime in the issue thread. | ||
|
||
* tools: add `.git-blame-ignore-revs` file [#43017](https://github.com/nodejs/node/pull/43017) | ||
* Matteo: how are going to update the file? | ||
* Darshan: We would need to make a PR | ||
* Antoine: Can we contact GitHub support for add an opt-out option for collaborators who don't want the blame to skip commits? | ||
|
||
* Auto closing old stale PRs [#42981](https://github.com/nodejs/node/issues/42981) | ||
* Gireesh: why are those PR stale? He would focus on fixing them, closed or anyway triaged. | ||
|
||
* Global `fetch` breaks `source-map` [#42638](https://github.com/nodejs/node/issues/42638) | ||
* Matteo pinged Eemeli to see if assembling a release of source-map is possible to close this issue | ||
|
||
* Rename default branch from "master" to "main" [#33864](https://github.com/nodejs/node/issues/33864) | ||
* Richard: build will take of all the CI tasks, individual devs would need to update their machine. | ||
* Matteo: are you updating also node-private? | ||
* Richard: not really, something would need to be done | ||
|
||
* process: add CLI opt to hide experimental warnings [#31000](https://github.com/nodejs/node/pull/31000) | ||
* Matteo: this was managed in the last TSC meeting, we can remove from the agenda. | ||
|
||
### nodejs/TSC | ||
|
||
* Onboard @juanarbol as security steward [#1233](https://github.com/nodejs/TSC/issues/1233) | ||
* Matteo: one day to go | ||
* Recertify moderation team [#1231](https://github.com/nodejs/TSC/issues/1231) | ||
* Matteo: no objections | ||
* End-of-Life dates of Node.js 16 and OpenSSL 1.1.1 do not align [#1222](https://github.com/nodejs/TSC/issues/1222) | ||
* Matteo: Confirmed we are shortening the Node v16 LTS lifetime, anything else is a potential breaking change (Richard looked at alternatives). | ||
* Matteo: Richard is preparing an announcement blog post. | ||
* Add Rafael to Security group <https://github.com/nodejs/TSC/issues/1235> | ||
* Matteo: communicated to everybody in the meeting | ||
|
||
## Strategic Initiatives | ||
|
||
### Startup performace | ||
|
||
* Landed <https://chromium-review.googlesource.com/c/v8/v8/+/3616553> to improve memory safety of the custom snapshots but later reverted it due to regressions - working on a reland. | ||
* Also opened <https://bugs.chromium.org/p/v8/issues/detail?id=12921> to discuss about possible solutions to ensure memory safety of read-only snapshots in V8. Continuing work on this issue. | ||
* mkcodecache is gone after <https://github.com/nodejs/node/pull/43023>, the code cache is now part of Node.js's custom snapshot. | ||
|
||
## Upcoming Meetings | ||
|
||
* **Node.js Project Calendar**: <https://nodejs.org/calendar> | ||
|
||
glick `+GoogleCalendar` at the bottom right to add to your own Google calendar. |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These appear on the same line.