2026-11-18 Express Working Session

Open
#536 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
1/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
express, node.js

Research direction

This is a scheduled Express working session announcement; no source files or tests are mentioned. Read the agenda links and meeting details to understand the session, then use the listed reactions to indicate availability. There is no code change or completion criterion for a first contribution.

Written by the indexing model from the issue text.

Description

meeting

Date/Time

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

Or in your local time:

Agenda

Extracted from top priority 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.