2025-06-09 Express TC Meeting

[github-actions]

Date/Time

Timezone	Date/Time
America/Los_Angeles	Mon 09-Jun-2025 14:00 (02:00 PM)
America/Denver	Mon 09-Jun-2025 15:00 (03:00 PM)
America/Chicago	Mon 09-Jun-2025 16:00 (04:00 PM)
America/New_York	Mon 09-Jun-2025 17:00 (05:00 PM)
Europe/London	Mon 09-Jun-2025 22:00 (10:00 PM)
Europe/Amsterdam	Mon 09-Jun-2025 23:00 (11:00 PM)
Europe/Moscow	Tue 10-Jun-2025 00:00 (12:00 AM)
Asia/Kolkata	Tue 10-Jun-2025 02:30 (02:30 AM)
Asia/Shanghai	Tue 10-Jun-2025 05:00 (05:00 AM)
Asia/Tokyo	Tue 10-Jun-2025 06:00 (06:00 AM)
Australia/Sydney	Tue 10-Jun-2025 07:00 (07:00 AM)

Or in your local time:

• https://www.timeanddate.com/worldclock/?iso=2025-06-09T21:00:00

Agenda

Extracted from tc agenda labelled issues and pull requests from expressjs/discussions prior to the meeting.

• Reports of PRs/issues opened or commented on during a week #384
• Exception for Multer to release v3 with ESM #381
• governance.md: add inactivity policy for any roles #378
• charter: update TC membership guidelines to ensure diverse representation #376
• clarify nomination process for Technical Committee members #375
• feat(adr): add TypeScript Working Group ADR #369
• ✨ ADR for Runtime/engine/host/environment support and CI #365
• Partnership process Express x Company #364
• eliminate express CoC handling #349
• Clean up expressjs org #134
• Scrimba + Express partnership expressjs.com#1931
• heads up: Potential Shift to Machine Translations on the Horizon expressjs.com#1676
• proposal: add the security-triage team as security manager of the organizations security-wg#62

Invited

This meeting is open for anyone who wants to attend. Reminder to follow our Code of Conduct.

@expressjs/express-tc
@expressjs/triagers
@expressjs/security-wg

Links

• Minutes:

Joining the meeting

• link for participants: https://zoom-lfx.platform.linuxfoundation.org/meeting/95266714809?password=f37cff1b-cb3a-4a21-9425-210e4714c72e
• For those who just want to watch: https://www.youtube.com/@expressjs-official

[jonchurch]

Minutes:

• Reports of PRs/issues opened or commented on during a week #384 -- decided to land it via PR into the tooling repo
• Exception for Multer to release v3 with ESM #381 -- ESM only multer v3?
  • Chris: v3 is dusty, have we decided if the code in there, the new API direction, has consensus for this being the v3? Or do we need to reevaluate?
  • Wes: would be close to putting a blocking review on converting it to ESM, if it is only for the sole dependency.
  • Ulises: wants to keep supporting CJS for multer, is not in favor of ESM only for multer. The code on the v3 branch (previously the v2/new API exploration code) was experimental at the time, and might not make sense in 2025 currently, we should reevaluate what is on there currently.
  • Jon: I want to see multer still have a CJS pathway for sure, thumbs down to ESM only multer bc it is such an entrypoint to Node.js backend dev, and I dont' want to break that for users who are following tutorials or are unable to debug ESM only issues in their applications. We should take time as a group (in a working session?) to evaluate wht multer in 2025 can look like. There is newer art in the space that we can look to and learn from.
• governance.md: add inactivity policy for any roles #378 - Inactivity policy adjustment, apply it to WG and all roles (Captain, TC, triage groups, etc).
  • we discussed in last week's Working Session, and are in favor with some tweaks. Specifically ensuring it is a MAY not WILL be removed.
  • It would update our TC inactivity policy from 12 months to 6 months
  • So long as it is a human decision, aka TC approval for removing Captains, WG team for removing members, aka most local, captains can remove committers w/o TC under inactivity.
• charter: update TC membership guidelines to ensure diverse representation #376 -- no company majority on TC, charter amendment
  • Wes: sees no risk in adopting, the context is from Node foundation to OpenJS foundation merge this language got hoisted up. Long history in Cross Project Council of hashing out this clause
  • Ulises: added language about contracting and other affiliations (like STF, or Github Stars, etc etc)
  • Wes is suggesting we dont land that language to Charter, but we land it to the Governance doc, and then recircle back on where these different thing should land!
  • Chris: In our next Working Session we should clarify whre these charter items should live.
• clarify nomination process for Technical Committee members #375 -- suggesting that nominations for TC clarified to be only by the TC members
• Chris: not in favor of limiting where nominations come from.
• Ulises/Wes: this likely came from clarifying that we want to ease evaluating self nominations in public settings, so that instead nominations come through with a higher chance of approval via backchanneling interest in joining TC through TC members.