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/2025h1/rust-plan.md
+35-39Lines changed: 35 additions & 39 deletions
Original file line number
Diff line number
Diff line change
@@ -1,29 +1,21 @@
1
-
# Approved RFC for a Rust vision doc
1
+
# Rust Vision Document
2
2
3
-
| Metadata ||
4
-
|--------|--------------------|
5
-
| Owner(s) |@nikomatsakis|
6
-
| Teams |[Leadership Council]|
7
-
| Status | Proposed |
3
+
| Metadata ||
4
+
|----------|----------------------------------|
5
+
| Owner(s) |vision team led by @nikomatsakis|
6
+
| Teams |[Leadership Council]|
7
+
| Status | Proposed |
8
8
9
9
## Summary
10
10
11
-
Author a Rust "vision Doc" following a similar process/format to the async vision doc.
12
-
The final document will combine
11
+
Present a first draft of a "Rust Vision Doc" at the Rust All Hands in May.
13
12
14
-
* goals/mission of Rust;
15
-
* status quo stories documenting the kinds of projects people build in Rust and the experiences they have when doing so;
16
-
* recommendations for major problems to attack and key constraints of the domain;
17
-
* and appendices with raw data, statistics, etc.
18
-
19
-
Unlike the async vision doc, this document will not include a specific "shiny future" narrative.
20
-
Instead, it will focus on (a) building a shared understanding of where/how Rust is being used today
21
-
and (b) identifying upcoming trends and opportunities that Rust should address over the next 3-5 years.
13
+
The Rust Vision Doc will summarize the state of Rust adoption -- where is Rust adding value? what works well? what doesn't? -- based on conversations with individual Rust users from different communities, major Rust projects, and companies large and small that are adopting Rust. It will use that raw data to make recommendations on what problems Rust should be attacking and what constraints we should be trying to meet. The document will not include specific features or recommendations, which ought to be legislated through RFCs.
22
14
23
15
## Motivation
24
16
25
-
The goal is to author a "Rust Vision Doc" that identifies the key opportunities for Rust to improve the state of software development over the next 3-5 years.
26
-
The document will be focused primarily on documenting the status quo and identifying opportunities where Rust can do better.
17
+
The goal is to author a longer term "vision doc" that identifies key opportunities for Rust over the next 3-5 years.
18
+
The document will help us focus our energies and attack problems that move the needle for Rust.
27
19
28
20
### Rust's planning processes have a 6 month time window
29
21
@@ -69,31 +61,37 @@ For the Rust Vision Doc, we plan to take a different approach. Rather than autho
69
61
70
62
### The next 6 months
71
63
72
-
Here is the overall plan for 2025h1:
64
+
Our goal for the next 6 months is to present a first draft of the vision doc at the Rust All Hands, planned for May 2025.
65
+
We will use this opportunity to get feedback on the doc structure and recommendations and to begin work on the actual RFC,
66
+
excepted to be accepted in 2025H2.
67
+
68
+
Here is the overall plan for 2025H1:
73
69
74
-
| Task | Nov | Dec | Jan | Feb | Mar | Apr | May | Jun |
| Gather status quo stories ||| ███ | ███ | ░░░ ||||
74
+
| Coallesce stores and personae ||| ░░░ | ███ | ███ ||||
75
+
| Develop recommendations and goals |||| ░░░ | ███ ||||
76
+
| Review RFC Draft 1 at Rust All Hands |||||| ███ | ███ ||
77
+
|Publish a blog post with summarized feedback|||||||| ███ |
82
78
83
79
The plan actually begins *now*, in the goal construction phase. One of the tasks to be done is building up a **small support team** of researchers who will help with doing the interviews and authoring status quo stories and other parts of the document. As goal owner, nikomatsakis will select initial members. With the Async Vision Doc, our experience was that most Rust users are eager to share their experiences, but that authoring and upleveling that into a status quo story is challenging. It's better to centralize that authorship into a small group of motivated people.
84
80
85
81
The plan to finalize the document is as follows:
86
82
87
83
* We will be gathering and summarizing data for the first 3 months.
88
-
* In early April we will publish the first RFC draft on the RFC repository. We will also schedule several reading sessions to gather feedback from Rust maintainers.
89
-
* We will summarize the feedback we got and publish a second revision on the RFC repository. If necessary, we can repeat the iterations.
90
-
*The final approval of the RFC will be done by the Leadership Council, as the only group empowered to speak for all Rust teams.
84
+
* In early April we will begin authoring the first draft.
85
+
* We will present the first draft for review at the Rust All hands and associated Rust Week conference.
86
+
*We will publish a blog post with collected feedback.
91
87
92
88
Approval of the RFC indicates general alignment with the framing and prioritizes it describes. It will not commit any Rust team to any particular action.
93
89
94
90
### The "shiny future" we are working towards
95
91
96
-
Assuming this vision doc is succesful, we believe it should be refreshed on a regular basis. This would be a good completement to the Rust Project Goal system. Projet Goals describe the next few steps. The Vision Doc helps to outline the destination.
92
+
Assuming this vision doc is succesful, we believe it should be refreshed on a regular basis. This would be a good completement to the Rust Project Goal system. Project Goals describe the next few steps. The Vision Doc helps to outline the destination.
93
+
94
+
We also expect that the Vision Doc template may be useful in other more narrow contexts, such as a revised version of the Async Vision Doc,a vision doc for Rust in UI, machine learning, etc.
97
95
98
96
## Design axioms
99
97
@@ -102,14 +100,12 @@ Assuming this vision doc is succesful, we believe it should be refreshed on a re
0 commit comments