Skip to content

async vison doc "shiny future" blog post #814

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

nikomatsakis
Copy link
Contributor

@nikomatsakis nikomatsakis commented Apr 6, 2021

This blog post announces the start of accepting "shiny future" stories. Like the last one, I have put it on the main rust blog, so cc @rust-lang/core for approval. I have dated the post for next Monday (2021-04-12), so as to leave time for folks to review and leave comments.

This post has a different structure than the previous one. It is shorter and more to the point, using a FAQ to help answer common questions and to direct readers to the previous post if they want to read up more on the motivation and background.

There are a few "to do" items before this is actually posted:

  • Update the number of landed stories and PRs, which will likely be different;
  • Update the number of collaborative writing sessions depending on what @rylev does this week;
  • Perhaps add a sentence linking to an example shiny future story, we don't have any yet.

cc @rust-lang/wg-async-foundations

@nikomatsakis nikomatsakis requested a review from a team April 6, 2021 19:42
Copy link
Member

@ashleygwilliams ashleygwilliams left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

few comments, think that structurally an FAQ in a blogpost is maybe not the right match but am curious what you think

rylev
rylev previously approved these changes Apr 7, 2021
@Mark-Simulacrum
Copy link
Member

@nikomatsakis I think we will likely want to push out the publication date to Tuesday or Wednesday at the earliest, as the edits here are somewhat amorphous at present, and a (shorter) re-review after the edits is likely necessary.

@nikomatsakis
Copy link
Contributor Author

Hmm, I had hoped to circle back to this on Friday or over the weekend, but I didn't wind up having time for that. Re-reading the post, I think you all were right about the FAQ not being the most compelling format. I've reworked it and I've adjusted the date to 2021-04-14 (Wednesday), as @Mark-Simulacrum suggested.

Thanks for the feedback @ashleygwilliams and @Mark-Simulacrum. I've removed the FAQ completely -- most of that material was already present on the site anyhow (I'll add what was missing there).

Copy link
Member

@ashleygwilliams ashleygwilliams left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, also i just wanna share that i think this process is really great and what you're all doing seems exciting- looking forward to hearing more :)

@Mark-Simulacrum
Copy link
Member

Left two comments - but I wouldn't view them as blockers, just nice to have potentially. I think we're good to go merging this tomorrow.

@Mark-Simulacrum
Copy link
Member

This looks great! I am planning to merge in ~1.5 hours, around 11am ET.

@Mark-Simulacrum Mark-Simulacrum merged commit 58be280 into rust-lang:master Apr 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants