docs: remove @bjohansebas from the Triage Captain and TypeScript Captain - #517
Merged
Conversation
UlisesGascon
approved these changes
Aug 17, 2026
jonchurch
approved these changes
Aug 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As I mentioned to Ulises privately, the project has been stagnant in many areas, and now that I have the energy/time, I’m not really sure where to focus anymore.
My roles as a Triage Captain don’t really help much in terms of driving things forward; it’s mostly approving or requesting changes and reviewing. I’ll just stay focused on the packages where I’m a Captain (and, obviously, docs — I love docs 😄), as well as the QUIC and Fetch model work that Node.js is going to adopt. I’ve already done quite a bit of research on that, and I’d like to help make sure someone picks it up from here so Express can at least evolve alongside Node.js instead of remaining stuck in HTTP/1 forever. Ideally, we should move toward something based on the standards coming out of WinterTC.
By the way, I think there are some things we need to change in the governance to make this less bureaucratic. Attending a meeting shouldn’t be a hard requirement to be a TC member, or at least to become a Captain. Some of us already have the trust of other major projects and even the Foundation itself, and we know what it means to take ownership of a package.
A meeting isn’t going to triage 200+ issues, make releases, or handle the security work across the entire project. :) Just as a reflection, though, several people here are doing an amazing job and are genuinely great at what they do.
I really hope Express keeps evolving and doesn’t fall back into stagnation again. I know there are a lot of packages, but the only really active area seems to be the
jshttporg, and I’m only interested in a few of them, so I’m not really sure how I can help there either.cc: @expressjs/express-tc @expressjs/triagers @expressjs/typescript-wg (Regarding the change in captains.)