|
| 1 | ++++ |
| 2 | +path = "inside-rust/2025/06/11/leadership-council-update" |
| 3 | +title = "June 2025 Leadership Council Update" |
| 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! |
| 12 | +We wanted to share an update on what the Council has been working on since [our last update][update]. |
| 13 | + |
| 14 | +[update]: https://blog.rust-lang.org/inside-rust/2025/03/17/leadership-council-update/ |
| 15 | + |
| 16 | +## Accomplishments so far |
| 17 | + |
| 18 | +### Welcome Josh Stone to the Council |
| 19 | + |
| 20 | +As [announced in March](https://blog.rust-lang.org/inside-rust/2025/03/26/leadership-council-repr-selection/), Josh Stone joined the Council representing the compiler team. |
| 21 | + |
| 22 | +### Program manager |
| 23 | + |
| 24 | +We've seen a lot of returns from good Project-directed program management. In support of this valuable work — so that we can do more with it while making it more sustainable — we allocated funds to the Edition and Goals teams to hire a program manager. TC and Joel interviewed a large number of candidates, and we're excited to announce that the Project, with logistical support from the Foundation, has brought on [Tomas Sedovic]. He's hit the ground running, joining many team calls in the past week, and supporting the teams with record keeping and communication — which is good for the transparency and effective functioning of our work — and with logistics such as the coordination of meetings and follow-up with contributors. Going forward, we're expecting this work to help us and our teams across the Project better manage the many ongoing initiatives that are of importance to us. |
| 25 | + |
| 26 | +[Tomas Sedovic]: https://github.com/tomassedovic |
| 27 | + |
| 28 | +### All-hands |
| 29 | + |
| 30 | +More than 150 people attended the all-hands event in May at [RustWeek 2025] in the Netherlands. We've received a lot of positive feedback about the event, as it was a great opportunity to get people from across the org to have focused discussions. |
| 31 | + |
| 32 | +The project was able to sponsor this event with $100,000 in funding for the event, with an additional $117,000 for travel and tickets. We are looking to see if we can secure funding to be able to continue these events in the future. |
| 33 | + |
| 34 | +Many thanks to [Mara Bos] who was instrumental in organizing this event and making it a success. |
| 35 | + |
| 36 | +[RustWeek 2025]: https://rustweek.org/ |
| 37 | +[Mara Bos]: https://github.com/m-ou-se/ |
| 38 | + |
| 39 | +### Additional items |
| 40 | + |
| 41 | +And a few other items: |
| 42 | +- [Josh Stone] has volunteered to be on the RustConf Program Committee to help select talks for [RustConf 2025](https://rustconf.com/). [leadership-council#163](https://github.com/rust-lang/leadership-council/issues/163) |
| 43 | +- [TC] has volunteered to be a substitute for the June Foundation board meeting. [leadership-council#176](https://github.com/rust-lang/leadership-council/issues/176) |
| 44 | +- Approved creating the Vision Doc team, which is working to create a document that identifies key opportunities for Rust over the next 3-5 years. [leadership-council#165](https://github.com/rust-lang/leadership-council/issues/165) |
| 45 | +- Approved placing the Rust logo in the RISC-V landscape page. [leadership-council#164](https://github.com/rust-lang/leadership-council/issues/164) |
| 46 | +- Approved a clarification of the definition of "expatriated crates" as part of our crate publishing policy. [rust-forge#840](https://github.com/rust-lang/rust-forge/pull/840) |
| 47 | +- The social media team set up a [Bluesky account](https://bsky.app/profile/rust-lang.org) for posting official announcements. The Rust Project also has an official [Mastodon account](https://social.rust-lang.org/@rust) as well. |
| 48 | +- Added the Foundation directors as a "team" in the team database. [team#1786](https://github.com/rust-lang/team/pull/1786) |
| 49 | +- Approved the infra team to set it up so that team leads can directly approve modifications to their team files. [leadership-council#171](https://github.com/rust-lang/leadership-council/issues/171) |
| 50 | +- Added some clarification on the approval process for posting on the official Rust blog. [leadership-council#173](https://github.com/rust-lang/leadership-council/issues/173). |
| 51 | +- Added some basic onboarding documentation for the project as a whole. [rust-forge#846](https://github.com/rust-lang/rust-forge/pull/846) |
| 52 | +- Clarified that the council does not need to be involved with transferring the Docker team out of the launching pad and into the infra team. [leadership-council#124](https://github.com/rust-lang/leadership-council/issues/124) |
| 53 | + |
| 54 | +[Josh Stone]: https://github.com/cuviper |
| 55 | +[TC]: https://github.com/traviscross |
| 56 | + |
| 57 | +## Ongoing work |
| 58 | + |
| 59 | +There are various efforts underway on projects that have had significant discussions since the last update, but have not concluded with any decisions, yet. |
| 60 | +They are: |
| 61 | + |
| 62 | +### Shape of Rust |
| 63 | + |
| 64 | +[James Munns] has continued to develop his ideas for a "Rust Society" to find a home for certain kinds of community groups and special interest groups. We've received great feedback during the all-hands to help further refine these ideas, and James is continuing to work on how this might be structured. [leadership-council#159](https://github.com/rust-lang/leadership-council/issues/159) |
| 65 | + |
| 66 | +One idea for how this might shape up is to re-charter the launching pad to be something more permanent for cross-cutting, long-lived teams (like the [Security Response Working Group](https://github.com/rust-lang/leadership-council/issues/141)). [leadership-council#170](https://github.com/rust-lang/leadership-council/issues/170) |
| 67 | + |
| 68 | +[James Munns]: https://github.com/jamesmunns |
| 69 | + |
| 70 | +### Foundation budget |
| 71 | + |
| 72 | +As part of [Microsoft's donation], the Council has had $650k available to spend at its discretion. There are three recent budget items that the Council has been considering: |
| 73 | + |
| 74 | +- Renewing the Compiler Ops contract for another six months. In the past six months we have spent about $20k out of the initial $30k that we reserved for this position. [leadership-council#181](https://github.com/rust-lang/leadership-council/issues/181) |
| 75 | +- Planning for spending of the [travel budget]. We reserved $75k per year for travel expenses and event tickets. In 2024 we only spent about $16k, but due to the larger all-hands event this year we have spent $117k in the first half of the year. Combining those means there is only about $17k left for the remainder of the year. We'll need to decide if we want to stick to our budgeted cap, or if we want to consider extending it. Additionally we are considering whether or not we want to reserve what remains for 2026. [leadership-council#182](https://github.com/rust-lang/leadership-council/issues/182) |
| 76 | +- Planning for 2026. At present the Council only has about $67k left unreserved. We could consider holding that for the travel budget next year, or to fund other things. We'll be having some discussions with the Foundation about other funding possibilities. |
| 77 | + |
| 78 | +[Microsoft's donation]: https://rustfoundation.org/media/1m-microsoft-donation-to-fund-key-rust-foundation-project-priorities/ |
| 79 | +[travel budget]: https://github.com/rust-lang/leadership-council/blob/main/policies/spending/travel.md |
| 80 | + |
| 81 | +### Additional items |
| 82 | + |
| 83 | +- We have continued to have discussions on how to have better communication between the Council, Foundation directors, and the Foundation staff. |
| 84 | +- A question came to the Council about the possibility of having explicit team membership durations. This came out of some discussions about how to address burnout, and would have other benefits such as having clearer team structures. [leadership-council#175](https://github.com/rust-lang/leadership-council/issues/175) |
| 85 | + |
| 86 | +## Meeting minutes |
| 87 | + |
| 88 | +We publish minutes from all Council meetings to the [Leadership Council repo][minutes]. |
| 89 | +Links to the minutes since our last update are: |
| 90 | + |
| 91 | +* [March 14, 2025](https://github.com/rust-lang/leadership-council/blob/main/minutes/sync-meeting/2025-03-14.md) |
| 92 | +* [March 28, 2025](https://github.com/rust-lang/leadership-council/blob/main/minutes/sync-meeting/2025-03-28.md) |
| 93 | +* [April 11, 2025](https://github.com/rust-lang/leadership-council/blob/main/minutes/sync-meeting/2025-04-11.md) |
| 94 | +* [April 25, 2025](https://github.com/rust-lang/leadership-council/blob/main/minutes/sync-meeting/2025-04-25.md) |
| 95 | +* [May 9, 2025](https://github.com/rust-lang/leadership-council/blob/main/minutes/sync-meeting/2025-05-09.md) |
| 96 | +* [May 23, 2025](https://github.com/rust-lang/leadership-council/blob/main/minutes/sync-meeting/2025-05-23.md) |
| 97 | + |
| 98 | +[minutes]: https://github.com/rust-lang/leadership-council/tree/main/minutes |
0 commit comments