2026-11-23 Express TC Meeting

Open
#537 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
15/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
express, javascript, node.js
Domain
documentation

Research direction

This issue schedules an Express TC meeting and lists its agenda, attendees, and joining details; it does not identify a code or documentation file to change. Read the agenda links for meeting context. The listed outcome is attending or indicating availability with an emoji reaction.

Written by the indexing model from the issue text.

Description

meeting

Date/Time

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

Or in your local time:

Agenda

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

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


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

  • 👍 - Attending
  • 👎 - Not attending
  • 😕 - Not sure yet
Dominant language
No language data
Stars
74
Forks
27
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from expressjs/discussions

All issues in expressjs/discussions

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.