2026-06-08 Express TC Meeting

[github-actions]

Date/Time

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

Or in your local time:

• https://www.timeanddate.com/worldclock/fixedtime.html?msg=2026-06-08%20Express%20TC%20Meeting&iso=20260608T1800&p1=1440&ah=1

Agenda

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

• New CORS playground #468
• Batch governance changes and present to CPC #466
• Access to Cloudflare Analytics for the Website Captains #465
• Have a Google Search Console account #464
• Use Node.js built-in debug and deprecated utilities instead of relying on external packages. #459
• Proposal: Unify the three GitHub organizations #458
• Create a .github-private repo expressjs #447
• Update the organization logo #426
• feat: propose sponsors level for opencollective and github #496
• docs: new Collaborator role #486
• docs: update governance to allow long-term contributors to be nominated as committers and captains #485
• Rfc for reusable workflows naming repository #455
• Default workflows part of all repositories #444
• Reusable workflows for npm publish #443

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/95266714809?password=f37cff1b-cb3a-4a21-9425-210e4714c72e

---

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

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

[kjugi]

We have decided to go over topics that are related to people from call.

For #443
@sheplu wanted an opinion from @wesleytodd . Wes raised his concerns about staging workflow. Overall, it seems that manual workflow trigger is somehow expected by both sides (author and reviewers). There is an agreement on that.
@UlisesGascon mentioned that we can try this idea on one of our packages.

For #426
@sheplu raised that new logo is used (almost) across our github orgs now. He will update logo for openCollective.
@UlisesGascon updated logo on youtube channel 🎉

For #447
@sheplu is up for the private repo. All participants agreed on this decision. We can progress further.
We can close this issue as done.

For #496
@sheplu asked for review.

For #458
@wesleytodd raised his concern about the amount of work around this topic.
@sheplu will drop a coment and close the issue that we can revisit this in the future. It would be great to see real benefits and motivation if this should be revisited.

For #459
@wesleytodd Likes the direction. Raised that DEBUG should be revisited. He thinks that we should land a new debug with contract on certain levels so it's very explicit "what and how". @UlisesGascon suggested to have a dedicated package on express org so we can reuse this across our org. @wesleytodd want to make sure that we are explicit about wrapping package to and define clear "why". We are not building a new logger, it's just a compatible wrapper (compatible for our requirements - that's my clarification).

For #466
Sorry - I did not followed on this one. There were no major decisions on this one.

For #465 and #464
@UlisesGascon pitched an idea to setup roles for developers so they can preview some data. We also have a list of captains here: https://github.com/expressjs/discussions/blob/master/docs/contributing/captains_and_committers.md
@kjugi Maybe we should be explicit about the access and who can access what exactly.
@UlisesGascon linked this as an example: https://github.com/nodejs/security-wg/blob/main/MAINTAINERS_THREAT_MODEL.md and put an idea to reuse it for our needs.
We like the idea as it would make it very explicit who can access what (having access is not required tho). We could fast forward the discussions and issues like this in the future.
Overall there were no concerns during the meeting to give access to Cloudflare and Google Search Console. We might need some action point on this one

Please correct me or bring more details if I missed any ✌️

[bjohansebas]

thanks @kjugi