-
Notifications
You must be signed in to change notification settings - Fork 319
Lessons learned from the Rust Vision Doc #1746
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
Conversation
|
One thing I'd like is suggestions for a snappier title! |
|
"Initial Vision of the Rust Vision Doc"? |
PLeVasseur
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice write-up. Mostly a couple of typos / rewords.
Wanted to highlight the idea of a potential user research team in supporting gathering feedback on some particular questions Rust Project Teams may be coming up against.
jackh726
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Really solid, only one small comment. (Maybe you also want to weave in @Kobzol's point about T-survey.)
|
OK, @jackh726 done -- shall we merge? |
|
Let's merge, but you need to fix the date at the top of the doc :) |
eea4da7 to
3e649e1
Compare
The first blog post resulting from the Rust Vision Doc effort.
cc @rust-lang/project-vision-doc-2025
Rendered