Running the program
So... somebody suckered you into serving as the owner of the goals program. Congratulations! This page will walk you through the process.
Call for proposals
Each goal milestone corresponds to six months, designated in the format YYYYHN, e.g., 2024H2 or 2025H1. To launch a new goal season, you should get started a month or two before the new season starts:
- For an H1 season, start around mid Oct or November of the year before.
- For an H2 season, start around mid April or May of the year before.
This is the checklist of steps to starting accepting goal proposals:
-
Prepare a Call For Proposals blog post on the Inside Rust blog based on this sample.
- We use Inside Rust and not the Main blog because the target audience is would-be Rust contributors and maintainers.
- Update the main README page to indicate that the next round of goals is begin accepted.
-
Create a new directory
src/YYYYhN, e.g.,src/2025h1, with the following files. Note that the sample files below include<!-- XXX -->directives that are detected by the mdbook plugin and replaced with appropriate content automatically.- A
src/YYYYhN/README.mdfile that contains the draft RFC. - A
src/YYYYhN/goals.mdfile containing the draft goal listing. - A
src/YYYYhN/not_accepted.mdfile containing the list of goals that were not accepted.
- A
- Modify SUMMARY.md to include your new milestone with some text like what is shown below.
Sample SUMMARY.md comments from 2025H1:
# ⏳ 2025H1 goal process
- [Overview](./2025h1/README.md)
- [Proposed goals](./2025h1/goals.md)
- [Goals not accepted](./2025h1/not_accepted.md)
Receiving PRs
to be written
Preparing the RFC
to be written
Opening the RFC
to be written
Once the RFC is accepted
to be written
Running the goal season
- Every Monday go to Zulip and run:
[TriageBot][] ping-goals 14 Oct-21
- To prepare the monthly blog post:
- Run the
cargo run -- updatescommand - Create a new post in main Rust blog found at the blog.rust-lang.org repository.
- Run the