|
| 1 | +# Node.js Technical Steering Committee (TSC) Meeting 2025-10-15 |
| 2 | + |
| 3 | +## Links |
| 4 | + |
| 5 | +* **Recording**: <https://www.youtube.com/watch?v=_zGVw3rHDb4> |
| 6 | +* **GitHub Issue**: <https://github.com/nodejs/TSC/issues/1794> |
| 7 | +* **Minutes**: <https://hackmd.io/@openjs-nodejs/HJL7J85axe> |
| 8 | + |
| 9 | +## Present |
| 10 | + |
| 11 | +* Matteo Collina @mcollina (voting member) |
| 12 | +* Filip Skokan @panva (voting member) |
| 13 | +* James Snell @jasnell (voting member) |
| 14 | +* Ruy Adorno @ruyadorno (voting member) |
| 15 | +* Antoine du Hamel @aduh95 (voting member) |
| 16 | +* Richard Lau @richardlau (voting member) |
| 17 | + |
| 18 | +## Agenda |
| 19 | + |
| 20 | +* Extracted from **tsc-agenda** labeled issues and pull requests from the **nodejs org** prior to the meeting. |
| 21 | + |
| 22 | +### Announcements |
| 23 | + |
| 24 | +* Node.js 25 scheduled to be release today! |
| 25 | + * Deprecation of SlowBuffer was pulled from 24, back in 25 tomorrow. |
| 26 | + * There are going to be people affected. Should have means to upgrade dep trees |
| 27 | + * Need to keep an eye out for other places that are impacted. |
| 28 | +* Volunteers needed for Mac OS X infra, see <https://github.com/nodejs/tsc/issues/1793> for details |
| 29 | + |
| 30 | +### Reminders |
| 31 | + |
| 32 | +* Remember to nominate people for the [contributor spotlight](https://github.com/nodejs/node/blob/main/doc/contributing/reconizing-contributors.md#bi-monthly-contributor-spotlight) |
| 33 | + |
| 34 | +### CPC and Board Meeting Updates |
| 35 | + |
| 36 | +* Approved 2026 budget, includes reduction in support for LFIT (Ryan) ... need volunteers to help fill the gap. |
| 37 | +* No jsconf in 2026, quite possible to have an event in 2027. |
| 38 | +* Currently revising parts of the in-kind contribution model. WIP. |
| 39 | + |
| 40 | +### nodejs/admin |
| 41 | + |
| 42 | +* Transfer DataDog/orchestrion-js to the org [#1011](https://github.com/nodejs/admin/issues/1011) |
| 43 | + * There have been no objections, welcome to the project! |
| 44 | + |
| 45 | +### nodejs/node |
| 46 | + |
| 47 | +* src: change default config to package.json [#59842](https://github.com/nodejs/node/pull/59842) |
| 48 | + * Tabled until people in the call to discuss |
| 49 | +* util: add colorize functionality [#43523](https://github.com/nodejs/node/pull/43523) |
| 50 | + * Re-opened because of questions of recent supply chain attacks. We cannot take on everything that's potentially an issue here. Adding things to core won't solve the problem. |
| 51 | + * Might not be relevant due to styleText, other additions |
| 52 | + * We're not opposed to landing this stuff if it's useful, just not for the reasons of supply chain attack mitigation |
| 53 | + |
| 54 | +### nodejs/build |
| 55 | + |
| 56 | +* web-infra access to search console [#4127](https://github.com/nodejs/build/issues/4127) |
| 57 | + * Approved in the latest TSC meeting |
| 58 | + |
| 59 | +### nodejs/TSC |
| 60 | + |
| 61 | +* Update charter with communication responsibilities [#1754](https://github.com/nodejs/TSC/pull/1754) |
| 62 | + * Tabled for Nov 5 meeting |
| 63 | +* Self-serve model for funding Node.js work [#1747](https://github.com/nodejs/TSC/issues/1747) |
| 64 | + * Tabled for Nov 5 meeting |
| 65 | +* Let's talk about the CI situation [#1614](https://github.com/nodejs/TSC/issues/1614) |
| 66 | + * We have funds currently.. expected to be more in 2026, we can viably do a RFP. |
| 67 | + * The biggest challenge is paying attention to the issues and pushing follow up. |
| 68 | + * Automation only gets us so far, we need someone to actually fix things |
| 69 | + * Next step: draft RFP focusing on burndown of existing flaky test backlog, get CI as green as possible. 2-3 months time period. Need SOW with $-cap. |
| 70 | + |
| 71 | +## Strategic Initiatives |
| 72 | + |
| 73 | +## Upcoming Meetings |
| 74 | + |
| 75 | +* **Node.js Project Calendar**: <https://nodejs.org/calendar> |
| 76 | + |
| 77 | +Click `Add to Google Calendar` at the bottom left to add to your own Google calendar. |
0 commit comments