Skip to content

Commit a1bc42a

Browse files
Merge pull request #1 from aidanhs/roadmap-2021-call
User-storyish request
2 parents 277173e + 2ae42e0 commit a1bc42a

File tree

1 file changed

+8
-1
lines changed

1 file changed

+8
-1
lines changed

posts/2020-09-03-Planning-2021-Roadmap.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,14 @@ release: false
77

88
The core team is beginning to think about the 2021 Roadmap, and we want to hear from the community. We’re going to be running two parallel efforts over the next several weeks: the 2020 Rust Survey, to be announced next week, and a call for blog posts.
99

10-
Blog posts can contain anything related to Rust: language features, tooling improvements, organizational changes, ecosystem needs — everything is in scope. We would encourage you to try to identify themes or broad areas into which your suggestions fit in, because these help guide the project as a whole. We are trying something a bit different this year. When you write a post, please submit it into [this google form](https://forms.gle/Hv41uA5qJEY89XRm7) so we don’t miss it! We will try to look at posts not submitted via this form, too, but posts submitted here aren’t going to be missed. Any platform — from blogs to GitHub gists — is fine!
10+
Blog posts can contain anything related to Rust: language features, tooling improvements, organizational changes, ecosystem needs — everything is in scope. We encourage you to try to identify themes or broad areas into which your suggestions fit in, because these help guide the project as a whole.
11+
12+
One way of helping us understand the lens you're looking at Rust through is to give one (or more) statements of the form "As a X I want Rust to Y because Z". These then may provide motivation behind items you call out in your post. Some examples might be:
13+
14+
- "As a day-to-day Rust developer, I want Rust to make consuming libraries a better experience so that I can more easily take advantage of the ecosystem"
15+
- "As an embedded developer who wants to grow the niche, I want Rust to make end-to-end embedded development easier so that newcomers can get started more easily"
16+
17+
This year, to make sure we don’t miss anything, when you write a post please submit it into [this google form](https://forms.gle/Hv41uA5qJEY89XRm7)! We will try to look at posts not submitted via this form, too, but posts submitted here aren’t going to be missed. Any platform — from blogs to GitHub gists — is fine!
1118

1219
To give you some context for the upcoming year, we established these high-level goals for 2020, and we wanted to take a look back at the first part of the year. We’ve made some excellent progress!
1320

0 commit comments

Comments
 (0)