Team asks
A team ask is the thing that you need from a Rust team to make progress. The precise asks can vary from "Discussion and moral support" (basically, regular vibe checks) up until specific RFC or stabilization decisions. Asks cannot require a specific outcome (e.g., the ask cannot be "guarantee me that you will accept the RFC), as project goals are not meant to substitute for a real decision process.
The list of recognized asks is shown below:
- The Ask column indicates the text that should appear in your project goal table.
- The aka column is a shorter name for the ask used in the condensed RFC tables.
- The description column describes what you are asking for.
| Ask | aka | Description |
|---|---|---|
| "Allocate funds" | Alloc funds | allocate funding |
| "Discussion and moral support" | Good vibes | approve of this direction and be prepared for light discussion on Zulip or elsewhere |
| "Deploy to production" | Deploy | deploy code to production (e.g., on crates.io |
| "Standard reviews" | r? | review PRs (PRs are not expected to be unduly large or complicated) |
| "Dedicated reviewer" | Ded. r? | assign a specific person (or people) to review a series of PRs, appropriate for large or complex asks |
| "Lang-team champion" | Champion | member of lang team or advisors who will champion the design within team |
| "Lang-team experiment" | Experiment | begin a lang-team experiment authorizing experimental impl of lang changes before an RFC is written; limited to trusted contributors |
| "Design meeting" | Design mtg. | hold a synchronous meeting to review a proposal and provide feedback (no decision expected) |
| "RFC decision" | RFC | review an RFC and deciding whether to accept |
| "RFC secondary review" | RFC rev. | briefly review an RFC without need of a formal decision |
| "Org decision" | Org | reach a decision on an organizational or policy matter |
| "MCP decision" | MCP | accept a Major Change Proposal |
| "ACP decision" | ACP | accept an API Change Proposal |
| "Finalize specification text" | Spec text | assign a spec team liaison to finalize edits to Rust reference/specification |
| "Stabilization decision" | Stabilize. | reach a decision on a stabilization proposal |
| "Policy decision" | Policy | make a decision related to team policy |
| "FCP decision(s)" | FCP | make formal decision(s) that require 'checkboxes' and a FCP (Final Comment Period) |
| "Blog post approval" | Blog | approve of posting about this on the main Rust blog |
| "Miscellaneous" | Misc | do some one-off action as described in the notes |