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

doc: add minutes for meeting 20 March 2024 #1520

Merged
merged 2 commits into from
Mar 28, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
111 changes: 111 additions & 0 deletions meetings/2024-03-20.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,111 @@
# Node.js Technical Steering Committee (TSC) Meeting 2024-03-20

## Links

* **Recording**: <https://youtube.com/live/wPrDWotnsdA>
* **GitHub Issue**: <https://github.com/nodejs/TSC/issues/1519>

## Present

* Ruben Bridgewater @BridgeAR (voting member)
* Geoffrey Booth @GeoffreyBooth (voting member)
* Joyee Cheung @joyeecheung (voting member)
* Chengzhong Wu @legendecas (voting member)
* Matteo Collina @mcollina (voting member)
* Michael Dawson @mhdawson (voting member)
* Rafael Gonzaga @RafaelGSS (voting member)
* Richard Lau @richardlau (voting member)
* Robert Nagy @ronag (voting member)
* Ruy Adorno @ruyadorno (voting member)
* Paolo Insogna @ShogunPanda (voting member)
* Myles Borins @MylesBorins (regular member)

## Agenda

### Announcements

* Matteo, have people sign up for the collaborator summit. If not and planning to attend please
do. Only needed for in person.

### CPC and Board Meeting Updates

*Extracted from **tsc-agenda** labeled issues and pull requests from the **nodejs org** prior to the meeting.
mhdawson marked this conversation as resolved.
Show resolved Hide resolved

* Matteo - interesting news, going to align the community Directors seats and a few others so
they are elected at the same time. Matteo that means my term is over and there will be an
Election. Plan to run again.

### nodejs/node

* doc: add policy for “placeholder” executables [#52107](https://github.com/nodejs/node/pull/52107)
* covered under discussion for - Corepack
decisions [#1518](https://github.com/nodejs/TSC/issues/1518)

* deps: remove corepack [#51981](https://github.com/nodejs/node/pull/51981)
* deferred discussion to focus on - Corepack decisions [#1518](https://github.com/nodejs/TSC/issues/1518)

* build: enable `yarn` and `pnpm` Corepack binaries by default #51886
* deferred discussion to focus on - Corepack decisions [#1518](https://github.com/nodejs/TSC/issues/1518)

### nodejs/nodejs.org

* Redesign suggests all versions of Node.js include corepack [#6441](https://github.com/nodejs/nodejs.org/issues/6441)

* globally installing npm should not be the recommended way for Mac and Linux [#6361](https://github.com/nodejs/nodejs.org/issues/6361)
* Matteo opened this - goes back in history, if you install in Mac, and Linux because it requires
sudo. If you use nvm to manage versions, it does not work very well.
* Geoffrey, package maintenance team is starting to discuss this approach, should this be
kicked over to that team ? Matteo, website is the issue in terms of what it recommends.
* Michael, clarify do you mean npm or node globally. Matteo, both.
* Myles, past discussion of creating a new/better installer which stalled out. Existing installers
are a challenge.
* Michael, sounds like we should kick over to the package maintenance team
* Matteo we should do something in the short term and in the long term
* Should really not be following recommendations for Mac,
* Paolo other ways to install like brew as well, challenge is that we don’t manage many of the
tools which is a complication in recommending. Ask npm if they can change paths used for
global models
* Michael will transfer issue to package-maint team

### nodejs/TSC

* Corepack decisions [#1518](https://github.com/nodejs/TSC/issues/1518)
* discussed and agreed that next step is to focus on -
<https://github.com/nodejs/node/pull/52107>, we will reserve most of next week’s meeting to
discuss. People please start discussion in the next week so we have as much basis as
possible to start the discussion.

* CPC representatives [#1504](https://github.com/nodejs/TSC/issues/1504)
* open PR for switch Michael will close

### nodejs/admin

* Events / Collaborator Summits for 2024 [#814](https://github.com/nodejs/admin/issues/814)
* Matteo, please register

### nodejs/corepack

* fix: remove npm [#418](https://github.com/nodejs/corepack/pull/418)
* deferred discussion to focus on - Corepack decisions [#1518](https://github.com/nodejs/TSC/issues/1518)

* Questions we agreed last week to try to move forward
* There is no intention to remove npm - <https://github.com/nodejs/node/pull/51951> (no objections from 13 TSC members in call)
* PR landed to document that there is no intension to remove npm

* Will Node.js install links that enable binaries, scripts, etc. outside of Node.js -
<https://github.com/nodejs/node/pull/51994>>
* More discussion this week - as part of - Corepack
decisions [#1518](https://github.com/nodejs/TSC/issues/1518)
* Should the existing PR be blocked on the asks for more design, plans, discussion, and the
npm `devEngines` work
* some progress in terms of agreeing we don’t need to rush the decision for Node.js 22.

## Strategic Initiatives

* Startup snapshot: landed patches in V8 to make snapshot context data reproducible. Working on backporting that + patches in Node.js to make the snapshot reproducible. <https://github.com/nodejs/node/pull/50983>

## Upcoming Meetings

* **Node.js Project Calendar**: <https://nodejs.org/calendar>

Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.