rotate the current goal period (#293)

* rotate the current goal period

* document the process we've done over the last days

---------

Co-authored-by: Niko Matsakis <nikomat@amazon.com>

Author: nikomatsakis

src/2025h1/README.md

@@ -1,4 +1,4 @@
-> *![Status: RFC pending](https://img.shields.io/badge/Status-RFC%20pending-yellow) This set of goals has proposed as [RFC #3764](https://github.com/rust-lang/rfcs/pull/3764) on the Rust RFC repository.*
+> ![Status: Accepted](https://img.shields.io/badge/Status-Accepted-green) [RFC #3764] has been **accepted**, establishing [<!-- #GOALS --> total Rust project goals for 2025H1](./goals.md).
 
 ## Summary
 

src/README.md

@@ -2,17 +2,29 @@
 
 This repo tracks the effort to set and track goals for the Rust project.
 
-## Current goal period (2024h2)
+## Current goal period (2025H1)
 
-There are [26 total goals](./2024h2/goals.md) established for the current goal period, which runs until the end of 2024. Of these, 3 were declared as flagship goals:
+The 2025H1 goal period runs from Jan 1 to Jun 30. We have identified three flagship goals for 2025H1:
 
-* **Continue simplifying Rust** by [releasing the Rust 2024 edition](./2024h2/Rust-2024-Edition.md).
-* **Improve the experience of building network systems in Rust** by [bringing Async Rust experience closer to parity with sync Rust](./2024h2/async.md).
-* **Enable safe abstractions for low-level systems** by [resolving the biggest blockers to Linux building on stable Rust](./2024h2/rfl_stable.md).
+* Continue making Rust easier to use for network systems by [**bringing the Async Rust experience closer to parity with sync Rust**](./async.md). In 2025H1 we plan to:
+    * tell a complete story for the use of async fn in traits, unblocking wide ecosystem adoption;
+    * improve the ergonomics of `Pin`, which is frequently used in low-level async code; and
+    * prepare to support asynchronous (and synchronous) generators in the language.
+* Continue helping Rust support low-level projects by [**stabilizing compiler options and tooling used by the Rust-for-Linux project**](./rfl.md). In 2025H1 we plan to:
+    * implement [RFC #3716] to allow stabilizing ABI-modifying compiler flags to control code generation, sanitizer integration, and so forth;
+    * taking the first step towards stabilizing [`build-std`](https://rust-lang.github.io/rust-project-goals/2025h1/https://doc.rust-lang.org/cargo/reference/unstable.html#build-std) by [creating a stable way to rebuild core with specific compiler options](./build-std.html);
+    * add rustdoc features to extract and customize rustdoc tests (`--extract-doctests`);
+    * stabilize clippy configuration like `.clippy.toml` and `CLIPPY_CONF_DIR`;
+    * stabilize compiler flags to extract dependency info (e.g., as via `-Zbinary-dep-depinfo=y`) and to configure no-std without requiring it in the source file (e.g., as via `-Zcrate-attr`);
+* Address the biggest concerns raised by Rust maintainers, lack of face-to-face interaction, by [**organizing the Rust All-Hands 2025**](./all-hands.md). In 2025H1 we plan to:
+    * convene Rust maintainers to celebrate Rust's tenth birthday at [RustWeek 2025](https://2025.rustweek.org) (co-organized with [RustNL](https://2025.rustweek.org/about/));
+    * author a first draft for a [Rust vision doc](./rust-vision-doc.md) and gather feedback.
 
-## Next goal period (2025h1)
+[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.
 
-The next goal period will be 2025h1 runs from Jan 1 to Jun 30. We are currently in the process of assembling goals. [Click here](./2025h1/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).
+## Next goal period (2025h2)
+
+Discussion about goals for the next goal period will begin in 
 
 ## About the process
 

src/SUMMARY.md

@@ -2,19 +2,16 @@
 
 [👋 Introduction](./README.md)
 
-# ⚙️ 2024H2 goal process 
-
-- [Overview](./2024h2/README.md)
-- [Goals](./2024h2/goals.md)
-- [Goals not accepted](./2024h2/not_accepted.md)
-- [General notes](./2024h2/notes.md)
-
-# ⏳ 2025H1 goal process
+# ⚙️ 2025H1 goal process
 
 - [Overview](./2025h1/README.md)
-- [Proposed goals](./2025h1/goals.md)
+- [Goals](./2025h1/goals.md)
 - [Goals not accepted](./2025h1/not_accepted.md)
 
+# ⏳ 2025H2 goal process
+
+- [Not yet started]()
+
 # 📖 Learn about
 
 - [Goal motivations](./about/motivation.md)
@@ -25,6 +22,11 @@
 - [Task owners](./about/owners.md)
 - [Design axioms](./about/design_axioms.md)
 - [RFC](./rfc.md)
+* [Archived goal lists]()
+    * [2024H2](./2024h2/README.md)
+        * [Goals](./2024h2/goals.md)
+        * [Goals not accepted](./2024h2/not_accepted.md)
+        * [General notes](./2024h2/notes.md)
 
 # ❓ How to
 
@@ -39,6 +41,7 @@
     * [Team coordination](./admin/coordination.md)
     * [Call for proposals](./admin/cfp.md)
     * [Preparing the RFC](./admin/prepare_rfc.md)
+    * [Merging the RFC](./admin/merge_rfc.md)
     * [Authoring monthly updates](./admin/author_updates.md)
     * [Sample texts](./admin/samples.md)
         * [Sample: Call for Proposal blog post](./admin/samples/cfp.md)
@@ -52,4 +55,4 @@
         * [`rfc`, export RFC text](./admin/rfc_command.md)
         * [`fcp`, create the FCP merge comment](./admin/fcp_command.md)
         * [`issues`, creating tracking issues](./admin/issues.md)
-        * [`updates`, create monthly blog post summary](./admin/updates.md) 
+        * [`updates`, create monthly blog post summary](./admin/updates.md) 

src/admin/merge_rfc.md

@@ -0,0 +1,13 @@
+# Merging the RFC
+
+Once the RFC is accepted
+
+* Merge the RFC itself
+* Run `cargo rpg teams` to prepare adjustment to the teams repository
+    * In particular to populate the project-goal-owners team 
+    * This will be needed to allow people to author updates on their goals
+* Run `cargo rpg issues` to create and update tracking issues
+    * Continuing goals will be moved to the new milestone
+    * You can run this tool over and over to keep things synchronized
+* Close out of date issues
+    * For all issues in previous milestone, close them