|
| 1 | +# Node.js Technical Steering Committee (TSC) Meeting 2025-05-28 |
| 2 | + |
| 3 | +## Links |
| 4 | + |
| 5 | +* **Recording**: <https://www.youtube.com/watch?v=7V5o6ohEEH4> |
| 6 | +* **GitHub Issue**: <https://github.com/nodejs/TSC/issues/1743> |
| 7 | + |
| 8 | +## Present |
| 9 | + |
| 10 | +* Antoine du Hamel @aduh95 (voting member) |
| 11 | +* Gireesh Punathil @gireeshpunathil (voting member) |
| 12 | +* Joyee Cheung @joyeecheung (voting member) |
| 13 | +* Matteo Collina @mcollina (voting member) |
| 14 | +* Michael Dawson @mhdawson (voting member) |
| 15 | +* Rafael Gonzaga @RafaelGSS (voting member) |
| 16 | +* Darshan Sen @RaisinTen (voting member) |
| 17 | +* Richard Lau @richardlau (voting member) |
| 18 | +* Filip Skokan (TSC onboardee) |
| 19 | + |
| 20 | +## Agenda |
| 21 | + |
| 22 | +### Announcements |
| 23 | + |
| 24 | +### Reminders |
| 25 | + |
| 26 | +* Remember to nominate people for the [contributor spotlight](https://github.com/nodejs/node/blob/main/doc/contributing/reconizing-contributors.md#bi-monthly-contributor-spotlight) |
| 27 | + |
| 28 | +### CPC and Board Meeting Updates |
| 29 | + |
| 30 | +*Extracted from **tsc-agenda** labeled issues and pull requests from the **nodejs org** prior to the meeting. |
| 31 | + |
| 32 | +* No update this week |
| 33 | + |
| 34 | +### nodejs/node |
| 35 | + |
| 36 | +* doc: clarify the scope of `--disallow-code-generation-from-strings` [#58328](https://github.com/nodejs/node/pull/58328) |
| 37 | + * skipped until next week as we did not haveChengzhong |
| 38 | + |
| 39 | +* Update nghttp2 mc to v1.65.0 [#58293](https://github.com/nodejs/node/pull/58293) |
| 40 | + * Joyee, when sending a request we try http2 before downgrading, diff is not related to that. |
| 41 | + * Matteo, a behavior has been removed from the spec, ngttp2 has implemented that |
| 42 | + * Michael, how many people will be affected? |
| 43 | + * Matteo, its being removed from the standard, API is still then but will be no-ops, |
| 44 | + * Richard, proposal is to backport to 24, would it need to go into LTS lines as otherwise |
| 45 | + we may not be able to update nghttp2 in earlier LTS lines |
| 46 | + * Matteo, we likely will need to upgrade older LTS lines and accept this as well |
| 47 | + * Discussion that we have allowed similar changes due to spec changes in the past |
| 48 | + * No concerns from the TSC members in the meeting |
| 49 | + |
| 50 | +* Revert <https://github.com/nodejs/node/pull/56664> [#58282](https://github.com/nodejs/node/pull/58282) |
| 51 | + * Discussion on the change |
| 52 | + * Technically the revert will be SemVer major, so we need TSC approval for it to land in 24.x |
| 53 | + * Only makes sense if we are going to backport to 24.x |
| 54 | + * Joyee, if we are going to revert we should do sooner than later |
| 55 | + * Rafael, we should land and backport before 24.x gets a larger number of downloads |
| 56 | + * From the TSC members in the meeting there were no objections to reverting |
| 57 | + * Joyee do all of the commits needs to be reverted? |
| 58 | + * Filip possibly only 2 of the 3 need to reverted. |
| 59 | + |
| 60 | +* doc: doc that proj has access to linked in [#57401](https://github.com/nodejs/node/pull/57401) |
| 61 | + * Michael, might as well close as Foundation staff have said no. |
| 62 | + * Joyee, is the same ownership for the other projects in the Foundation ? |
| 63 | + * Michael, good questions, not sure. |
| 64 | + * Darshan, seems like the email discussion has stalled out. Not sure how to make progress |
| 65 | + * Joyee, also agree that I don’t remember we ever agreed to this |
| 66 | + * Matteo, lets talk about it privately. |
| 67 | + |
| 68 | +* Deadlock at process shutdown [#54918](https://github.com/nodejs/node/issues/54918) |
| 69 | + * Joyee, we can remove from the agenda as the fixes have address the pain from the CI, |
| 70 | + and we have not seen issues in the CI for the last few weeks. |
| 71 | + |
| 72 | +### nodejs/nodejs.org |
| 73 | + |
| 74 | +* feat: supporter page and updated home page [#7552](https://github.com/nodejs/nodejs.org/pull/7552) |
| 75 | + * going to take off the agenda until there is more to discuss. |
| 76 | + |
| 77 | +### nodejs/TSC |
| 78 | + |
| 79 | +* Nominating @panva to the TSC [#1740](https://github.com/nodejs/TSC/issues/1740) |
| 80 | + * Welcome! |
| 81 | + |
| 82 | +* May is the month for TSC Elections. [#1737](https://github.com/nodejs/TSC/issues/1737) |
| 83 | + * Only one nomination for each position, will leave open until this Friday and unless there |
| 84 | + Are objections will consider Michae/Matteo re-elected. |
| 85 | + |
| 86 | +* Adopt Datadog Test Optimization tool [#1721](https://github.com/nodejs/TSC/issues/1721) |
| 87 | + * invite Bryan to a future TSC meeting to discuss? |
| 88 | + * Joyee, if somebody is willing to do the work, then why not? |
| 89 | + * Richard, we did turn on something for Windows (buildpulse). We need a volunteer who |
| 90 | + is going to implement/maintain. Not sure the one added for windows helped |
| 91 | + * Possibly misunderstanding of issue, we know there are flaky tests just nobody looking at |
| 92 | + them |
| 93 | + * If there is a volunteer then make it happen then no objections to implementing it? |
| 94 | + * Joyee, will there be human resources |
| 95 | + |
| 96 | +* Let's talk about the CI situation [#1614](https://github.com/nodejs/TSC/issues/1614) |
| 97 | + * Main CI is better |
| 98 | + * Some discussion about the daily masters, IBM i mentioned specifically |
| 99 | + |
| 100 | +## Strategic Initiatives |
| 101 | + |
| 102 | +## Upcoming Meetings |
| 103 | + |
| 104 | +* **Node.js Project Calendar**: <https://nodejs.org/calendar> |
| 105 | + |
| 106 | +Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. |
0 commit comments