TEMPLATE (replace with title of your goal)

Instructions: Copy this template to a fresh file with a name based on your plan. Give it a title that describes what you plan to get done in the next 6 months (e.g., "stabilize X" or "nightly support for X" or "gather data about X"). Feel free to replace any text with anything, but there are placeholders designed to help you get started.

The point of contact is the person responsible for providing updates.

The status should be either Proposed (if you have owners) or Proposed, Invited (if you do not yet).

Summary

Short description of what you will do over the next 6 months.

Motivation

Begin with a few sentences summarizing the problem you are attacking and why it is important.

The status quo

Elaborate in more detail about the problem you are trying to solve. This section is making the case for why this particular problem is worth prioritizing with project bandwidth. A strong status quo section will (a) identify the target audience and (b) give specifics about the problems they are facing today. Sometimes it may be useful to start sketching out how you think those problems will be addressed by your change, as well, though it's not necessary.

The next 6 months

Sketch out the specific things you are trying to achieve in this goal period. This should be short and high-level -- we don't want to see the design!

The "shiny future" we are working towards

If this goal is part of a larger plan that will extend beyond this goal period, sketch out the goal you are working towards. It may be worth adding some text about why these particular goals were chosen as the next logical step to focus on.

This text is NORMATIVE, in the sense that teams should review this and make sure they are aligned. If not, then the shiny future should be moved to frequently asked questions with a title like "what might we do next".

However, for most proposals, alignment on exact syntax should not be required to start a goal, only alignment on the problem and the general sketch of the solution. This may vary for goals that are specifically about syntax, such as ergonomic improvements.

Team asks

This section outlines what support you need from the Rust teams. For each team, identify the level of support you need:

• Vibes: You don't need the team to do anything at all, but you do want to know they like your idea.
  • Example: Prototyping a new feature on crates.io that you hope to eventually upstream.
  • Example: Conducting research that might eventually become a language feature.
• Small: You only need the team to do its routine activities.
  • Example: A compiler change that will require a few small PRs to be reviewed.
  • Example: Asking the lang team to approve a lint.
• Medium: You need dedicated support from one person, but the rest of the team doesn't have to do much.
  • Example: A compiler change that doesn't require any rearchitecting but
  • Example: Implementing a small, noncontroversial language feature.
• Large: You need deeper review from the entire team.
  • Example: Rearchitecting part of the compiler.
  • Example: Implementing a complex language feature that will require design meetings.

If you're not sure, leave it blank, the project goals team can help.

"Vibes" and "Small" asks require someone on the team to "second" your goal; "Medium" and "Large" asks require a dedicated champion from the team. If you don't have a second or a champion, the project goals team will help you find them, don't worry about it.

Frequently asked questions

What do I do with this space?

This is a good place to elaborate on your reasoning above -- for example, why did you put the design axioms in the order that you did? It's also a good place to put the answers to any questions that come up during discussion. The expectation is that this FAQ section will grow as the goal is discussed and eventually should contain a complete summary of the points raised along the way.