|
| 1 | ++++ |
| 2 | +path = "inside-rust/2025/12/09/leadership-council-update" |
| 3 | +title = "Leadership Council update — December 2025" |
| 4 | +authors = ["Eric Huss"] |
| 5 | + |
| 6 | +[extra] |
| 7 | +team = "Leadership Council" |
| 8 | +team_url = "https://www.rust-lang.org/governance/teams/leadership-council" |
| 9 | ++++ |
| 10 | + |
| 11 | +Hello again from the Rust Leadership Council! We wanted to share an update on what the Council has been working on since [our last update][update]. |
| 12 | + |
| 13 | +[update]: https://blog.rust-lang.org/inside-rust/2025/09/10/leadership-council-update/ |
| 14 | + |
| 15 | +## Accomplishments so far |
| 16 | + |
| 17 | +### Welcome Jakub Beránek to the Council |
| 18 | + |
| 19 | +As [announced in September](https://blog.rust-lang.org/inside-rust/2025/09/23/leadership-council-repr-selection/), [Jakub Beránek] joined the Council representing the Infrastructure team. |
| 20 | + |
| 21 | +[Jakub Beránek]: https://github.com/Kobzol |
| 22 | + |
| 23 | +### Foundation updates |
| 24 | + |
| 25 | +In October we wrapped up the election process for the Project Directors of the Rust Foundation. [Jack Huey], [Niko Matsakis], and [David Wood] are our new Directors ([see announcement][pd-election]). We'd like to thank [Tomas Sedovic] for facilitating the election process. |
| 26 | + |
| 27 | +[pd-election]: https://rustfoundation.org/media/introducing-the-rust-foundations-newest-project-directors-october-2025/ |
| 28 | +[Jack Huey]: https://github.com/jackh726/ |
| 29 | +[Niko Matsakis]: https://github.com/nikomatsakis/ |
| 30 | +[David Wood]: https://github.com/davidtwco/ |
| 31 | +[Tomas Sedovic]: https://github.com/tomassedovic |
| 32 | + |
| 33 | +We've been discussing the 2026 "Project Priorities" budget with the Foundation, which would continue the program funded by Microsoft in 2024 and 2025. We're happy to report that we will be able to continue this program, which funds initiatives such as our travel budget, program management, compiler operations, and other maintenance support for the Rust project. The final budget will be submitted for board approval at the next meeting in December. We'll have more to share about this in the future. [#183](https://github.com/rust-lang/leadership-council/issues/183) [#234](https://github.com/rust-lang/leadership-council/issues/234) |
| 34 | + |
| 35 | +We have engaged in extensive discussions regarding the Foundation's 3-year strategy, which is also scheduled for approval at the December board meeting. [#197](https://github.com/rust-lang/leadership-council/issues/197) |
| 36 | + |
| 37 | +After monitoring travel budget spending and addressing concerns regarding 2025 expenditure levels, we have decided to maintain our current policy for the time being. [#182](https://github.com/rust-lang/leadership-council/issues/182) |
| 38 | + |
| 39 | +We coordinated with the Foundation on the [announcement of the Rust Innovation Lab](https://blog.rust-lang.org/2025/09/03/welcoming-the-rust-innovation-lab/), and are excited to see this initiative move forward. |
| 40 | + |
| 41 | +### Shape of Rust |
| 42 | + |
| 43 | +We have implemented changes to the team structure to further clarify the status of teams in the Launching Pad. In particular: |
| 44 | + |
| 45 | +- The Async Working Group has moved under the lang team. [#137](https://github.com/rust-lang/leadership-council/issues/137) |
| 46 | +- The Community Content team has been archived. [#129](https://github.com/rust-lang/leadership-council/issues/129) |
| 47 | + |
| 48 | +Progress has been made with other Launching Pad teams, though these efforts have not yet concluded. In particular, we have looked at the Secure Code Working Group [#140](https://github.com/rust-lang/leadership-council/issues/140), Embedded Working Group [#127](https://github.com/rust-lang/leadership-council/issues/127), CLI Working Group [#138](https://github.com/rust-lang/leadership-council/issues/138), and Gamedev Working Group [#126](https://github.com/rust-lang/leadership-council/issues/126). While undecided, these teams may eventually join the proposed Rust Society or become cross-cutting teams within an updated Launching Pad. |
| 49 | + |
| 50 | +[James Munns] submitted [a proposal](https://github.com/rust-lang/leadership-council/issues/159#issuecomment-3237633417) detailing the vision and operational structure of the Rust Society. |
| 51 | + |
| 52 | +[James Munns]: https://github.com/jamesmunns |
| 53 | + |
| 54 | +### Additional items |
| 55 | + |
| 56 | +Other updates include: |
| 57 | + |
| 58 | +- We concluded a contributor survey primarily focused on understanding the balance between funded and volunteer-based contributions within the Rust Project. The results will help inform how we can better support maintainers. [#222](https://github.com/rust-lang/leadership-council/issues/222) |
| 59 | +- We approved a requirement for all Project members to have a Zulip account (in addition to a GitHub account) to ensure more reliable communication. [#228](https://github.com/rust-lang/leadership-council/issues/228) |
| 60 | +- We agreed to extend an invitation to the Rust for Linux contributors for the 2026 All-Hands. [#236](https://github.com/rust-lang/leadership-council/issues/236) |
| 61 | +- In response to a query regarding responsibility for stable versus unstable support in stable releases, we clarified that this generally falls under the Lang team's purview, with the Compiler team primarily responsible for implementation. [#180](https://github.com/rust-lang/leadership-council/issues/180) |
| 62 | +- We agreed to delegate decisions regarding GSoC mentor rewards to the Mentorship team. [#232](https://github.com/rust-lang/leadership-council/issues/232) |
| 63 | +- We considered a request to establish a Project Representative position but decided against it for the time being. [#226](https://github.com/rust-lang/leadership-council/issues/226) |
| 64 | + |
| 65 | +## Ongoing work |
| 66 | + |
| 67 | +Several projects have seen significant discussion since our last update but have not yet reached a conclusion. |
| 68 | + |
| 69 | +### Foundation |
| 70 | + |
| 71 | +We are excited about the development of the [Rust Foundation Maintainers Fund](https://rustfoundation.org/media/announcing-the-rust-foundation-maintainers-fund/). We are working closely with the Foundation to guide how this program will fund Rust Project maintainers. A working group is forming to define the usage of these funds ([#248](https://github.com/rust-lang/leadership-council/pull/248)). We expect to have an approved plan and policy in place in January 2026. [#242](https://github.com/rust-lang/leadership-council/issues/242) |
| 72 | + |
| 73 | +David Wood has proposed a clarification of Project Director responsibilities, which we hope will improve understanding and communication between the Council, the Directors, and the Foundation. [#250](https://github.com/rust-lang/leadership-council/pull/250) |
| 74 | + |
| 75 | +### Additional items |
| 76 | + |
| 77 | +- We are following up on a request to add Graydon Hoare to the alumni section of the website. |
| 78 | +[#231](https://github.com/rust-lang/leadership-council/issues/231) |
| 79 | +- Regarding a request to link the community Discord from our website, we have deferred the decision to the website management team. [#219](https://github.com/rust-lang/leadership-council/issues/219) |
| 80 | +- We received invitations to apply for funding from the Rust Ecosystem Fund. [#240](https://github.com/rust-lang/leadership-council/issues/240) |
| 81 | + |
| 82 | +## Following our work |
| 83 | + |
| 84 | +As you can see from the many links above, the work of the Council happens mostly in public on GitHub issues posted in [our repository](https://github.com/rust-lang/leadership-council/issues). The items on our meeting agendas are drawn from these. After discussing an item, we summarize that discussion and any shared [rationales](https://aturon.github.io/tech/2018/05/25/listening-part-1/) on the issue. When we make decisions, we propose on the issue a "final comment period" (FCP), and as with all FCPs in the Project, we're interested in and review any feedback that people have before or during this final comment period. |
| 85 | + |
| 86 | +To follow our work in real time, watch our repository. |
| 87 | + |
| 88 | +## Meeting minutes |
| 89 | + |
| 90 | +We publish minutes from all Council meetings to the [Leadership Council repo][minutes]. Links to the minutes since our last update are: |
| 91 | + |
| 92 | +* [August 29, 2025](https://github.com/rust-lang/leadership-council/blob/main/minutes/sync-meeting/2025-08-29.md) |
| 93 | +* [September 12, 2025](https://github.com/rust-lang/leadership-council/blob/main/minutes/sync-meeting/2025-09-12.md) |
| 94 | +* [September 26, 2025](https://github.com/rust-lang/leadership-council/blob/main/minutes/sync-meeting/2025-09-26.md) |
| 95 | +* [October 10, 2025](https://github.com/rust-lang/leadership-council/blob/main/minutes/sync-meeting/2025-10-10.md) |
| 96 | +* [October 24, 2025](https://github.com/rust-lang/leadership-council/blob/main/minutes/sync-meeting/2025-10-24.md) |
| 97 | +* [November 7, 2025](https://github.com/rust-lang/leadership-council/blob/main/minutes/sync-meeting/2025-11-07.md) |
| 98 | +* [November 14, 2025](https://github.com/rust-lang/leadership-council/blob/main/minutes/sync-meeting/2025-11-14.md) |
| 99 | +* [November 21, 2025](https://github.com/rust-lang/leadership-council/blob/main/minutes/sync-meeting/2025-11-21.md) |
| 100 | + |
| 101 | +[minutes]: https://github.com/rust-lang/leadership-council/tree/main/minutes |
0 commit comments