Merge pull request #1039 from rylev/governance-update-2022-10-06

Add the governance update email from 2022-09-30

posts/inside-rust/2022-10-06-governance-update.md

@@ -0,0 +1,23 @@
+---
+layout: post
+title: "Governance Update"
+author: Ryan Levick
+team: leadership chat <https://www.rust-lang.org/governance>
+---
+
+As part of ongoing work on governance, Rust leadership jointly established a group, "leadership chat", consisting of the Core team, leads of all teams on the [governance page], the Moderation team, and the project directors on the Rust Foundation board. This group has been serving as an interim governing body while efforts to establish the next evolution of Rust project-wide governance are underway.
+
+We previously posted [an update on the future of Rust project-wide governance][update]. In that post, we promised that the next steps would be to "take the findings we have so far and begin crafting proposals for how the Rust project will be governed in the future." In this post, we'd like to provide an update on the status of this work.
+
+Late in July, the interim leadership team established an informal working group to conduct further research and draft an RFC for the establishment of a new project-wide governing body. This RFC relies on the requirements document[^1] that was compiled as a result of in-depth interviews conducted by Ryan Levick and Mara Bos with team members from across the Rust project. Currently, there are seven people involved in this working group: Ryan Levick (Core Project Director), JT (Core), Mark Rousskov (Core Project Director, Release Lead), Jane Losare-Lusby (Collaboration Project Director), Josh Triplett (Lang Team Lead), Josh Gould (Moderation), and Khionu Sybiern (Moderation).
+
+The working group's objective is not to completely re-engineer every aspect of Rust's governance model — that would require the participation and consent of all the other teams working in the project — but rather to lay the foundation for dynamic project-wide governance by introducing policies and procedures for constraining, monitoring, and adjusting the governance model in response to the project's evolving needs. As part of this work, not only is explicit attention being paid to the issues that led to the resignation of the [former mod team] last November but also additional governance shortfalls identified through Ryan's and Mara's research. At the same time, we're deliberately keeping the scope small in the hope of getting out of the way as soon as possible to let the work continue under the new more representative and accountable governance body.
+
+According to our current projections, we are roughly halfway through drafting this RFC since the process began at the end of August. We're still making steady progress, and when we have a full draft, we'll post it for project-wide review. In the interest of transparency, we will continue to publish updates until the RFC is made available. The goal of keeping the initial discussions private is not to exclude people, but rather to keep the size of the group discussions manageable[^2] during the early stages of the RFC drafting process. We are completely open to sharing early drafts and discussing current plans outside of our weekly meetings. Any project participants with questions or concerns are encouraged to get in touch with the working group's members.
+
+[^1]: Which can be found in the [previous governance update post][update]
+[^2]: Even with "only" seven people, having discussions of this magnitude is difficult.
+
+[governance page]: https://www.rust-lang.org/governance
+[update]: https://blog.rust-lang.org/inside-rust/2022/05/19/governance-update.html
+[former mod team]: https://blog.rust-lang.org/inside-rust/2021/11/25/in-response-to-the-moderation-team-resignation.html