Skip to content

Better define the scope of rustdoc members roles #993

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
GuillaumeGomez wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Better define the scope of rustdoc members roles #993

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
73044de
Better define the scope of rustdoc members roles
GuillaumeGomez Jan 19, 2026
931dd84
Add more precision for the rustdoc front-end role
GuillaumeGomez Jan 26, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 8 additions & 4 deletions src/rustdoc/membership.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -66,10 +66,11 @@ Once you're a member of the rustdoc team, a number of events will happen:
Rustdoc has multiple different areas and team members are not working on all of them. Currently
we have three main areas:

- Front-end: Everything related to HTML/CSS/JS
- JSON backend: Work on the `--output-format=json` backend.
- Front-end: Everything related to HTML/CSS/JS and (HTML) UI/UX changes, including the search, front-end features and front-end settings.
- JSON backend: Work on the `--output-format=json` backend, including the `rustdoc-json-types`
crate.
- Internals: The internals of rustdoc: interacting with the compiler, doctests, generating
rustdoc internal code representation, parsing command line arguments, lints, etc.
rustdoc internal code representation, parsing command line arguments, lints, intra-doc links, etc.

These groups are NOT full-fledged teams, and as such, to be part of any of these groups, you need to
be a member of the rustdoc team.
Expand All @@ -78,10 +79,13 @@ For now, only the front-end group has an official status in the
[team repository](https://github.com/rust-lang/team) and is called `rustdoc-frontend`. If a rustdoc
team member is interested to be part of this group, they can ask to be added into it.

Rustdoc roles handle their own FCPs and RFCs if it only impacts their own area, otherwise other
Copy link
Member

@aDotInTheVoid aDotInTheVoid Jan 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doesn't this require making a rustdoc-json-backend team (which is probably worthwhile doing anyway)?

Copy link
Member Author

@GuillaumeGomez GuillaumeGomez Jan 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, hence why I pinged the infra team. ;)

Copy link
Member

@Kobzol Kobzol Jan 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(Just send a PR to team and that should be it :) )

Copy link
Member Author

@GuillaumeGomez GuillaumeGomez Jan 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Dully noted. ;)

roles or even other teams will be added into the process as needed.

Let's take the front-end group as an example. It is a part of the rustdoc team, so you need to be a
member of the rustdoc team to be able to join this group. Being part of the front-end group means
you are encouraged to be part of the review rotations for front-end pull requests and you will need
to respond on front-end FCPs.
to respond on front-end FCPs and RFCs.

## How promotion decisions are made
[hdam]: #how-promotion-decisions-are-made
Expand Down