Who's involved?

Maintainers

Maintainers meet regularly and have direct responsibility for overseeing the Rush Stack family of projects. In alphabetical order:
@apostolisms
manages the team that hosts the Rush Stack projects
@D4N14L
feature implementation, focusing on Rush workspaces and Heft
@dmichon-msft
feature implementation, focusing on performance and watch mode
@iclanton
architecture, focusing on Heft and Rush build cache
@octogonz
architecture, community engagement, docs and TSDoc

Affiliate Collaborators

Affiliate Collaborators help keep things running smoothly, but are not as directly involved as the maintainers. Collaboration can take many forms such as triaging issues, reviewing PRs, facilitating design discussions, writing docs, or answering support questions. In alphabetical order:
@Claudiazhaoya
@elliot-nelson
@halfnibble
@sachinjoseph

Alumni

When a Maintainer or Collaborator is no longer actively involved, they become Alumni. In reverse chronological order:
@nickpape
Maintainer 2016-2018
broad contributions including Rush's task scheduler and stream collator
@qz2017
Maintainer 2016-2018
broad contributions including Rush version policies and publishing features
@dgaeta
Collaborator 2017
implemented API Extractor and API Documenter features

Star Contributors

This list recognizes individuals who are not formally affiliated with Rush Stack, but who nonetheless made major contributions that the maintainers would like to acknowledge. If you'd like to nominate someone, let us know. In reverse chronological order:
@adventure-yunfei
recognized for major contributions to API Extractor and API Documenter
@wbern
helped design Rush's multi-project watch mode feature, implemented the @telia/rush-select console
@rbuckton
recognized for major contributions to API Extractor and TSDoc, including the declaration reference syntax
@ThomasMichon
contributed the "installation variants" feature for Rush
@dzearing
pioneered early components such as package-deps-hash, gulp-core-build, and load-themed-styles