-
Notifications
You must be signed in to change notification settings - Fork 301
Add post announcing the survey 2022 launch #1052
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
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,49 @@ | ||
--- | ||
layout: post | ||
title: "Launching the 2022 State of Rust Survey" | ||
author: The Rust Survey Working Group | ||
description: "Hearing from you about the seventh year of Rust" | ||
--- | ||
|
||
The [2022 State of Rust Survey][survey] is here! | ||
|
||
It's that time again! Time for us to take a look at who the Rust community is composed of, how the Rust project is doing, and how we can improve the Rust programming experience. The Rust Survey working group is pleased to announce our [2022 State of Rust Survey][survey]! Whether or not you use Rust today, we want to know your opinions. Your responses will help the project understand its strengths and weaknesses, and establish development priorities for the future. | ||
|
||
Completing this survey should take about 5–20 minutes and is anonymous. We will be accepting submissions for the next two weeks (until the 19th of December), and we will share our findings on [blog.rust-lang.org] sometime in early 2023. You can also check out [last year’s results][2021 survey]. | ||
|
||
We're happy to be offering the survey in the following languages. If you speak multiple languages, please pick one. | ||
|
||
rylev marked this conversation as resolved.
Show resolved
Hide resolved
|
||
- [English] | ||
- [Simplified Chinese] | ||
- [Traditional Chinese] | ||
- [French] | ||
- [German] | ||
- [Japanese] | ||
- [Korean] | ||
- [Portuguese] | ||
- [Russian] | ||
- [Spanish] | ||
rylev marked this conversation as resolved.
Show resolved
Hide resolved
|
||
- [Ukrainian] | ||
|
||
Please help us spread the word by sharing the survey link on your social network feeds, at meetups, around your office, and in other communities. | ||
|
||
If you have any questions, please see our [frequently asked questions]. | ||
|
||
Finally, we wanted to thank everyone who helped develop, polish, and test the survey. | ||
|
||
[blog.rust-lang.org]: https://blog.rust-lang.org | ||
[frequently asked questions]: https://github.com/rust-lang/surveys/blob/main/documents/Community-Survey-FAQ.md | ||
[2021 survey]: https://blog.rust-lang.org/2022/02/15/Rust-Survey-2021.html | ||
|
||
[survey]: https://surveyhero.com/c/sfhmgxgd | ||
[English]: https://surveyhero.com/c/sfhmgxgd?lang=en | ||
[Portuguese]: https://surveyhero.com/c/sfhmgxgd?lang=pt | ||
[Simplified Chinese]: https://surveyhero.com/c/sfhmgxgd?lang=zh-cn | ||
[French]: https://surveyhero.com/c/sfhmgxgd?lang=fr | ||
[Korean]: https://surveyhero.com/c/sfhmgxgd?lang=ko | ||
[Spanish]: https://surveyhero.com/c/sfhmgxgd?lang=es | ||
[Russian]: https://surveyhero.com/c/sfhmgxgd?lang=ru | ||
[Traditional Chinese]: https://surveyhero.com/c/sfhmgxgd?lang=zh-tw | ||
[German]: https://surveyhero.com/c/sfhmgxgd?lang=de | ||
[Japanese]: https://surveyhero.com/c/sfhmgxgd?lang=ja | ||
[Ukrainian]: https://surveyhero.com/c/sfhmgxgd?lang=uk |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
This says it takes about 5-20 minutes, while the introduction page of the survey states 10-25 minutes. It might be worth aligning the two statements. I'm usually a slow reader so maybe not the best judge to determine, which is the actual time, but I'd guess it's more 10-25 minutes.
I could create a PR, if that would update the text automatically :)