Skip to content

Proposal: Unify the three GitHub organizations #458

Closed

Description

@bjohansebas

I feel that having three GitHub organizations causes confusion, especially for new contributors (I’ve been told this quite often when I’m explaining how to contribute to Express).

It also makes it more complicated to maintain the same settings across the three organizations, as well as the same health files in the .github repository.

In addition, we have to replicate teams—for example, the triage and security-triage teams are duplicated across all organizations. We’re also planning to replicate the TypeScript Working Group in the other organizations so we can ping people more easily. If the organizations were unified, this wouldn’t be necessary.

I’m not aware of any historical reason for maintaining three separate organizations, but either way, I think unifying them would simplify everything.

cc: @expressjs/triagers @expressjs/express-tc

Activity

  1. rxmarbles commented on Dec 17, 2025

    @rxmarbles

    I second this motion. We did a similar thing at GoDaddy because we had separate orgs for various OSS projects. Eventually I united them under a single org for better visibility and accessibility

  2. efekrskl commented on Dec 17, 2025

    @efekrskl
    Member

    Great idea! As someone who's trying to get more familiar with the repos we have, this would make things easier.

  3. sheplu commented on Jun 8, 2026

    @sheplu
    Member

    closed for now - can be rediscussed later with justification on the payoff

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions