Skip to content

lang-docs team adoptions charter follow-up #1650

@jamesmunns

Description

@jamesmunns

@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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions