-
Notifications
You must be signed in to change notification settings - Fork 201
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
base: master
Are you sure you want to change the base?
Conversation
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? |
There was a problem hiding this 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.
(This PR will obviously need a T-rustdoc FCP to make it official once most things have been sufficiently fleshed out) |
There was a problem hiding this 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!
Absolutely! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
a few nitpicks
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, |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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).
There was a problem hiding this 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). |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
4da4ad9
to
ab7ee18
Compare
e92f236
to
cc605f3
Compare
|
There was a problem hiding this 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
src/rustdoc/membership.md
Outdated
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. |
There was a problem hiding this comment.
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 😅
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. |
rustbot has assigned @Mark-Simulacrum. Use |
@rfcbot fcp merge |
This comment was marked as outdated.
This comment was marked as outdated.
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. |
30 minutes latency, ok XD. Gonna edit my message haha. |
Add more information about review policy Fix typos and links
There was a problem hiding this 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.
src/rustdoc/index.md
Outdated
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?* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit:
- *How do I subscribe to the compiler team's calendar?* | |
- *How do I subscribe to the rustdoc team's calendar?* |
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). |
There was a problem hiding this comment.
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.
src/rustdoc/membership.md
Outdated
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. |
There was a problem hiding this comment.
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.
- 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). |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
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, |
There was a problem hiding this comment.
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).
🔔 This is now entering its final comment period, as per the review above. 🔔 psst @GuillaumeGomez, I wasn't able to add the |
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. |
This is already covered. See
which delegates to
(see linked documents for more details) |
cc @rust-lang/rustdoc
Rendered