Skip to content

Add 2018 survey announcement #265

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 6 commits into from
Aug 8, 2018
Merged

Conversation

sophiajt
Copy link
Contributor

@sophiajt sophiajt commented Aug 7, 2018

Draft of the 2018 survey announcement

@rust-highfive
Copy link

r? @alexcrichton

(rust_highfive has picked a reviewer for you, use r? to override)

@sophiajt
Copy link
Contributor Author

sophiajt commented Aug 8, 2018

@alexcrichton - we're not quite ready. @Manishearth is currently reviewing and will make a few edits first.

@aturon
Copy link
Member

aturon commented Aug 8, 2018

cc @rust-lang/core

layout: post
title: "Launching the 2018 State of Rust Survey"
author: The Rust Community Team
description: "Hearing from you about the second year of Rust"
Copy link
Member

Choose a reason for hiding this comment

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

third year :-)

Choose a reason for hiding this comment

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

Ah to be young again

@mgattozzi
Copy link

Besides the third year thing and getting the languages in for the survey this LGTM and I'm excited to tally all this up and see how the community is doing! :D

@Manishearth
Copy link
Member

sophiajt#1

description: "Hearing from you about the third year of Rust"
---

It's that time again! Time for us to take a look at how the Rust project is doing, and where we should plan for the future. The Rust Community Team is pleased to announce our [2018 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 to establish development priorities for the future.
Copy link
Member

Choose a reason for hiding this comment

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

"where we should plan for the future" sounds strange with the "how" in the first part of the sentence, and sounds like we're trying to decide a place to meet? "what we should plan for the future" sounds better to me

Copy link
Member

Choose a reason for hiding this comment

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

"Your responses will help the project understand its strengths and weaknesses, and to establish development priorities for the future."

I would change this to:

"Your responses will help the project understand its strengths and weaknesses and establish development priorities for the future."

(remove the comma and "to")


It's that time again! Time for us to take a look at how the Rust project is doing, and where we should plan for the future. The Rust Community Team is pleased to announce our [2018 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 to establish development priorities for the future.

Completing this survey should take about 10 to 15 minutes, and is anonymous unless you choose to give us your contact information. We will be accepting submissions until September 8th, and we will write up our findings a month or so afterwards to [blog.rust-lang.org]. You can see last year’s results [here][2017 survey].
Copy link
Member

Choose a reason for hiding this comment

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

I would remove the comma after "minutes" because "is anonymous..." isn't a complete sentence


Completing this survey should take about 10 to 15 minutes, and is anonymous unless you choose to give us your contact information. We will be accepting submissions until September 8th, and we will write up our findings a month or so afterwards to [blog.rust-lang.org]. You can see last year’s results [here][2017 survey].

This year, volunteers have also translated the survey into many languages! You can now take the survey in a number of languages:
Copy link
Member

Choose a reason for hiding this comment

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

"many languages" and "number of languages" sounds repetitive, what about "You can now take the survey in:"?

(If you speak multiple languages, please pick one)


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.
Copy link
Member

Choose a reason for hiding this comment

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

plz add oxford comma after "around your office" thx :)

@sophiajt
Copy link
Contributor Author

sophiajt commented Aug 8, 2018

This now has @aturon and @carols10cents fixes added.

@sophiajt
Copy link
Contributor Author

sophiajt commented Aug 8, 2018

@rust-lang/core - We should be ready. We'll take the surveys live before this hits the blog, just let us know when.

@Mark-Simulacrum
Copy link
Member

The post looks good to me, but I am unable to view the survey, so can't really approve or request changes there. Presumably it's good, though!

@sophiajt
Copy link
Contributor Author

sophiajt commented Aug 8, 2018

@Mark-Simulacrum - I can add if you if you like. It's nearly identical to last year's survey with a few wording tweaks and a couple new questions

@Mark-Simulacrum
Copy link
Member

Doesn't matter to me -- I'll review it if you want.

@sophiajt
Copy link
Contributor Author

sophiajt commented Aug 8, 2018

@Mark-Simulacrum - thanks. I think we're probably good there, since it's the third year for pretty much the same survey.

@ashleygwilliams ashleygwilliams dismissed carols10cents’s stale review August 8, 2018 20:32

suggestions were address

@ashleygwilliams ashleygwilliams merged commit 957448f into rust-lang:gh-pages Aug 8, 2018
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.

9 participants