doc: add minutes for 2026-07-08 meeting

meetings/2026-07-08.md

@@ -0,0 +1,118 @@
+# Node.js Technical Steering Committee (TSC) Meeting 2026-07-08
+
+## Links
+
+* **Recording**: <https://www.youtube.com/watch?v=lQYgrEbDU2s>
+* **GitHub Issue**: Not opened before the meeting.
+
+## Present
+
+* Antoine du Hamel @aduh95 (voting member)
+* Filip Skokan @panva (voting member)
+* Marco Ippolito @marco-ippolito (voting member)
+* Matteo Collina @mcollina (voting member)
+* Rafael Gonzaga @RafaelGSS (voting member)
+* Richard Lau @richardlau (voting member)
+* Ruben Bridgewater @BridgeAR (voting member)
+* Ruy Adorno @ruyadorno (voting member)
+* Joe Sepi @joesepi (Guest - Node.js CPC rep)
+
+## Agenda
+
+### Announcements
+
+* Node.js Interactive will be held in Atlanta in mid-August. A Code & Learn is
+  planned as part of the event.
+* [NodeConf EU](https://www.nodeconf.eu/) will be held at the end of September,
+  with a collaborator summit planned for October 1. Collaborators who need a
+  discounted ticket code should contact Matteo.
+
+### CPC and Board Meeting Updates
+
+* No updates.
+
+*Extracted from **tsc-agenda** labeled issues and pull requests from the
+**nodejs org** prior to the meeting.*
+
+### nodejs/admin
+
+* Request to add @Javonne-liu and @Xiao-Tao to @nodejs/platform-loong64 team
+  [#1075](https://github.com/nodejs/admin/issues/1075)
+  * Matteo asked whether there were objections to granting access. There were no
+    objections.
+  * Richard explained that the platform has a CI machine and Jenkins job, but
+    Jenkins logs are now restricted to collaborators and platform teams. Adding
+    these maintainers lets them monitor the job and be contacted for issues on
+    that platform.
+  * Matteo added them to the team during the meeting.
+
+### nodejs/version-management
+
+* Should this repo be archived?
+  [#29](https://github.com/nodejs/version-management/issues/29)
+  * Jordan had asked to keep the repository unarchived. The TSC agreed that the
+    item no longer needed agenda discussion.
+
+### nodejs/node
+
+* Promote Alpine Linux out of experimental to be a tier 2 platform
+  [#62764](https://github.com/nodejs/node/issues/62764)
+  * Richard relayed that Stuart had asked whether the issue still needed TSC
+    discussion.
+  * The direction is to promote Alpine x64 builds to tier 2. Promoting Alpine
+    arm64 may be proposed later.
+  * There were no blockers requiring TSC discussion. Remaining details can be
+    handled by the Build team, and the agenda label can be removed.
+* module: add --experimental-strip-private-modules
+  [#63869](https://github.com/nodejs/node/pull/63869)
+  * Marco said the PR was still blocked and asked whether it should move to a
+    vote.
+  * Matteo said a vote is an option if the objection cannot be resolved, and
+    suggested exploring an alternative that would provide loader machinery or
+    glue for type stripping in `node_modules` instead of adding a new flag.
+  * Marco noted that Amaro already exposes pieces of the functionality, but users
+    generally want Node.js to provide the no-loader experience that motivated
+    type stripping in core.
+  * Antoine said he preferred users who need this behavior writing a small amount
+    of loader glue over Node.js maintaining the larger core change, and reiterated
+    concerns about private packages.
+  * Matteo will write down and experiment with an alternative proposal. Marco can
+    revisit opening a vote after that.
+
+### nodejs/.github
+
+* SECURITY.md: remove outdated sections, explicitely state no CVE
+  [#38](https://github.com/nodejs/.github/pull/38)
+  * Antoine explained that the global `SECURITY.md` used by repositories without
+    their own copy was copied from `nodejs/node`, is outdated, and describes a
+    process that does not fit most repositories in the organization.
+  * Rafael noted that llhttp and llparse vulnerabilities have historically been
+    handled through Node.js CVEs rather than separate project CVEs. If the
+    project wants separate CVEs for those repositories, he recommended waiting for
+    the OpenJS CNA work instead of adding that to the current security release
+    process.
+  * The group agreed with waiting for the OpenJS CNA work for that case and was
+    okay with the documentation update.
+
+### nodejs/TSC
+
+* Draft Statement of Work - Test reliability lead
+  [#1629](https://github.com/nodejs/TSC/issues/1629)
+  * Matteo said there is budget set aside that could potentially be allocated to
+    CI/test reliability work, and that a statement of work with deliverables still
+    needs to be drafted. He is happy to hand this off if someone else can take it;
+    otherwise it will remain in his queue.
+  * Antoine asked whether there is data showing how CI reliability is doing.
+  * Richard pointed to the reliability repository, which collects statistics on
+    recent CI and pull request runs, including pass rates and flaky-test rates.
+  * Filip noted that `@trivikr` has been doing a lot of work closing flaky tests
+    recently.
+  * The item will stay on the agenda for future discussion.
+
+## 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.