Program management update — June 2026

Program management — meetings

We started attending the Types meetings. The topic is something neither of us are deeply familiar with, but the team was extremely welcoming, and kept stressing that we ask questions any time we can't follow something. To help us better understand recent topics, they pointed us to the Well-formedness article on the Rust Compiler Development Guide page.

The Rustdoc team considered having virtual face-to-face meetings in place of the async ones they've been having over Zulip. We joined, and minuted the meeting, but the team decided to stick with async for now. They did raise an interest in doing something akin to the Language Design meetings — and they would appreciate a PM presence there.

Finally, the Types team started a library trait evolution experiment to explore designs for evolving the standard library types (e.g. supertrait auto-impl, Sized hierarchy, and immobile types). There is a Zulip channel for discussion, and a recurring meeting we set up.

Project goals

Funding

Each goal can now add a section requesting funding (e.g., improve rustc_codegen_cranelift performance). Roadmaps now list the funding information across all their goals (e.g., Fast Builds). There is also a funding overview across all goals.

If you have a Project goal that needs financial support, add a funding section according to the template. If you're interested in supporting a goal financially, you may reach out to the contact listed on the funding page.

Help wanted

We also have a page for goals that are looking for contributors, analogous to the funding page. If you're interested in joining an effort, please check it out, and contact the goal owner.

If your goal needs help, add a Help wanted section using the template.

New goals

We've accepted several new goal proposals:

We're considering new Project goal proposals year-round! Here's how to propose a new goal. Once you open the pull request, we'll work with you to make sure everything is set.

Note that we still require that the teams with asks on them sign off, and that teams with medium or larger asks have a champion. This is a way to make sure the teams aren't over-committing their capacity.

We're also looking for ways to streamline the current process, let teams handle their goals more directly, and make larger long-term improvements.

Leadership Council

We'd like to highlight a few developments that recently came out of the Leadership Council meetings.

As a reminder: the meetings happen every two weeks on Friday at 11:30 New York time. We publish meeting notes in the Council repo and summaries on Zulip. The draft agenda is usually posted on the Monday before the meeting.

Keep in mind that the Council meetings may be observed by all Project members — if you'd like to join, talk to your representative.

If you don't know who your representative is, look your name up in the All Rust team members page, then click on the teams you're active in, which should get you to the top-level teams (e.g. Compiler, Language, Library, Launching pad, Infrastructure, etc.), and then look up the current representative on the Leadership Council team page.

T-comprehensibility

David Wood proposed chartering a Comprehensibility team:

Comprehensibility is a long-standing deficiency of the Rust Project. New contributors and organisations interested in participating in the project have a difficult time understanding how to contribute, and cross-team collaboration is impeded by mismatched expectations and working practices. Teams retain the ultimate decision making power about the content of their charters, process and policies, but t-comprehensibility will be involved in the drafting and updating to ensure that the project's documentation is consistent and coherent overall.

Documentation (especially process documentation) is something that must be actively maintained, and without a sustained effort it's among the first things to become stale. Having a team of individuals with an interest to keep it updated sounds like a great idea.

The proposal has finished its final comment period (FCP) and is expected to merge. The team creation will follow.

The next All Hands

Mara Bos proposed, and the Council accepted, to hold the next All Hands in 2027, and collocate it with RustWeek, organized by RustNL, once again. They have also agreed to reserve $50,000 for the All Hands out of the next year's Council budget, if there is money left after PMs are paid. This will be in addition to funding the travel grants (again, contingent on the availability of funds).

Based on the feedback received from the All Hands attendees, this is fantastic news for a huge number of people.

LLM committee

oli proposed creating an LLM committee that would have the power (delegated by the Council) to write and edit the LLM policy for the Project. It would be composed of 4-5 people representing the diverse views on the topic across the Project, be trusted by the Council and the Project, and have the ability to work together and make progress despite disagreement.

The team is explicitly designed such that everyone should feel comfortable reaching out to at least one committee member. It should also be able to adapt to the frequent changes in the AI industry without causing too much churn.

This is very much under open, active discussion. It will need a careful read and consideration. We're happy with this development and hope it works out.

On a personal note, I (Tomáš) would love to see Rust moving towards having a clearer policy on the matter, and as a project, we have not done so thus far. I'm curious to see what happens here. I hope we all manage to stay on topic on the issue (this is about how we move forward, not what the policy should be and why).

Program management

There were two proposals concerning Program management opened in the last couple of weeks:

Discuss long-term place for Program Management program by TC
Charter Program Management Team by Rémy Rakic (lqd)

The first one focuses on who's responsible for the funding and management of the Program managers (presently Nurzhan and Tomáš, and possibly Antonio Piraino serving as compiler-ops). Josh Triplett suggests this be the same team that would manage the Maintainers in Residence.

The second one is concerned with chartering the PM team, listing their responsibilities and expectations. People management is work that plenty of people (e.g. TC, Niko Matsakis, Eric Huss) have done before we joined, and it will keep happening. The proposal acknowledges this and formalizes the role.

Rust for Linux

Our regular meetings resumed after the All Hands.

Miguel Ojeda mentioned that zerocopy is now the first (third-party) crate they vendor that can directly generate code in the kernel image \o/.

The team would also like to have a runtime toggle in Rustdoc that would let them show private and hidden items in the documentation. Rustdoc can show this information already, but only at build-time using the --document-private-items and --document-hidden-items. We've opened a discussion on Zulip, but it hasn't been resolved yet.

Finally, Benno Lossin shared an example of what field access would desugar to using the Field projection mechanism of places and handles. This is important because it lets us validate it on existing field projections (e.g. for shared and mutable references), and see exactly what any proposed syntax for extending this to other kinds of pointers would do in normal Rust code that we ship today.

Rust for CPython

Following the discussion at the All Hands, the CPython folks met with us on 2026-07-02 to discuss Project goals.

We came up with some goals worth considering:

Rust in CPython in general (it might make sense for this to be a Roadmap)
Project build design space (building things without using Cargo)
Thread state memory
Stabilizing macro metavar
Stabilizing the Rust dylib format

In some cases, people are either currently working on or have looked into similar areas in the past, so the team will have those conversations first and then start opening goals.

Worth a look

June (and the early bits of July) was extremely prolific in terms of blog posts and announcements!

Project updates

Foundation posts

Stats

Total words of meeting minutes written: 662k (June 2025–June 2026)

Meetings attended: 40

Total words of meeting minutes written (May): 68.1k

Average (mean) word count per team meeting:

Cargo: 2.1k
Lang triage: 3.0k
Libs-API: 5k
Leadership Council: 2.1k