Skip to content

Add rustdoc team processes #852

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.

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
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

GuillaumeGomez
Copy link
Member

@GuillaumeGomez GuillaumeGomez commented May 21, 2025

cc @rust-lang/rustdoc

Rendered

@ehuss
Copy link
Contributor

ehuss commented May 21, 2025

Can you also add the rustdoc team to triagebot.toml for this directory and give yourselves permissions in https://github.com/rust-lang/team/blob/HEAD/repos/rust-lang/rust-forge.toml?

Copy link
Member

@aDotInTheVoid aDotInTheVoid left a comment

Choose a reason for hiding this comment

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

Thanks for working on this! I'm very happy to see this written down.

@fmease fmease added T-rustdoc Team: Rustdoc needs-fcp This change is insta-stable, so needs a completed FCP to proceed. labels May 21, 2025
@fmease
Copy link
Member

fmease commented May 21, 2025

(This PR will obviously need a T-rustdoc FCP to make it official once most things have been sufficiently fleshed out)

@fmease fmease added the S-waiting-on-team Status: Awaiting review/feedback/decision from relevant team(s) label May 21, 2025
Copy link
Member

@Manishearth Manishearth left a comment

Choose a reason for hiding this comment

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

overall this seems pretty good!

@GuillaumeGomez
Copy link
Member Author

(This PR will obviously need a T-rustdoc FCP to make it official once most things have been sufficiently fleshed out)

Absolutely!

@GuillaumeGomez
Copy link
Member Author

I added the change in triagebot.toml as suggested by @ehuss.

I went through all comments.

@fmease: Hopefully I clarified that the rustdoc "groups" are not full-fledged teams and as such, to be part of them, you need to be a member of the rustdoc team.

Copy link
Contributor

@lolbinarycat lolbinarycat left a comment

Choose a reason for hiding this comment

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

a few nitpicks

Comment on lines 36 to 44
An FCP will be needed for any stabilization of small user-facing changes, like UI/UX changes, new
command-line arguments, new attributes, etc. However, if the change is considered too big/important,
Copy link
Contributor

Choose a reason for hiding this comment

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

We should mention insta-stable GUI changes and the relaxed stability requirements thereof, since those aren't really a thing that exist anywhere else in rust project software.

Copy link
Member Author

Choose a reason for hiding this comment

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

rustdoc GUI is not considered stable (like the HTML/JS/CSS). We just try to limit its changes as much as possible. If it is a user-facing change, we want to go through an FCP to ensure that the reasons behind the change are valid and that majority agrees.

Copy link
Member

Choose a reason for hiding this comment

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

I think it would be good to clarify that UI/UX refers to the programmatic interface of rustdoc, not the web GUI (except for major changes).

Copy link
Contributor

@apiraino apiraino left a comment

Choose a reason for hiding this comment

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

left a comment after a cursory read.

Great work @GuillaumeGomez !

### Can I work on code experimentally before a approval is gained?
Of course! You are free to work on PRs or write code. But those PRs should be marked as
experimental and they should not land, nor should anyone be expected to review them (unless
folks want to).
Copy link
Contributor

Choose a reason for hiding this comment

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

or as draft.

Slightly tangential, there is an ongoing discussion about the overlap between the label S-experimental and the "draft" state that GH offers. I don't know if this discussion is relevant to this bit of documentation, just wanted to mention it.

Copy link
Member Author

Choose a reason for hiding this comment

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

No clue, might be worth revisiting want this discussion has a conclusion.

@GuillaumeGomez GuillaumeGomez force-pushed the rustdoc branch 2 times, most recently from 4da4ad9 to ab7ee18 Compare May 22, 2025 12:41
@GuillaumeGomez GuillaumeGomez force-pushed the rustdoc branch 2 times, most recently from e92f236 to cc605f3 Compare May 22, 2025 20:53
@GuillaumeGomez
Copy link
Member Author

  • Clarified rustdoc team roles
  • Added more information about review policy
  • Fixed typos and links

Copy link
Contributor

@lolbinarycat lolbinarycat left a comment

Choose a reason for hiding this comment

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

looks pretty good, just a few nits about phrasing

Comment on lines 81 to 82
Being part of the front-end group doesn't change your rustdoc team membership. However
you will be assigned for reviews on front-end pull requests and on front-end FCPs.
Copy link
Member

Choose a reason for hiding this comment

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

i think i was just on mobile and didn't read enough of the context 😅

@GuillaumeGomez
Copy link
Member Author

I think it's mostly ready now. I'm gonna switch it to full-fledged PR. I'll start the FCP in a few days if there is no new comment in-between.

@GuillaumeGomez GuillaumeGomez marked this pull request as ready for review June 5, 2025 08:54
@rustbot
Copy link
Collaborator

rustbot commented Jun 5, 2025

r? @Mark-Simulacrum

rustbot has assigned @Mark-Simulacrum.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

@rustbot rustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Jun 5, 2025
@GuillaumeGomez
Copy link
Member Author

@rfcbot fcp merge

@GuillaumeGomez

This comment was marked as outdated.

@rfcbot
Copy link

rfcbot commented Jun 10, 2025

Team member @GuillaumeGomez has proposed to merge this. The next step is review by the rest of the tagged team members:

No concerns currently listed.

Once a majority of reviewers approve (and at most 2 approvals are outstanding), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up!

See this document for info about what commands tagged team members can give me.

@GuillaumeGomez
Copy link
Member Author

GuillaumeGomez commented Jun 10, 2025

30 minutes latency, ok XD. Gonna edit my message haha.

Copy link
Member

@camelid camelid left a comment

Choose a reason for hiding this comment

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

Thanks, this looks great! I left a few comments about small clarifications, but the overall charter looks excellent.

you're looking for the [rustc-dev-guide](https://rustc-dev-guide.rust-lang.org/rustdoc.html).

- [Calendar](./calendar.md)
- *How do I subscribe to the compiler team's calendar?*
Copy link
Member

Choose a reason for hiding this comment

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

nit:

Suggested change
- *How do I subscribe to the compiler team's calendar?*
- *How do I subscribe to the rustdoc team's calendar?*

Comment on lines +3 to +5
The rustdoc team hosts a meeting every second Monday on each month on the
[t-rustdoc/meetings channel on zulip](https://rust-lang.zulipchat.com/#narrow/channel/393423-t-rustdoc.2Fmeetings)
at 21:00 CET (UTC+1) and CEST on summer (UTC+2).
Copy link
Member

Choose a reason for hiding this comment

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

Seems better to just link to the calendar here since this will probably fall out of date.

It also implies some obligations (in some cases, optional obligations):

- Members are expected to respond to FCPs in maximum 4 weeks (28 days).
- Members may take part in various other [maintainer activities] to help the team.
Copy link
Member

Choose a reason for hiding this comment

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

This doesn't have an associated link reference.

Comment on lines +32 to +35
- PRs are pull requests to the [`rust-lang/rust`][rust] repository and are a light-weight
proposal mechanism, suitable for most proposals. PRs are preferred when the proposal is
accompanied by a small patchset (such as stabilization of a compiler flag or addition of
a new target).
Copy link
Member

Choose a reason for hiding this comment

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

People also often open issues for feature proposals. Not critical to mention here, but maybe worth adding.

Copy link
Contributor

Choose a reason for hiding this comment

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

yeah, people often do that since we have no ACP/MCP type process.

Comment on lines 36 to 44
An FCP will be needed for any stabilization of small user-facing changes, like UI/UX changes, new
command-line arguments, new attributes, etc. However, if the change is considered too big/important,
Copy link
Member

Choose a reason for hiding this comment

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

I think it would be good to clarify that UI/UX refers to the programmatic interface of rustdoc, not the web GUI (except for major changes).

@rfcbot
Copy link

rfcbot commented Jul 8, 2025

🔔 This is now entering its final comment period, as per the review above. 🔔

psst @GuillaumeGomez, I wasn't able to add the final-comment-period label, please do so.

@camelid camelid added the final-comment-period Will be merged/postponed/closed in ~10 calendar days unless new substational objections are raised. label Jul 8, 2025
@lolbinarycat
Copy link
Contributor

I think that we should have a section for what happens if you get assigned as a reviewer on a PR that you don't have the time or experience to review properly, such as if it's a large change to a sub-component you haven't worked with before. Having a policy for this would probably be quite helpful for any new team members.

@fmease
Copy link
Member

fmease commented Jul 9, 2025

I think that we should have a section for what happens if you get assigned as a reviewer on a PR that you don't have the time or experience to review properly, such as if it's a large change to a sub-component you haven't worked with before.

This is already covered. See src/rustdoc/reviews.md:

Review Policy

The rustdoc team follows the same review policy as the compiler team. Take a look at
their chapter about it.

which delegates to compiler/reviews.md which in turn states (excerpts):

Basic Reviewing Requirements

There are a number of requirements that need to be met in order for reviewing to
be effective:

  • Reviewers must have a sufficient understanding of the code under review.
    […]
  • Reviewers must have a good idea on whether they are the right person to approve the change.
    […]

(see linked documents for more details)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
final-comment-period Will be merged/postponed/closed in ~10 calendar days unless new substational objections are raised. needs-fcp This change is insta-stable, so needs a completed FCP to proceed. S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. S-waiting-on-team Status: Awaiting review/feedback/decision from relevant team(s) T-rustdoc Team: Rustdoc
Projects
None yet
Development

Successfully merging this pull request may close these issues.