Are there changes to Rust that you, or your organization, would like to make happen? Do you need advice in getting started with that? The Rust Project Goals team is here to help!
We are currently beginning the "pre-planning" for the Rust 2026 goals. In this "pre-planning" phase, we are looking for people who have ideas for things they want to do but who are not sure how to interface with the Rust org to see it happen. We are particularly interested in supporting organizations and groups, which often have a harder time connecting to open source.
A project goal is a kind of a contract between you and the Rust project teams. When you propose a project goal, you are promising to do the work you describe. When the Rust teams approve your goal, they are committing to support you (e.g., by doing reviews, giving feedback, etc). To make sure this happens, every approved Rust project goal has a champion, a Rust team member or affiliate that will meet regularly with you and help ensure you stay unblocked.
For 2026, we are shifting to annual project goals (though a goal doesn't have to take the whole year). In the past, goals covered six month periods like 2025H1 and 2025H2.
| Time period | Activity |
|---|---|
| Dec 2025 (now!) | We are soliciting pre-proposals and assessing which 2025H2 goals will continue into 2026 |
| Jan 2026 | We will publish the first draft of the 2026 goal slate and begin discussion with Rust teams in earnest |
| (Continuing goals just continue working) | |
| Feb 2026 | Refinement of goals continues |
| Mar 2026 | Publish and merge the RFC with 2026 goals |
| Apr 2026 | Announce 2026 goals |
| July 2026 | Publish Q3 check-in on goal progress |
| Oct 2026 | Publish Q4 check-in and the whole thing begins again... |
Great! Reach out on Zulip in #project-goals/2026-workshop.
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。