|✅ Now till 2021-04-30||Improve the sample projects|
|✅ Now till 2021-04-30||Propose new "status quo" stories or comment on existing PRs|
|✅ Now till 2021-04-30||Propose new "shiny future" stories or comment on existing PRs|
|🛑 Starting 2021-04-30||Vote for the awards on the status quo and shiny future stories!|
The process we are using to write the vision doc encourages active collaboration and "positive sum" thinking. It starts with a brainstorming period, during which we aim to collect as many "status quo" and "shiny future" stories as we can.
This brainstorming period runs for six weeks, until the end of April. For the first two weeks (until 2021-04-02), we are collecting "status quo" stories only. After that, we will accept both "status quo" and "shiny future" stories until the end of the brainstorming period. Finally, to cap off the brainstorming period, we will select winners for awards like "Most Humorous Story" or "Most Supportive Contributor".
Once the brainstorming period is complete, the working group leads will begin work on assembling the various stories and shiny futures into a coherent draft. This draft will be reviewed by the community and the Rust teams and adjusted based on feedback.
The brainstorming period runs until 2021-04-30:
- Folks open "status quo" and "shiny future" story PRs against the wg-async-foundations repo.
- We collectively comment on these PRs, helping to improve them and make them more complete.
- Unless they contain factual inaccuracies, the aim is to merge all PRs opened in the brainstorming period.
- We also expect people to sometimes extend other stories with additional details or FAQs.
- At the end of the brainstorming period, we will vote and give awards for things like "most amusing". (We'd like suggestions on the best categories!)
During this brainstorming period, we want to focus on getting as many ideas as we can. Having multiple "shiny futures" that address the same problem is a feature, not a bug, as it will let us mix-and-match later to try and find the best overall plan. Comments and questions will be used as a tool for improving understanding or sharpening proposals. Presenting alternative ideas is done by writing an alternative story.
To merge a story or project PR, any member of the working group can open a topic on Zulip and propose it be merged. Ideally there will be no outstanding concerns. If a second member of the working group approves, the PR can then be merged.
Reviewers should ensure that new stories and projects are added to the
SUMMARY.md file either before merging or directly afterwards.
At this point, the wg leads will write the draft vision document, drawing on the status quo and shiny future stories that were submitted. Like an RFC, this draft vision doc will be opened for comment and improved based on the resulting feedback. When the wg leads feel it is ready, it will be taken to the lang and libs teams for approval (and other Rust teams as appropriate).
This meant to be a living document. We plan to revisit it regularly to track our progress and update it based on what we've learned in the meantime. Note that the shiny future stories in particular are going to involve a fair bit of uncertainty, so we expect them to change as we go.