Extend the reference team to the lang-docs team - #445
Conversation
|
Note that deploying this will need someone with admin permissions to first rename the team on the GitHub interface, otherwise we'll lose all permissions configured in the repositories: |
|
@pietroalbini If my understanding is correct, the current "reference" team doesn't use |
|
But yeah, we could archive the reference team then create a fresh team if it's desirable. |
|
@JohnTitor I think the best solution is for someone to rename the old team to the new one before merging this PR, and then merge this as-is once someone from the lang team approves the changes. |
You mean the team is on GitHub? We don't have the reference team on the GitHub teams AFAIK. |
|
Sorry, you're right :) Then this PR is fine to merge as soon as someone from lang acks. |
|
On #443, Josh and Taylor from the lang added 👍 so we could say this got some approvals? The core team (i.e. org owner) only can merge this and set up for repository permission so could I ask @nikomatsakis as a core and lead of the lang to do that? |
|
Looks great! |
| [website] | ||
| name = "lang-docs team" | ||
| description = "Developing and writing the docs related to the lang team" | ||
| zulip-stream = "t-lang/docs" |
There was a problem hiding this comment.
This link is broken. The zulip stream is t-lang/doc.
There was a problem hiding this comment.
Oops, thanks. Will fix it soon.
EDIT: Opened #454.
As mentioned in #443, this extends the reference team to the lang-docs team.
This is the first step, we could add folks interested in maintaining the docs later.
Added myself to the leads as a maintainer of the nomicon.
Closes #443
cc @rust-lang/lang, and @ehuss as they maintain the docs submodules on rust-lang/rust.