create a 2025H2 RFC

Author: Niko Matsakis

src/2025h2/README.md

@@ -0,0 +1,103 @@
+# Rust project goals 2025h2
+
+
+## Summary
+
+*![Status: Accepting goal proposals](https://img.shields.io/badge/Status-Accepting%20goal%20proposals-yellow) We are in the process of assembling the goal slate.*
+
+This is a draft for the eventual RFC proposing the 2025h2 goals.
+
+## Motivation
+
+The 2025h2 goal slate consists of <!-- #GOALS --> project goals, of which we have selected (TBD) as **flagship goals**. Flagship goals represent the goals expected to have the broadest overall impact.
+
+### How the goal process works
+
+**Project goals** are proposed bottom-up by a **point of contact**, somebody who is willing to commit resources (time, money, leadership) to seeing the work get done. The point of contact identifies the problem they want to address and sketches the solution of how they want to do so. They also identify the support they will need from the Rust teams (typically things like review bandwidth or feedback on RFCs). Teams then read the goals and provide feedback. If the goal is approved, teams are committing to support the point of contact in their work.
+
+Project goals can vary in scope from an internal refactoring that affects only one team to a larger cross-cutting initiative. No matter its scope, accepting a goal should never be interpreted as a promise that the team will make any future decision (e.g., accepting an RFC that has yet to be written). Rather, it is a promise that the team are aligned on the contents of the goal thus far (including the design axioms and other notes) and will prioritize giving feedback and support as needed.
+
+Of the proposed goals, a small subset are selected by the roadmap owner as **flagship goals**. Flagship goals are chosen for their high impact (many Rust users will be impacted) and their shovel-ready nature (the org is well-aligned around a concrete plan). Flagship goals are the ones that will feature most prominently in our public messaging and which should be prioritized by Rust teams where needed.
+
+### Rust’s mission
+
+Our goals are selected to further Rust's mission of **empowering everyone to build reliable and efficient software**. Rust targets programs that prioritize
+
+* reliability and robustness;
+* performance, memory usage, and resource consumption; and
+* long-term maintenance and extensibility.
+
+We consider "any two out of the three" as the right heuristic for projects where Rust is a strong contender or possibly the best option.
+
+### Axioms for selecting goals
+
+We believe that...
+
+* **Rust must deliver on its promise of peak performance and high reliability.** Rust’s maximum advantage is in applications that require peak performance or low-level systems capabilities. We must continue to innovate and support those areas above all.
+* **Rust's goals require high productivity and ergonomics.** Being attentive to ergonomics broadens Rust impact by making it more appealing for projects that value reliability and maintenance but which don't have strict performance requirements.
+* **Slow and steady wins the race.** For this first round of goals, we want a small set that can be completed without undue stress. As the Rust open source org continues to grow, the set of goals can grow in size.
+
+## Guide-level explanation
+[guide-level-explanation]: #guide-level-explanation
+
+### Flagship goals
+
+The flagship goals proposed for this roadmap are as follows:
+
+(TBD)
+
+#### Why these particular flagship goals?
+
+(TBD--typically one paragraph per goal)
+
+### Project goals
+
+The full slate of project goals are as follows. These goals all have identified points of contact who will drive the work forward as well as a viable work plan. The goals include asks from the listed Rust teams, which are cataloged in the [reference-level explanation](#reference-level-explanation) section below.
+
+**Invited goals.** Some goals of the goals below are "invited goals", meaning that for that goal to happen we need someone to step up and serve as a point of contact. To find the invited goals, look for the ![Help wanted][] badge in the table below. Invited goals have reserved capacity for teams and a mentor, so if you are someone looking to help Rust progress, they are a great way to get involved.
+
+<!-- GOALS -->
+
+# Reference-level explanation
+[reference-level-explanation]: #reference-level-explanation
+
+The following table highlights the asks from each affected team.
+The "owner" in the column is the person expecting to do the design/implementation work that the team will be approving.
+
+<!-- TEAM ASKS -->
+
+### Definitions
+
+Definitions for terms used above:
+
+* *Author RFC* and *Implementation* means actually writing the code, document, whatever.
+* *Design meeting* means holding a synchronous meeting to review a proposal and provide feedback (no decision expected).
+* *RFC decisions* means reviewing an RFC and deciding whether to accept.
+* *Org decisions* means reaching a decision on an organizational or policy matter.
+* *Secondary review* of an RFC means that the team is "tangentially" involved in the RFC and should be expected to briefly review.
+* *Stabilizations* means reviewing a stabilization and report and deciding whether to stabilize.
+* *Standard reviews* refers to reviews for PRs against the repository; these PRs are not expected to be unduly large or complicated.
+* Other kinds of decisions:
+    * [Lang team experiments](https://lang-team.rust-lang.org/how_to/experiment.html) are used to add nightly features that do not yet have an RFC. They are limited to trusted contributors and are used to resolve design details such that an RFC can be written.
+    * Compiler [Major Change Proposal (MCP)](https://forge.rust-lang.org/compiler/mcp.html) is used to propose a 'larger than average' change and get feedback from the compiler team.
+    * Library [API Change Proposal (ACP)](https://std-dev-guide.rust-lang.org/development/feature-lifecycle.html) describes a change to the standard library.
+
+[AGS]: ./Project-goal-slate.md
+[AMF]: ./a-mir-formality.md
+[Async]: ./async.md
+[ATPIT]: ./ATPIT.md
+[CS]: ./cargo-script.md
+[CT]: ./const-traits.md
+[ERC]: ./ergonomic-rc.md
+[MGCA]: ./min_generic_const_arguments.md
+[NBNLB]: ./Polonius.md
+[NGS]: ./next-solver.md
+[PET]: ./Patterns-of-empty-types.md
+[PGC]: ./pubgrub-in-cargo.md
+[RFL]: ./rfl_stable.md
+[SBS]: ./sandboxed-build-script.md
+[YKR]: ./yank-crates-with-a-reason.md
+[SC]: ./Rust-for-SciComp.md
+[OC]: ./optimize-clippy.md
+
+<!-- Github usernames -->

src/2025h2/goals.md

@@ -0,0 +1,22 @@
+# Goals
+
+
+This page lists the <!-- #GOALS --> project goals **proposed** for 2025h2.
+
+> Just because a goal is listed on this list does not mean the goal has been accepted.
+> The owner of the goal process makes the final decisions on which goals to include
+> and prepares an RFC to ask approval from the teams.
+
+## Flagship goals
+
+Flagship goals represent the goals expected to have the broadest overall impact. 
+
+<!-- FLAGSHIP GOALS -->
+
+## Other goals
+
+These are the other proposed goals. 
+
+**Invited goals.** Some goals of the goals below are "invited goals", meaning that for that goal to happen we need someone to step up and serve as a point of contact. To find the invited goals, look for the ![Help wanted][] badge in the table below. Invited goals have reserved capacity for teams and a mentor, so if you are someone looking to help Rust progress, they are a great way to get involved.
+
+<!-- OTHER GOALS -->

src/2025h2/not_accepted.md

@@ -0,0 +1,6 @@
+# Not accepted
+
+
+This section contains goals that were proposed but ultimately not accepted, either for want of resources or consensus. In many cases, narrower versions of these goals were proposed instead.
+
+<!-- GOALS NOT ACCEPTED -->

src/README.md

@@ -22,9 +22,10 @@ The 2025H1 goal period runs from Jan 1 to Jun 30. We have identified three flags
 
 [The full list of 2025H1 goals is available here.](./2025h1/goals.md) We author monthly blog posts about our overall status, but you can also follow the tracking issue for a [particular goal](./2025h1/goals.md) to get updates specific to that goal.
 
-## Next goal period (2025h2)
 
-Discussion about goals for the next goal period will begin in May.
+## Next goal period (2025H2)
+
+The next goal period will be 2025H2, running from July 1 to December 30. We are currently in the process of assembling goals. [Click here](./2025h2/goals.md) to see the current list. If you'd like to propose a goal, [instructions can be found here](./how_to/propose_a_goal.md).
 
 ## About the process
 

src/SUMMARY.md

@@ -10,7 +10,9 @@
 
 # ⏳ 2025H2 goal process
 
-- [Not yet started]()
+- [Overview](./2025h2/README.md)
+- [Proposed goals](./2025h2/goals.md)
+- [Goals not accepted](./2025h2/not_accepted.md)
 
 # 📖 Learn about