-
Notifications
You must be signed in to change notification settings - Fork 134
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
doc: add minutes for meeting 13 March 2024 (#1517)
* doc: add minutes for meeting 12 March 2024 Signed-off-by: Michael Dawson <midawson@redhat.com> * Make the linter happy * Update meetings/2024-03-13.md Co-authored-by: Geoffrey Booth <webadmin@geoffreybooth.com> * Update meetings/2024-03-13.md Co-authored-by: Geoffrey Booth <webadmin@geoffreybooth.com> * Update meetings/2024-03-13.md Co-authored-by: Geoffrey Booth <webadmin@geoffreybooth.com> * Update meetings/2024-03-13.md Co-authored-by: Geoffrey Booth <webadmin@geoffreybooth.com> * Fixup --------- Signed-off-by: Michael Dawson <midawson@redhat.com> Co-authored-by: Geoffrey Booth <webadmin@geoffreybooth.com>
- Loading branch information
1 parent
9c6d717
commit 0dc0f89
Showing
1 changed file
with
118 additions
and
0 deletions.
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,118 @@ | ||
| # Node.js Technical Steering Committee (TSC) Meeting 2024-03-13 | ||
|
|
||
| ## Links | ||
|
|
||
| * **Recording**: <https://youtube.com/live/QeaIyQ37PnM> | ||
| * **GitHub Issue**: <https://github.com/nodejs/TSC/issues/1516> | ||
|
|
||
| ## Present | ||
|
|
||
| * Antoine du Hamel @aduh95 (voting member) | ||
| * Benjamin Gruenbaum @benjamingr (voting member) | ||
| * Geoffrey Booth @GeoffreyBooth (voting member) | ||
| * Gireesh Punathil @gireeshpunathil (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) | ||
| * Richard Lau @richardlau (voting member) | ||
| * Ruy Adorno @ruyadorno (voting member) | ||
| * Paolo Insogna @ShogunPanda (voting member) | ||
| * Tobias Nießen @tniessen (voting member) | ||
|
|
||
| ## Agenda | ||
|
|
||
| ### Announcements | ||
|
|
||
| * Matteo, collaborator summit is first week of April in London, if you are collaborator please | ||
| reach out if you need any more info on how to join, see you there. | ||
|
|
||
| ### CPC and Board Meeting Updates | ||
|
|
||
| *Extracted from **tsc-agenda** labeled issues and pull requests from the **nodejs org** prior to the meeting. | ||
|
|
||
| * No updates this week. | ||
|
|
||
| ### nodejs/node | ||
|
|
||
| * build: enable `yarn` and `pnpm` Corepack binaries by default | ||
| * Ruy | ||
| * Conversation is suffering because of not having a design doc, goals etc. Request in the PR | ||
| is that we that we have more complete design, document, plans etc. | ||
| * Geoffrey, agree with all of that, challenge is that there is a number of decisions that we have | ||
| not made. Have opened a couple of PRs to put down a number of policies. | ||
| * Michael, one thing to discuss is whether we have consensus if we need more design docs, | ||
| plans, etc before landing the PR. | ||
| * Matteo, something that might be easier might be question of if the project should work | ||
| towards moving npm? That might be a simple fundamental question | ||
| * Geoffrey PR to clarify that - <https://github.com/nodejs/node/pull/51951> | ||
| * Ruy, there is also PR to remove corepack completely | ||
| * Geoffrey let’s talk about the executable question | ||
| * Intent is to clarify if Node.js will bundle binaries which are not vendored into the Node.js deps - <https://github.com/nodejs/node/pull/51994/files> | ||
| * Michael, possibly it should be that Node.js will not enable external links, downloads | ||
| * Antoine, if that PRs lands, would the PR just not update to say add corepack binaries | ||
| * Matteo, guiding principle for what Node.js includes is not necessarily important, but what is | ||
| important that you get reproducible builds. | ||
| * Michael how does this affect discussion does Corepack affect reproducible builds | ||
| * Matteo, corepack fixed issue I raised. | ||
| * Michael, answer question on yarn or pnpm, past vote confirmed we would not include yarn | ||
| and pnpm binaries. | ||
| * Richard, | ||
| * Geoffrey, it saves needing to run a command for yarn and pnpm users but adds burden to project. | ||
| * Michael, key question in my mind is what level of responsibility/overhead we take by | ||
| including a jumper? Threat model was updated to state we don’t take responsibility. | ||
| * don’t believe that it will be effective in trying to wash our hands on it, will likely still | ||
| get vulnerability reports, asks for fixes etc. | ||
| * Ruy, pnpm has been very passive in the discussion, most value to yarn, which is why I | ||
| believe the plans, technical rationale is important. | ||
| * Geoffrey pnpm wants to stay out of it because it’s become heated | ||
| * Matteo, take is that it does not matter, | ||
| * Antoine, Myles suggested we should discuss if Corepack can land it Node.js 22 | ||
|
|
||
| * Possible questions to clarify | ||
| * There is no intention to remove npm - <https://github.com/nodejs/node/pull/51951> (no objections from 13 TSC members in call) | ||
| * Will Node.js install links that enable binaries, scripts, etc. outside of Node.js - | ||
| <https://github.com/nodejs/node/pull/51994> | ||
| * Should the existing PR be blocked on the asks for more design, plans, discussion, and the npm `devEngines` work | ||
|
|
||
| [#51886](https://github.com/nodejs/node/pull/51886) | ||
|
|
||
| * deps: remove corepack [#51981](https://github.com/nodejs/node/pull/51981) | ||
| * see discussion above | ||
|
|
||
| ### nodejs/nodejs.org | ||
|
|
||
| * Redesign suggests all versions of Node.js include corepack [#6441](https://github.com/nodejs/nodejs.org/issues/6441) | ||
| * skipped so we could focus on the corepack discussion | ||
| * globally installing npm should not be the recommended way for Mac and Linux [#6361](https://github.com/nodejs/nodejs.org/issues/6361) | ||
| * skipped so we could focus on the corepack discussion | ||
|
|
||
| ### nodejs/TSC | ||
|
|
||
| * CPC representatives [#1504](https://github.com/nodejs/TSC/issues/1504) | ||
| * skipped so we could focus on the corepack discussion | ||
|
|
||
| ### nodejs/admin | ||
|
|
||
| * Events / Collaborator Summits for 2024 [#814](https://github.com/nodejs/admin/issues/814) | ||
| * skipped so we could focus on the corepack discussion | ||
|
|
||
| ### nodejs/corepack | ||
|
|
||
| * fix: remove npm [#418](https://github.com/nodejs/corepack/pull/418) | ||
| * skipped so we could focus on the corepack discussion | ||
|
|
||
| ### nodejs/next-10 | ||
|
|
||
| * Deep Dive: Advocacy and promotion for the project [#247](https://github.com/nodejs/next-10/issues/247) | ||
| * removed from agenda, deep dive took place | ||
|
|
||
| ## Strategic Initiatives | ||
|
|
||
| ## Upcoming Meetings | ||
|
|
||
| * **Node.js Project Calendar**: <https://nodejs.org/calendar> | ||
|
|
||
| Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. |