|
| 1 | +# Node.js Technical Steering Committee (TSC) Meeting 2025-04-30 |
| 2 | + |
| 3 | +## Links |
| 4 | + |
| 5 | +* **Recording**: didn't stream |
| 6 | +* **GitHub Issue**: <https://github.com/nodejs/TSC/issues/1732> |
| 7 | +* **Minutes Google Doc**: <https://docs.google.com/document/d/1hD3fWwi-J4CyHsg37aiMWzWeMF-kblN0Gki_1JcLU34/edit?tab=t.0> |
| 8 | + |
| 9 | +## Present |
| 10 | + |
| 11 | +* Ruben Bridgewater @BridgeAR (voting member) |
| 12 | +* Gireesh Punathil @gireeshpunathil (voting member) |
| 13 | +* Marco Ippolito @marco-ippolito (voting member) |
| 14 | +* Darshan Sen @RaisinTen (voting member) |
| 15 | +* Robert Nagy @ronag (voting member) |
| 16 | +* Ruy Adorno @ruyadorno (voting member) |
| 17 | +* Paolo Insogna @ShogunPanda (voting member) |
| 18 | + |
| 19 | +## Agenda |
| 20 | + |
| 21 | +### Announcements |
| 22 | +* Marco: next-10 survey ready to be published please review <https://github.com/nodejs/next-10/pull/331> |
| 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 | +* doc: doc that proj has access to linked in [#57401](https://github.com/nodejs/node/pull/57401) |
| 33 | +Waiting for Matteo to come back |
| 34 | + |
| 35 | +* Deadlock at process shutdown [#54918](https://github.com/nodejs/node/issues/54918) |
| 36 | +No update, keeping on the agenda as a reminder |
| 37 | + |
| 38 | +### nodejs/nodejs.org |
| 39 | + |
| 40 | +* feat: supporter page and updated home page [#7552](https://github.com/nodejs/nodejs.org/pull/7552) |
| 41 | +Keeping on the agenda for visibility |
| 42 | + |
| 43 | +### nodejs/TSC |
| 44 | + |
| 45 | +* Let's talk about the CI situation [#1614](https://github.com/nodejs/TSC/issues/1614) |
| 46 | +Gireesh: hard to organize the bounty, distribute money, workload etc… |
| 47 | +Paolo: are we blocked on foundation? |
| 48 | +Gireesh: Could use some help from new contributors. |
| 49 | +Darshan: how do we let contributors know this is a priority |
| 50 | +Marco: we could add it to our technical priorities |
| 51 | + |
| 52 | +* NodeJS Feature Bounty Program [#1723](https://github.com/nodejs/TSC/issues/1723) |
| 53 | +Darshan: someone asked for a feature on loaders, hard to find who to get in touch with from the project. We could create a list of contributors in getting funding in a specific area. Does not go through Openjs |
| 54 | +Paolo: do we list people who are interested in work in a specific area and the specifics are discussed in private (money/time etc…) between the two parts? Looks reasonable |
| 55 | +Darshan: not perfect and the legal part is hard across multiple countries, we could improve it. |
| 56 | +Paolo: maybe the foundation could give legal help? |
| 57 | +Need to make clear that the feature is not guaranteed to land |
| 58 | + |
| 59 | +* Adopt Datadog Test Optimization tool [#1721](https://github.com/nodejs/TSC/issues/1721) |
| 60 | + |
| 61 | +## Strategic Initiatives |
| 62 | + |
| 63 | +none |
| 64 | + |
| 65 | +## Upcoming Meetings |
| 66 | + |
| 67 | +* **Node.js Project Calendar**: <https://nodejs.org/calendar> |
| 68 | + |
| 69 | +Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. |
| 70 | + |
0 commit comments