Better define the scope of rustdoc members roles #993
Conversation
rustbot
added
the
S-waiting-on-review
|
rustbot has assigned @aDotInTheVoid. Use |
src/rustdoc/membership.md
Outdated
|
|
||
| - 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. |
There was a problem hiding this comment.
Do you see anything that needs clarification?
There was a problem hiding this comment.
Obvious question is that you haven't mentioned search in any of these. I think it's considered front-end, since it's HTML-specific, but we should probably say so.
There was a problem hiding this comment.
Specifying the scope of each team a bit more precisely then.
|
I mean, looks sensible, but I'm not sure how is it related to t-infra? 😅 |
|
For the add of new roles/tags. Also I'm not sure if it works for RFCs yet. |
| [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 |
There was a problem hiding this comment.
Doesn't this require making a rustdoc-json-backend team (which is probably worthwhile doing anyway)?
There was a problem hiding this comment.
Yep, hence why I pinged the infra team. ;)
There was a problem hiding this comment.
(Just send a PR to team and that should be it :) )
7 participants
Since the experiment with the @rust-lang/rustdoc-frontend was a success, I think we can now add the two other roles:
rustdoc-json-backendandrustdoc-internals. That will require for the infra team to also give their opinion here (cc @Kobzol).cc @rust-lang/rustdoc
Rendered