|
| 1 | +# Node.js Technical Steering Committee (TSC) Meeting 2024-08-14 |
| 2 | + |
| 3 | +## Links |
| 4 | + |
| 5 | +* **Recording**: <https://www.youtube.com/watch?v=EMqANecYmHs> |
| 6 | +* **GitHub Issue**: <https://github.com/nodejs/TSC/issues/1606> |
| 7 | +* **Minutes Google Doc**: <https://docs.google.com/document/d/1jw1FljN4_87TWDsnwxzp1KSowTNo1Kl_lxddhFkEAHQ/edit?tab=t.0> |
| 8 | + |
| 9 | +## Present |
| 10 | + |
| 11 | +* Joyee Cheung @joyeecheung (voting member) |
| 12 | +* Gireesh Punathil @gireeshpunathil (voting member) |
| 13 | +* Matteo Collina @mcollina (voting member) |
| 14 | +* Marco Ippolito @marco-ippolito (voting member) |
| 15 | +* Richard Lau @richardlau (voting member) |
| 16 | +* Ruy Adorno @ruyadorno (voting member) |
| 17 | +* Antoine du Hamel @aduh95 (voting member) |
| 18 | +* Paolo Insogna @ShogunPanda (voting member) |
| 19 | +* Ruben Bridgewater @BridgeAR (voting member) |
| 20 | + |
| 21 | +## Agenda |
| 22 | + |
| 23 | +### Announcements |
| 24 | + |
| 25 | +* We have dates for the Node.js collaboration summit in Dublin, November 7-8th 2024. All info: <https://github.com/openjs-foundation/summit/issues/419> |
| 26 | +* New Node.js 22 release with experimental type stripping support. |
| 27 | + |
| 28 | +### Reminders |
| 29 | + |
| 30 | +* Remember to nominate people for the [contributor spotlight](https://github.com/nodejs/node/blob/main/doc/contributing/reconizing-contributors.md#bi-monthly-contributor-spotlight) |
| 31 | + |
| 32 | +### CPC and Board Meeting Updates |
| 33 | + |
| 34 | +\*Extracted from **tsc-agenda** labeled issues and pull requests from the **nodejs org** prior to the meeting. |
| 35 | + |
| 36 | +* No updates. |
| 37 | + |
| 38 | +### nodejs/admin |
| 39 | + |
| 40 | +* Conversion to Enterprise account [#905](https://github.com/nodejs/admin/issues/905) |
| 41 | + * Matteo has converted “nodejs” |
| 42 | + |
| 43 | +* module: unflag detect-module [#53619](https://github.com/nodejs/node/pull/53619) |
| 44 | + * Behind a flag in 22.x and 20.x. The ask is to enable detection by default in Node.js 22.x. |
| 45 | + * Matteo: if we want feedback right away, we should release it now; if we want to be cautious, let's wait for 23.x |
| 46 | + * Antoine: do we expect it to be breaking? |
| 47 | + * Matteo: No |
| 48 | + * Ruy: IMO having feedback earlier is valuable in this case. |
| 49 | + * Joyee: I'm not opposed to releasing, I just wonder what's the strategy for dealing with the potential breakage. |
| 50 | + * Matteo: We're only 2 months away from 22.x being LTS, one could argue it's indeed too short. |
| 51 | + |
| 52 | +* Antoine: IMO 2 months is long enough for getting feedback – and possibly revert if it turns out to be semver-major. |
| 53 | + |
| 54 | +* Matteo: good to land it now, if we need to revert we can mark as semver-major. |
| 55 | + |
| 56 | +* Joyee: we would need a CITGM run |
| 57 | + |
| 58 | +* Richard: We had some issues with CITGM, with a npm regression, causing us to miss the other regression. |
| 59 | + |
| 60 | +* Matteo: Any objections for releasing in 22.x? We are ok to release it in v22, but keep a close look on the CITGM results in case of a breakage. If that happens, we might want to consider labelling it as semver-major. |
| 61 | + |
| 62 | +* _No objections_ |
| 63 | + |
| 64 | +## Strategic Initiatives |
| 65 | + |
| 66 | +No updates this week. |
| 67 | + |
| 68 | +## Upcoming Meetings |
| 69 | + |
| 70 | +* **Node.js Project Calendar**: <https://nodejs.org/calendar> |
| 71 | + |
| 72 | +Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. |
0 commit comments