Merge pull request #698 from ehuss/governance

Update governance documentation

Author: rylev

book.toml

@@ -44,9 +44,11 @@ curly-quotes = true
 "compiler/diagnostic-codes.html" = "https://rustc-dev-guide.rust-lang.org/diagnostics/diagnostic-codes.html"
 "compiler/profile-queries.html" = "https://rustc-dev-guide.rust-lang.org/queries/profiling.html"
 "chat/index.html" = "/platforms/index.html"
-"chat/discord.html" = "platforms/discord.html"
-"github.html" = "platforms/github.html"
-"chat/email.html" = "platforms/email.html"
-"chat/zulip/index.html" = "platforms/zulip/index.html"
-"chat/zulip.html" = "platforms/zulip.html"
+"chat/discord.html" = "/platforms/discord.html"
+"github.html" = "/platforms/github.html"
+"chat/email.html" = "/platforms/email.html"
+"chat/zulip/index.html" = "/platforms/zulip/index.html"
+"chat/zulip.html" = "/platforms/zulip.html"
 "platforms/zulip/triagebot.html" = "/triagebot/index.html"
+"core/blogs.html" = "/platforms/blogs.html"
+"core/index.html" = "/governance/council.html"

src/SUMMARY.md

@@ -8,6 +8,7 @@
   - [GitHub](./platforms/github.md)
   - [Zulip](./platforms/zulip.md)
       - [Moderation](./platforms/zulip/moderation.md)
+  - [Blogs](./platforms/blogs.md)
 - [Triagebot](./triagebot/README.md)
     - [Agenda Generator](./triagebot/agenda.md)
     - [Issue Assignment](./triagebot/issue-assignment.md)
@@ -32,8 +33,6 @@
     - [Triagebot Dashboard](./triagebot/triage-dashboard.md)
     - [Zulip Meeting Management](./triagebot/zulip-meeting.md)
     - [Zulip Notifications](./triagebot/zulip-notifications.md)
-- [Core](./core/README.md)
-    - [Rust Blog Guidelines](./core/blogs.md)
 - [Community](./community/README.md)
     - [State of Rust Survey FAQ](./community/survey-faq.md)
 - [Compiler](./compiler/README.md)
@@ -61,6 +60,8 @@
   - [Self-hosting a docs.rs instance](./docs-rs/self-hosting.md)
   - [Maintenance procedures](./docs-rs/maintenance.md)
 - [Governance](./governance/README.md)
+    - [Leadership Council](./governance/council.md)
+    - [Moderation](./governance/moderation.md)
 - [Infrastructure](./infra/README.md)
     - [Other Installation Methods](./infra/other-installation-methods.md)
     - [Release Channel Layout](./infra/channel-layout.md)

src/community/survey-faq.md

@@ -27,7 +27,7 @@ The answers from the survey will be anonymized, aggregated, and summarized. A hi
 
 ### How is personally identifiable information handled?
 
-Nearly every question in the survey is optional. You are welcome to share as much or as little information as you are comfortable with. Only the Rust language Core Team and the Community Team Survey Leads will have access to the raw data from the survey. All the answers are anonymized prior to be shared with the rest of the teams and prior to the results publication.
+Nearly every question in the survey is optional. You are welcome to share as much or as little information as you are comfortable with. Only the Community Team Survey Leads will have access to the raw data from the survey. All the answers are anonymized prior to be shared with the rest of the teams and prior to the results publication.
 
 ### Why is the survey collecting contact information?
 
@@ -39,7 +39,7 @@ The survey optionally collects contact information for the following cases if yo
 - Rust training
 - interest in a Rust team contacting you about your survey responses
 
-If you would like to be contacted about any of this, or any other concerns, but you don't want to associate your email with your survey responses, you can instead email the Rust Community Team at community-team@rust-lang.org or the Core Team at core-team@rust-lang.org, and we will connect you to the right people.
+If you would like to be contacted about any of this, or any other concerns, but you don't want to associate your email with your survey responses, you can instead email the Rust Community Team at community-team@rust-lang.org, and we will connect you to the right people.
 
 ## Where and when is the survey results report published?
 

src/core/README.md

@@ -4,8 +4,8 @@ If we get a DMCA takedown notice, here's what needs to happen:
 
 ## Contact Legal
 
-Before removing the crates, get in touch with legal support, currently by
-emailing the Core team, and ask an opinion from them on the received request and
+Before removing the crates, get in touch with legal support,
+and ask an opinion from them on the received request and
 whether we have to comply with it.
 
 ## Remove relevant version(s) and/or entire crates from crates.io