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.
Accomplishments so far
Content team
Pete LeVasseur and TC created the Content team (leadership-council#206). The team is charged with producing publishable content that is of interest and benefit to the Rust Project and its community including blog posts, videos, podcasts, etc. The team is talking with people in the Project and the community to share their knowledge and experience, and most immediately, the team has been organizing interviews that will be recorded at RustConf.
We are looking forward to soon seeing what they produce.
All-hands 2026
The Council approved the 2026 All-Hands event (leadership-council#192). This event is an opportunity for Project members to meet in person to to collaborate on the future of Rust. The event is scheduled to occur again with RustWeek 2026 in The Netherlands on May 21-23. More information will be coming soon.
Additional items
And a few other items:
- Coordinated with the mods team on the creation of the venue mods team, which is responsible for moderating venues such as GitHub and Zulip. team#1874
- Approved the renewal of the compiler ops contract. leadership-council#181
- Approved substitutes for the July and August Foundation board meetings. leadership-council#187 leadership-council#194 leadership-council#201
- Coordinated with the RustConf organizers on how to distribute free or reduced-price tickets for Project members. leadership-council#190
- Added @jieyouxu to the team-repo-admins, who are responsible for updating the Rust team memberships and resources. leadership-council#205
- Coordinated with the infra team to set up the email alias for
contact@rust-lang.orgas the contact address of the rust-lang GitHub organization. leadership-council#202 - Coordinated with the social media team to approve the creation of an official LinkedIn page for Rust, now up at https://www.linkedin.com/company/rust-lang/. leadership-council#208
- Approved a travel grant for @tomassedovic to go to Kangrejos 2025, the Rust for Linux Workshop. leadership-council#217
Ongoing work
There are various efforts underway on projects that have had significant discussions since the last update, but have not concluded with any decisions, yet. They are:
Rust Society
@JamesMunns has continued to develop the concept of the "Rust Society". The Rust Society will be an organizational structure for user groups (commonly called "Special Interest Groups", "Working Groups", etc. in other organizations) outside of the Rust Project, but administrated by the Rust Project via a new "T-Society-Admins" subteam of the Launching Pad.
This structure is intended to be the long-term home for existing Domain Working Groups, which will be retired as a concept after this work is complete. In the future, this structure intends to offer "open enrollment" for any interested group of users.
See the latest proposed charter for how the Rust Society will function.
Foundation
There have been continual discussions with the Foundation on various topics. We are excited to welcome Lori Lorusso, who has started as the Foundation's new Director of Outreach. She hit the ground running and has been helping to coordinate with the Foundation and plan upcoming projects.
We have been discussing with the Foundation the possibilities for continuing the budget for project priorities in 2026. For 2024 and 2025, this budget was made possible by a generous unrestricted grant from Microsoft. We are looking for ways that we can continue this budget so as to continue important programs such as travel grants, the all-hands, project grants, program management, and compiler operations.
We discussed the condition of the 2025 travel grant budget (leadership-council#182). Many Project members used most of their $2,000 limit during the all-hands earlier this year, and we had concerns that members would not be able to attend other events like RustConf. Ultimately we decided to keep with the current policy and will be working on figuring out what our possible option might be for funding this in 2026.
Finally, on the top of our minds is the Foundation three-year strategy. We have a keen interest in working with the Foundation staff to ensure that we are all focused together on the best objectives. We hope to share more on this soon.
Additional items
- We have been discussing a policy for better management of the alumni status of Project members. leadership-council#218 leadership-council#175
- We had some discussions on who is responsible for how stable and unstable features relate to the stable releases. leadership-council#180
- The September 2025 council elections have started. leadership-council#211
- The 2025 Foundation director elections have started. @tomassedovic will be facilitating this year. https://blog.rust-lang.org/inside-rust/2025/08/20/electing-new-project-directors-2025/
- We launched the 2025 Leadership Council Survey, and will be posting the results soon.
Following our work
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. The items on our meeting agendas are drawn from these. After discussing an item, we summarize that discussion and any shared rationales 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.
To follow our work in real time, watch our repository.
Meeting minutes
We publish minutes from all Council meetings to the Leadership Council repo. Links to the minutes since our last update are: