You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/2024h2/README.md
+9-23Lines changed: 9 additions & 23 deletions
Original file line number
Diff line number
Diff line change
@@ -1,21 +1,14 @@
1
-
> * This RFC has been opened on the RFC repo as [RFC #3672].*
> * This goal slate has been accepted as [RFC #3672].*
7
2
8
3
## Summary
9
4
10
-
This RFC presents the Rust project goal slate for 2024H2. The slate consists of <!-- #GOALS --> total project goals of which we have selected 3 as our "flagship goals":
11
-
12
-
* Release the Rust 2024 edition (owner: @traviscross)
13
-
* Bring the Async Rust experience closer to parity with sync Rust (owners: @tmandry, @nikomatsakis)
14
-
* Resolve the biggest blockers to Linux building on stable Rust (owners: @joshtriplett, @nikomatsakis)
5
+
The Rust project has accepted <!-- #GOALS --> total project goals for 2024H2, with 3 designated as flagship goals:
15
6
16
-
Flagship goals represent the goals expected to have the broadest overall impact.
7
+
*[Release the Rust 2024 edition](./Rust-2024-Edition.md) (owner: @traviscross)
8
+
*[Bring the Async Rust experience closer to parity with sync Rust](./async.md) (owners: @tmandry, @nikomatsakis)
9
+
*[Resolve the biggest blockers to Linux building on stable Rust](./rfl_stable.md) (owners: @joshtriplett, @nikomatsakis)
17
10
18
-
**This RFC follows an [unusual ratification procedure](https://rust-lang.zulipchat.com/#narrow/stream/435869-project-goals-2024h2/topic/Procedural.20next.20steps.20and.20timeline). Team leads are asked to review the [list of asks for their team](#reference-level-explanation) and confirm that their team is aligned. Leads should feel free to consult with team members and to raise concerns on their behalf. Once all team leads have signed off, the RFC will enter FCP.**
11
+
Read on to learn more about our goal program!
19
12
20
13
## Motivation
21
14
@@ -82,18 +75,13 @@ The flagship goals proposed for this roadmap are as follows:
The slate of additional project goals are as follows. These goals all have identified owners 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. Some goals are actively looking for volunteers; these goals are tagged with ![Help wanted][].
80
+
The slate of additional project goals are as follows. These goals all have identified owners 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.
89
81
90
-
<!-- GOALS 'Proposed' -->
82
+
Some goals here do not yet have an owner (look for the ![Help wanted][] badge). Teams have reserved some capacity to pursue these goals but until an appropriate owner is found they are only considered provisionally accepted. If you are interested in serving as the owner for one of these orphaned goals, reach out to the mentor listed in the goal to discuss.
91
83
92
-
### Orphaned goals ![Help wanted][]
93
-
94
-
Goals in this section are "pre-approved" by the team but lack an owner. These indicate a place where we are looking for someone to step up and help drive the goal the goal to completion. Every orphaned goal has someone who is willing and able to serve as mentor, but lacks the time or resources to truly *own* the goal. If you are interested in serving as the owner for one of these orphaned goals, reach out to the listed mentor to discuss. Orphaned goals may also be used as the basis of applying for grants from the Rust Foundation or elsewhere.
@@ -119,8 +107,6 @@ Definitions for terms used above:
119
107
* 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.
120
108
* Library [API Change Proposal (ACP)](https://std-dev-guide.rust-lang.org/development/feature-lifecycle.html) describes a change to the standard library.
This page lists the project goals accepted for 2024h2, with the exception of [flagship goals](./flagship.md), which are listed separately.
4
+
5
+
Some goals here do not yet have an owner (look for the ![Help wanted][] badge). Teams have reserved some capacity to pursue these goals but until an appropriate owner is found they are only considered provisionally accepted. If you are interested in serving as the owner for one of these orphaned goals, reach out to the mentor listed in the goal to discuss.
0 commit comments