2026-02-11 Express Working Session

[github-actions]

Date/Time

Timezone	Date/Time
America/Los_Angeles	Wed, Feb 11, 2026, 01:00 PM
America/Denver	Wed, Feb 11, 2026, 02:00 PM
America/Chicago	Wed, Feb 11, 2026, 03:00 PM
America/Bogota	Wed, Feb 11, 2026, 04:00 PM
America/New_York	Wed, Feb 11, 2026, 04:00 PM
UTC	Wed, Feb 11, 2026, 09:00 PM
Europe/London	Wed, Feb 11, 2026, 09:00 PM
Europe/Madrid	Wed, Feb 11, 2026, 10:00 PM
Europe/Paris	Wed, Feb 11, 2026, 10:00 PM
Europe/Warsaw	Wed, Feb 11, 2026, 10:00 PM
Europe/Moscow	Thu, Feb 12, 2026, 12:00 AM
Asia/Kolkata	Thu, Feb 12, 2026, 02:30 AM
Asia/Shanghai	Thu, Feb 12, 2026, 05:00 AM
Asia/Tokyo	Thu, Feb 12, 2026, 06:00 AM
Australia/Sydney	Thu, Feb 12, 2026, 08:00 AM

Or in your local time:

• https://www.timeanddate.com/worldclock/fixedtime.html?msg=2026-02-11%20Express%20Working%20Session&iso=20260211T2100&p1=1440&ah=1

Agenda

Extracted from top priority labelled issues and pull requests from expressjs/discussions prior to the meeting.

• OpenCollective tiers #475
• Connect Thanks.dev to OpenCollective #462
• Use Node.js built-in debug and deprecated utilities instead of relying on external packages. #459
• Propose a higher minimum Node.js version for all the packages (CI related) #236
• docs: update governance document to remove outdated sections #386
• charter: update TC membership guidelines to ensure diverse representation #376
• add Github Access Structure Overview section express#5503

Invited

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

Observers/Guests

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

Joining the meeting

• link for participants: https://zoom-lfx.platform.linuxfoundation.org/meeting/95258037175?password=07aad89d-ff43-45df-9b28-f437e167a0b9

---

Please use the following emoji reactions in this post to indicate your
availability.

• 👍 - Attending
• 👎 - Not attending
• 😕 - Not sure yet

[jonchurch]

Gonna skip to stay heads down on some lodash build tooling work that is finally clicking 👍

Im online though, ping me if needed

[Phillip9587]

Hey everyone, I’d really appreciate it if someone could take a look at this body-parser PR that implements the long-outstanding generic parser:
expressjs/body-parser#696
Any feedback or review would be super helpful. Thanks!

[blakeembrey]

We spent most of the time discussing the issues brought up on Slack around needing TC to get things done. Two main takeaways:

1. We're having trouble prioritizing the many issues being created, and many aren't urgent, so providing a priority to review would massively help.
2. There's two levels to complaints: some issues require the TC, but most are actually at a package level and shouldn't even need TC input. We need to work on figuring out how to resolve this tension because the TC shouldn't be blocking work in repos.
3. Related to 2, I maintain a lot of things solo (all tiny packages) and getting reviews is difficult because only the TC can do it according to our governance. We discussed carving something out for solo maintainers.

[blakeembrey]

@jonchurch @UlisesGascon Can either of you look at the PR @Phillip9587 mentioned? You're both captains of the repo.