Add Community team and State of Rust survey FAQ

Author: XAMPPRocky

src/SUMMARY.md

@@ -3,6 +3,8 @@
 [Overview](./README.md)
 - [Core](./core/README.md)
     - [Rust Blog Guidelines](./core/blogs.md)
+- [Community](./community/README.md)
+    - [State of Rust Survey FAQ](./community/survey-faq.md)
 - [Compiler](./compiler/README.md)
     - [Bug Fix Procedure](./compiler/bug-fix-procedure.md)
     - [Cross Compilation](./compiler/cross-compilation/README.md)

src/community/README.md

@@ -0,0 +1,13 @@
+# Community
+
+This section documents the processes of the community team, and related projects.
+
+### External Links
+
+- The [Community team] GitHub repository contains information about how the community team organises.
+- The [RustBridge] website contains information on hosting your own local RustBridge event.
+- [Rustlings] is an project with small exercises designed around getting newcomers used to reading and writing Rust.
+
+[community team]: https://github.com/rust-community/team
+[rustbridge]: https://rustbridge.com
+[rustlings]: https://github.com/rust-lang/rustlings

src/community/survey-faq.md

@@ -0,0 +1,52 @@
+# State of Rust Survey FAQ
+
+In this FAQ we try to answer common questions about the Annual State of the Rust Language Community Survey. If in your opinion there is a missing question or if you have a concern about this document, please do not hesitate to contact the [Rust Community Team]([email protected]) or open an [issue with the Community Team](https://github.com/rust-community/team/issues).
+
+## Why is this survey important for the Rust project?
+
+[Rust](https://rust-lang.org) is an Open Source project. As such, we want to hear both from people inside and outside our ecosystem about the language, how it is perceived, and how we can make the language more accessible and our community more welcoming. This feedback will give our community the opportunity to participate on shaping the future of the project. We want to focus in the requirements of the language current and potential users to offer a compelling tool for them to solve real world problems in a safe, efficient and modern way.
+
+## What are the goals of the survey?
+
+- To understand the community's main development priorities and needs
+- To categorize the population of users of the language
+- To focus our efforts on events and conferences to drive more impact
+- To identify potential new contributors to the community goals
+
+## How much time will it take to answer the survey?
+
+In average, it should take from 10 to 15 minutes.
+
+## What kind of questions are included in the survey?
+
+It includes some basic questions about how do responders use Rust, their opinion the ecosystem's tools and libraries, some basic questions regarding the responders' employer or organization and their intention to use Rust, technical background and demographic questions and some feedback related to the Rust project's community activities and general priorities.
+
+## How will we use the data from the survey responses?
+
+The answers from the survey will be anonymized, aggregated, and summarized. A high level writeup will be posted to https://blog.rust-lang.org.
+
+### How is personally identifiable information handled?
+
+Nearly every question in the survey is optional. You are welcome to share as much or as little information as you are comfortable with. Only the Rust language Core Team and the Community Team Survey Leads will have access to the raw data from the survey. All the answers are anonymized prior to be shared with the rest of the teams and prior to the results publication.
+
+### Why is the survey collecting contact information?
+
+The survey optionally collects contact information for the following cases if you expressed interest in:
+
+- future conferences or meetups in your area
+- helping to organize a Rust event, meetup, or conference
+- talking to a Rust team about using Rust inside your company
+- Rust training
+- interest in a Rust team contacting you about your survey responses
+
+If you would like to be contacted about any of this, or any other concerns, but you don't want to associate your email with your survey responses, you can instead email the Rust Community Team at [email protected] or the Core Team at [email protected], and we will connect you to the right people.
+
+## Where and when is the survey results report published?
+
+We expect to publish results from the survey within a month or two of the survey completion. The survey results will be posted to [project's blog](https://blog.rust-lang.org).
+
+## Where can I see the previous survey reports?
+
+- [State of Rust 2018](https://blog.rust-lang.org/2018/11/27/Rust-survey-2018.html)
+- [State of Rust 2017](https://blog.rust-lang.org/2017/09/05/Rust-2017-Survey-Results.html)
+- [State of Rust 2016](https://blog.rust-lang.org/2016/06/30/State-of-Rust-Survey-2016.html)