doc: add minutes for 2026-05-06 meeting

meetings/2026-05-06.md

@@ -0,0 +1,99 @@
+# Node.js Technical Steering Committee (TSC) Meeting 2026-05-06
+
+## Links
+
+* **Recording**: <https://www.youtube.com/watch?v=N20irVFli0s>
+* **GitHub Issue**: <https://github.com/nodejs/TSC/issues/1854>
+* **Minutes**: <https://hackmd.io/@openjs-nodejs/SJ5SqQlCbx>
+
+## Present
+
+* Antoine du Hamel @aduh95 (voting member)
+* Ruben Bridgewater @BridgeAR (voting member)
+* Marco Ippolito @marco-ippolito (voting member)
+* Matteo Collina @mcollina (voting member)
+* Filip Skokan @panva (voting member)
+* Rafael Gonzaga @RafaelGSS (voting member)
+* Richard Lau @richardlau (voting member)
+* Robert Nagy @ronag (voting member)
+* Paolo Insogna @ShogunPanda (voting member)
+* Michaël Zasso @targos (voting member)
+
+## Agenda
+
+### Announcements
+
+* [Node.js 26 is OUT](https://nodejs.org/en/blog/release/v26.0.0)! Released yesterday, will be LTS in October. Last release of the old cycle, starting from v27 all releases will be LTS. 27 will not come out in October, but will arrive in April in 1 year from now.
+  * <https://nodejs.org/en/blog/announcements/evolving-the-nodejs-release-schedule>
+* [Nodeconf.eu](https://www.nodeconf.eu/) CFP is open and tickets on sale. Matteo to open an issue to talk about collab summit for the 1st of October.
+
+### Reminders
+
+* Remember to nominate people for the [contributor spotlight](https://github.com/nodejs/node/blob/main/doc/contributing/reconizing-contributors.md#bi-monthly-contributor-spotlight)
+
+### CPC and Board Meeting Updates
+
+*Extracted from **tsc-agenda** labeled issues and pull requests from the **nodejs org** prior to the meeting.
+
+### nodejs/node
+
+* doc: downgrade macOS x64 to Tier 2 [#63055](https://github.com/nodejs/node/pull/63055)
+  * Antoine: Apple will make Mac x64 EOL, it will happen before 26 is EOL. We should ship it in v26.1.0.
+  * Rafael: since we do not have a timeline from Apple. The safest option is to do it for 27.x
+  * Antoine: Making it tier 2 would not break releases, but it set the correct expectations.
+  * Rafael: what is the perspective from the build team?
+  * Antoine: we don't have anyone from Build today.
+  * Matteo: I recommend to move it to tier 2.
+  * Filip: making it tier 2 would only change the public expectation mid-lifetime of a release. This is an accademical discussion, will happen anyway.
+  * Paolo: will it affect 24?
+  * Antoine: no, but we don't know. Rosetta will still work on Mac OS 27 to be released this September.
+  * Rafael: I would prefer to do it eventually when Apple does remove support. I would feel more comfortable.
+  * Paolo: we should not drop support mid-cycle as much as we can.
+  * Antoine: will send an email to the rest of the TSC.
+* JSON Schema validation in Node.js core [#62598](https://github.com/nodejs/node/issues/62598)
+  * Matteo: I added it to create awarness, mostly because it adds 3 modules to core.
+  * ..only 1 name, 3 options..
+  * Matteo: Userland created significant innovation in the last few years, solidyfying something in core is premature.
+  * Rafael: I agree.
+  * Paolo I agree.
+  * Ruben: even if we want to do it at some point, and it's premature to pick a winner.
+* loader: implement package maps [#62239](https://github.com/nodejs/node/pull/62239)
+  * Matteo: we need to call a special meeting for this to discuss with the interested parties.
+* doc: create ai-guidelines and include to CONTRIBUTING [#62105](https://github.com/nodejs/node/pull/62105)
+  * Rafael: Only Joyee approved since my recent change
+  * Matteo: Ping Fedor to check if he still objects on it
+  * Rafael: I will ping you, James, and Fedor to re-review that PR.
+
+* tools: add ncrypto updater script [#61613](https://github.com/nodejs/node/pull/61613)
+  * Filip: we can now sync changes from Node to ncrypto, automation needs to be finished. We could also pull changes from ncrypto into node, this will happen too. I am very opposed to nodejs/node crypto/tls to go through ncrypto rather than nodejs/node.
+* Virtual File System for Node.js [#61478](https://github.com/nodejs/node/pull/61478)
+  * Matteo: split this PR into a smaller one [#63115](https://github.com/nodejs/node/pull/63115), will wait for the AI policy to land this.
+* lib: added logger api in node core [#60468](https://github.com/nodejs/node/pull/60468)
+  * Matteo: no question for the TSC, removed the label.
+
+### nodejs/TSC
+
+* Reconsider ABI stability requirement for V8 updates in majors [#1852](https://github.com/nodejs/TSC/issues/1852)
+  * Matteo: Shall we open an issue asking for feedback to end users?
+  * Antoine: We are in the dark right now.
+  * Joyee: it effects those who use nan and API directly and pre-build their addons, only if they do not version their artifact based on API version. As long as their API is based on node api version. It means that they would need more than one API version artifact per major version.
+  * Antoine: ...
+  * Joyee: adding a field to a struct is an ABI change, not an API change. API changes are much less common. It's API-breaking if you need to rewrite your code. It's ABI-breaking if you need to rebuild.
+  * Matteo: should we talk it about publicly?
+  * Joyee: we should keep versioning the ABI, we still version, just don't tie it with Node.js major. Start a blog post to get the word out and explain the motivation. This is a policy change. We should change our versioning scheme.
+  * Antoine: we can add a new label for ABI changes, and we can decide based on ecosystem response.
+  * Rafael: move to github, good progress.
+* Update meeting schedule [#1832](https://github.com/nodejs/TSC/issues/1832)
+  * Antoine: we need to move with that, I'll send an email.
+
+### nodejs/admin
+
+* Clean up triager team [#1058](https://github.com/nodejs/admin/issues/1058)
+
+## Strategic Initiatives
+
+## Upcoming Meetings
+
+* **Node.js Project Calendar**: <https://nodejs.org/calendar>
+
+Click `Add to Google Calendar` at the bottom left to add to your own Google calendar.