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.

Sign up for GitHub

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

Jump to bottom

Establish team charters #44

Open
ehuss opened this issue Aug 8, 2023 · 1 comment
Open

Establish team charters #44

ehuss opened this issue Aug 8, 2023 · 1 comment
Labels
A-project-structure Area: Structure of the Rust Project I-council-nominated This issue nominated for discussion in a meeting. S-active Status: Someone or some group is actively working on this.

Comments

@ehuss
Copy link
Contributor

ehuss commented Aug 8, 2023 •
edited
Loading

The core team previously started a process to establish charters for all teams. However, it wasn't finished. I would like to see a central place (my preference is the Forge) which contains basic charters for all of the teams which would answer the following:

  • The team's mission and responsibilities
  • Requirements for team membership, and the process to get involved
  • Contact information so that someone can find where the team does its work (GitHub repos, Zulip streams, etc.)

As an extension to this, I think it would be good to have suggestions on having teams document their processes. My preference would be for teams to decide where and how that is documented, but having some starting templates could be helpful for standing up teams and making it clear what people's expectations should be.

A consideration is what gets chartered (teams, working groups, etc.).

There's tons of background here, but I will just drop a few links for now:

(There's stuff I'm missing...)

I would like to keep this issue focused on documenting existing team missions, and not to grow to more general considerations about what Rust's governance structure should look like (#33), definitions of different structures (teams, sub-teams, working-groups, project-groups), etc.
@ehuss ehuss added the S-needs-council Status: Needs a council representative to adopt this label Aug 8, 2023
ehuss added a commit to ehuss/rust-forge that referenced this issue Aug 9, 2023
@ehuss
Remove outdated RFC 1068 governance docs.
fa12dfc 
These docs are very outdated and contains some misleading information.
There are important things to resurrect at some point, which is
something the Council should take on:

* Definition of teams, and the structure of the Project in general:
  rust-lang/leadership-council#33
* Team charters, defining what each team's mission and responsibilities
  are: rust-lang/leadership-council#44
* Suggestions on moderation team processes should follow up with either
  the Council or https://github.com/rust-lang/moderation-team
* Suggested decision making processes for teams:
  rust-lang/leadership-council#45
  (and rust-lang/leadership-council#23 to some
  degree).
ehuss added a commit to ehuss/rust-forge that referenced this issue Aug 9, 2023
@ehuss
Remove team repository list.
5b9c5b6 
This will generally not be kept up-to-date, and this information
can be found elsewhere like the GitHub repo listing or the
https://www.rust-lang.org/governance pages. As part of
rust-lang/leadership-council#44
I'd also like to better surface this kind of information on the Forge.
ehuss added a commit to ehuss/rust-forge that referenced this issue Aug 21, 2023
@ehuss
Remove outdated RFC 1068 governance docs.
9634f6b 
These docs are very outdated and contains some misleading information.
There are important things to resurrect at some point, which is
something the Council should take on:

* Definition of teams, and the structure of the Project in general:
  rust-lang/leadership-council#33
* Team charters, defining what each team's mission and responsibilities
  are: rust-lang/leadership-council#44
* Suggestions on moderation team processes should follow up with either
  the Council or https://github.com/rust-lang/moderation-team
* Suggested decision making processes for teams:
  rust-lang/leadership-council#45
  (and rust-lang/leadership-council#23 to some
  degree).
ehuss added a commit to ehuss/rust-forge that referenced this issue Aug 21, 2023
@ehuss
Remove team repository list.
ead5920 
This will generally not be kept up-to-date, and this information
can be found elsewhere like the GitHub repo listing or the
https://www.rust-lang.org/governance pages. As part of
rust-lang/leadership-council#44
I'd also like to better surface this kind of information on the Forge.
@ehuss ehuss added S-active Status: Someone or some group is actively working on this. A-project-structure Area: Structure of the Rust Project and removed S-needs-council Status: Needs a council representative to adopt this labels Nov 20, 2023
@traviscross traviscross added the I-council-nominated This issue nominated for discussion in a meeting. label Nov 8, 2024
@traviscross
Copy link
Contributor

I nominate to briefly review this as we have it marked as active, and to propose that we unmark it as active if it is not.

This should take five minutes.

@ehuss ehuss mentioned this issue Nov 22, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-project-structure Area: Structure of the Rust Project I-council-nominated This issue nominated for discussion in a meeting. S-active Status: Someone or some group is actively working on this.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ehuss @traviscross