Skip to content
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

lang-docs team adoptions charter follow-up #1650

Open
4 tasks
jamesmunns opened this issue Jan 31, 2025 · 4 comments
Open
4 tasks

lang-docs team adoptions charter follow-up #1650

jamesmunns opened this issue Jan 31, 2025 · 4 comments

Comments

@jamesmunns
Copy link
Member

@jackh726 raised a concern that was missed in the lang-docs team adopting rustlings, rust-by-example, and the book team:

So, I think moving these groups under lang-docs is good idea in terms of organization. But, what I personally would really like to see before this happens is some kind of "charter" from lang-docs on what what is expected from subteams in terms of autonomy and such. It may seem "obvious", but especially given @chris Krycho's comment re. the book team, I think it would be really good to formalize this.

I would like to follow up with this, which would mean:

I agree it is good to document:

  • What the sub-teams are expected to do
  • What responsibility is delegated to the sub-teams (particularly the expected level of autonomy).

Niko provided a potentially useful example of a charter from the proposed project-goals team: https://rust-lang.github.io/rust-project-goals/admin/team.html

@jamesmunns
Copy link
Member Author

For reference, any of the members of the relevant teams are welcome to propose a charter, but I would expect review from the team leads and parent team leads. For the three adopted teams, this would need an r+ from the lang-docs leads as well as the adopted team leads. For the revisions to the lang-docs charter, that would mean an r+ from the lang-docs lead as well as the t-lang leads (CC @nikomatsakis @tmandry).

Leaving this as a note, mainly for @rust-lang/team-repo-admins when they review the follow-on PRs adding charter content here.

@jamesmunns
Copy link
Member Author

Whoops, I was under the impression that charters (or a link to them?) were encoded in the teams metadata, which is why I opened this issue here.

They definitely aren't, so I need to re-home this issue. I'll find a suitable place for it, as I'd like to make sure it doesn't get lost! Sorry for the noise for the teams repo admins :)

@tmandry
Copy link
Member

tmandry commented Feb 1, 2025

A link to them probably should be. I would like it if there was a central place to view team charters even, but I'm not sure where it would go (possibly forge?)

@jamesmunns
Copy link
Member Author

It would be cool to either inline them in https://www.rust-lang.org/governance (generated from this repo), or at least show a link button.

I've opened #1651 to track that, so we don't get off topic here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants