Update governance documentation #698
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rylev
approved these changes
Aug 10, 2023
hdost
reviewed
Aug 11, 2023
The redirects are relative to the current page, so they need `/` to anchor to the root of the site.
In preparation to remove the core chapter.
Followup will rework some of the text to remove the RFC aspects of it.
This content is moved as-is without modification. The intent is to help organize and manage the chapter size.
This removes the RFC wording from the council policy to make it stand on its own, and not be framed as a proposal.
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).
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.
This updates documentation to point to the leadership council.
I'm not entirely certain what the RFC authors' intent was with this style, but my guess was that it was because it was proposing a new term. Since the team is now a real team, and this document is no longer being framed as a proposal, this removes it and uses a consistent style.
|
@rylev Just checking if there is anything else you'd like to see before merging this or if it is waiting on anything? |
|
@ehuss nope - I was expecting you to merge it, but I can if you want me to. |
|
I think you are the only one with permission to merge things here (and Mark, but I'm not really clear who else has access). |
rylev
approved these changes
Aug 25, 2023
|
We should discuss giving merge permissions at least to the librarians committee of the Council. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This updates the governance documentation to reflect the changes as a result of RFC 3392. This also replaces mentions of the core team with the leadership council. There are several commits which should explain each change. The intent here is for the official governance documentation lives here as a permanent home.
Closes #694
Closes rust-lang/leadership-council#14