@@ -5,59 +5,91 @@ title: Community
5
5
6
6
# Rust Community
7
7
8
- We have a great community and we want to keep it that way. Rust is
9
- more than just a revolutionary programming language, it is a
10
- tight-knit community with a [ legendary dedication to kindness and
11
- inclusivity] [ techwhirl ] . We are committed to providing a friendly,
12
- safe and welcoming environment for all, regardless of gender, sexual
13
- orientation, disability, ethnicity, religion, or similar personal
14
- characteristic. Our [ code of conduct] [ coc ] must be observed in
15
- all matters relating to Rust online.
8
+ Rust has a lot going for it as a language, but its greatest strength
9
+ is its tight-knit community and its focus on kindness and inclusivity.
10
+
11
+ We are committed to providing a friendly, safe and welcoming
12
+ environment for all, regardless of gender, sexual orientation,
13
+ disability, ethnicity, religion, or similar personal
14
+ characteristic. Our [ code of conduct] [ coc ] sets the standards for
15
+ behavior in all official Rust forums, and is upheld by the
16
+ [ moderation team] [ mod_team_email ] .
16
17
17
18
[ coc ] : https://www.rust-lang.org/conduct.html
18
- [ techwhirl ] : http://techwhirl.com/conference-report-friendly-diverse-rust-camp/
19
19
20
- ## News
20
+ ## TL;DR
21
21
22
- [ This Week in Rust] [ twir ]
22
+ The most important community resources for getting started with Rust are:
23
23
24
- This Week in Rust contains the latest news, upcoming events and a
25
- week-by-week account of changes in the Rust language and libraries.
24
+ - The [ #rust] [ rust_irc ] IRC channel, a very friendly channel that
25
+ loves answering questions at any depth.
26
+ - The [ users forum] [ users_forum ] for asynchronous discussion about all
27
+ things Rust.
28
+ - The [ This Week in Rust] [ twir ] newsletter, to keep up with what's
29
+ happening in the community.
30
+
31
+ ## News
26
32
27
- [ Rust Programming Blog] [ rust_blog ]
33
+ [ This Week in Rust] [ twir ] collects the latest news, upcoming events
34
+ and a week-by-week account of changes in the Rust language and
35
+ libraries.
28
36
29
- The Rust programming blog is where the Rust team makes announcements
37
+ [ The Rust Blog ] [ rust_blog ] is where the Rust team makes announcements
30
38
about major developments.
31
39
32
- [ Reddit] [ reddit ]
40
+ The Rust community has an [ * unofficial* subreddit] [ reddit ] where
41
+ virtually everything happening in the Rust community is discussed.
42
+ The forum abides by the [ official code of conduct] [ reddit_coc ] .
33
43
34
- Reddit is an unofficial online forum for all things Rust.
44
+ We also have an official [ Twitter ] [ twitter ] account,
35
45
36
46
[ twir ] : http://this-week-in-rust.org/
37
47
[ rust_blog ] : http://blog.rust-lang.org/
38
48
[ reddit ] : https://www.reddit.com/r/rust
49
+ [ reddit_coc ] : https://www.reddit.com/r/rust/comments/2rvrzx/our_code_of_conduct_please_read/
50
+ [ twitter ] : https://twitter.com/rustlang
39
51
40
52
## How to Get Help
41
53
42
- [ IRC Channels] [ rust_irc ]
54
+ ### Moderation
55
+
56
+ [ Rust Moderation Team] [ mod_team ]
57
+
58
+ If you feel you have been or are being harassed or made uncomfortable
59
+ by a community member, please [ contact] [ mod_team_email ] any of the
60
+ Rust moderation team immediately. Whether you're a regular contributor
61
+ or a newcomer, we care about making the community a safe space for
62
+ you.
63
+
64
+ [ mod_team ] : https://www.rust-lang.org/team.html#Moderation
65
+ [ mod_team_email ] : mailto:rust-mods@googlegroups.com
43
66
44
- Rustaceans primarily communicate via IRC. The
45
- [ #rust] [ rust_irc ] channel on Moznet is a venue for general
46
- discussion about Rust, and a good place to ask for help. You'll find
67
+ ### IRC channels
68
+
69
+ Rustaceans maintain a number of friendly, high-traffic IRC channels.
70
+
71
+ The [ #rust] [ rust_irc ] channel on Moznet is a venue for general
72
+ discussion about Rust, and a good place to ask for help. You'll find
47
73
people willing to help you with any questions you may have, and
48
- responses are typically very fast. To get involved in the development
49
- of Rust itself, for anything about contribution, or to find a mentor,
50
- [ #rust-internals] [ internals_irc ] is the right channel. There are also
51
- some more specific IRC channels noted below.
74
+ responses are typically very fast.
52
75
53
- IRC on Moznet
76
+ To get involved in the development of Rust itself, for anything about
77
+ contribution, or to find a mentor, [ #rust-internals] [ internals_irc ] is
78
+ the right channel.
54
79
80
+ There are also some more specific IRC channels
81
+ noted below.
82
+
83
+ ** Core channels** :
55
84
- [ #rust] [ rust_irc ] is for all things Rust;
56
85
- [ #rust-internals] [ internals_irc ] is for discussion of other Rust implementation topics;
57
86
- [ #rustc] [ rustc_irc ] is the home of the [ compiler team] [ compiler_team ] ;
58
87
- [ #rust-libs] [ libs_irc ] is the home of the [ libraries team] [ library_team ] ;
59
88
- [ #rust-tools] [ tools_irc ] is the home of the [ tools and infrastructure team] [ tool_team ] ;
60
89
- [ #rust-lang] [ lang_irc ] is the home of the [ language team] [ language_team ] ;
90
+ - [ #rust-community] [ community_irc ] is the home of the [ community team] [ community_team ] ;
91
+
92
+ ** Topical channels** :
61
93
- [ #cargo] [ cargo_irc ] is for discussion of Cargo, Rust's package manager;
62
94
- [ #servo] [ servo_irc ] is for discussion of Servo, the browser engine written in Rust;
63
95
- [ #rust-offtopic] [ offtopic_irc ] is for general chit-chat amongst Rustaceans;
@@ -67,31 +99,12 @@ IRC on Moznet
67
99
- [ #rust-gamedev] [ gamedev_irc ] is for people doing game development in Rust;
68
100
- [ #rust-bots] [ bots_irc ] notifcations about Rust from a selection of bots.
69
101
70
- [ Stack Overflow] [ stack_overflow ]
71
-
72
- Stack Overflow is a question and answer site for programmers.
73
- Searching for your problem might reveal someone who has asked it
74
- before.
75
-
76
- [ Rust Forum] [ forum ]
77
-
78
- Rust Programming Language Forum is for general discussion and broader questions.
79
-
80
- [ Twitter] [ twitter ]
81
-
82
- [ Rust Moderation Team] [ mod_team ]
83
-
84
- If you feel you have been or are being harassed or made uncomfortable
85
- by a community member, please [ contact] [ mod_team_email ] any of the
86
- Rust moderation team immediately. Whether you're a regular contributor
87
- or a newcomer, we care about making this community a safe place for
88
- you.
89
-
90
102
[ rust_irc ] : irc://moznet/rust
91
103
[ rustc_irc ] : irc://moznet/rustc
92
104
[ libs_irc ] : irc://moznet/rust-libs
93
105
[ tools_irc ] : irc://moznet/rust-tools
94
106
[ lang_irc ] : irc://moznet/rust-lang
107
+ [ community_irc ] : irc://moznet/rust-community
95
108
[ internals_irc ] : irc://moznet/rust-internals
96
109
[ gamedev_irc ] : irc://moznet/rust-gamedev
97
110
[ crypto_irc ] : irc://moznet/rust-crypto
@@ -101,49 +114,77 @@ you.
101
114
[ offtopic_irc ] : irc://moznet/rust-offtopic
102
115
[ servo_irc ] : irc://moznet/servo
103
116
[ bots_irc ] : irc://moznet/rust-bots
104
- [ stack_overflow ] : https://stackoverflow.com/questions/tagged/rust
105
- [ forum] : https://users.rust-lang.org/
106
- [ twitter ] : https://twitter.com/rustlang
107
- [ mod_team ] : https://www.rust-lang.org/team.html#Moderation
108
- [ mod_team_email ] : mailto:rust-mods@googlegroups.com
109
117
110
- ## User Groups
118
+ ### Discourse Forums
119
+
120
+ We have two forums for asynchronous discussion:
121
+
122
+ - The [ Users Forum] [ users_forum ] , a space for asking questions, posting code
123
+ snippets, talking about Rust projects, and so on.
111
124
112
- [ Rust User Groups] [ user_group ]
125
+ - The [ Internals Forum] [ internals_forum ] , a space dedicated to design and
126
+ implementation discussion about Rust itself (which includes Cargo, the
127
+ standard library, and other core bits of infrastructure).
113
128
114
- There are more than 50 Rust User Groups worldwide in over 20 countries
115
- with over 7,000 members. Rustaceans meet periodically in Rust User
116
- Groups. Its a great introduction to the community and a great way to
117
- learn and socialize with other people with a similar interest.
118
- Meetings are usually monthly and very informal. Meetings are open to
119
- everyone.
129
+ [ users_forum ] : https://users.rust-lang.org/
130
+ [ internals_forum ] : https://internals.rust-lang.org/
120
131
121
- [ Rust Calendar] [ calendar ]
132
+ ### Stack Overflow
133
+
134
+ [ Stack Overflow] [ stack_overflow ] is a question and answer site for programmers.
135
+ The Rust community is fairly active on the site, so searching for your problem
136
+ might reveal someone who has asked it before.
137
+
138
+ [ stack_overflow ] : https://stackoverflow.com/questions/tagged/rust
139
+
140
+ ## User Groups and Meetups
141
+
142
+ There are more than 50 [ Rust User Groups] [ user_group ] worldwide in over 20
143
+ countries totaling over 7,000 members. Rustaceans meet periodically in Rust User
144
+ Groups. Its a great introduction to the community and a great way to learn and
145
+ socialize with other people with a similar interest. Meetings are usually
146
+ monthly and very informal. Meetings are open to everyone.
147
+
148
+ There's a global [ calendar] [ calendar ] for keeping up with Rust events.
122
149
123
150
[ user_group ] : ./user_groups.html
124
151
[ calendar ] : https://www.google.com/calendar/embed?src=apd9vmbc22egenmtu5l6c5jbfc@group.calendar.google.com
125
152
126
- ## People
127
-
128
- [ Rust Teams] [ teams ]
129
-
130
- Rust has a community-driven development process where most decisions
131
- are made through consensus, under the stewardship of a core team. The
132
- [ Core Team] [ core_team ] is responsible for steering the design and
133
- development process, overseeing the introduction of new features, and
134
- ultimately making decisions for which there is no consensus (this
135
- happens rarely). The [ Language Design Team] [ language_team ] is
136
- responsible for design of new language features. The [ Library
137
- Team] [ library_team ] is responsible for the Rust standard library,
138
- rust-lang crates, and conventions. The [ Compiler Team] [ compiler_team ]
139
- is responsible for compiler internals and optimizations. The [ Tooling
140
- and Infrastructure Team] [ tool_team ] is responsible for support for
141
- Cargo, Multirust, and CI Infrastructure. The [ Community
142
- Team] [ community_team ] is responsible for coordinating events,
143
- outreach, commercial users, teaching materials, and exposure. The
144
- [ Moderation Team] [ mod_team ] is responsible for helping to uphold the
153
+ ## The teams
154
+
155
+ Rust has a community-driven development process where most decisions are made
156
+ through open discussion and consensus, under the stewardship of various
157
+ [ teams] [ teams ] :
158
+
159
+ * The [ Core Team] [ core_team ] is responsible for steering the design and
160
+ development process, overseeing the introduction of new features, and ultimately
161
+ making decisions for which there is no consensus (this happens rarely).
162
+
163
+ * The [ Language Design Team] [ language_team ] is responsible for design of new
164
+ language features.
165
+
166
+ * The [ Library Team] [ library_team ] is responsible for the Rust standard
167
+ library, rust-lang crates, and conventions.
168
+
169
+ * The [ Compiler Team] [ compiler_team ] is responsible for compiler internals and
170
+ optimizations.
171
+
172
+ * The [ Tooling and Infrastructure Team] [ tool_team ] is responsible for official
173
+ tools like Cargo, multirust, rustfmt, as well as the CI Infrastructure for the
174
+ project.
175
+
176
+ * The [ Community Team] [ community_team ] is responsible for coordinating events,
177
+ outreach, commercial users, teaching materials, and exposure.
178
+
179
+ * The [ Moderation Team] [ mod_team ] is responsible for helping to uphold the
145
180
[ code of conduct] [ coc ] .
146
181
182
+ In addition to the official team rosters, most teams also have a larger set
183
+ of reviewers who are knowledgeable about the area and can sign off on code.
184
+
185
+ If you're interested in getting involved in one of these teams, feel free to
186
+ reach out to the team leader, who can help get you started.
187
+
147
188
[ teams ] : https://www.rust-lang.org/team.html
148
189
[ core_team ] : https://www.rust-lang.org/team.html#Core
149
190
[ language_team ] : https://www.rust-lang.org/team.html#Language-design
@@ -155,35 +196,29 @@ outreach, commercial users, teaching materials, and exposure. The
155
196
156
197
## Rust Development
157
198
158
- [ How to contribute] [ contribute ]
159
-
160
- According to [ CodeTriage] [ codetriage ] , the Rust
161
- language has the most contributors of any programming language. If you
162
- want to join in the fun but aren't sure what to work on, please take
163
- a look at [ how to contribute] [ contribute ] .
164
-
165
- [ Rust Internals Forum] [ internals ]
166
-
167
- This is the main forum for discussing the design and implementation of
168
- Rust.
169
-
170
- [ Github] [ github ]
171
-
172
- This is where all the source code resides.
199
+ Rust has had over [ 1,200 different contributors] [ ] authors] , a number that grows
200
+ every single week. We'd love for you to join that list! If you aren't sure what
201
+ to work on or how to get started, take a look at our
202
+ [ how to contribute] [ contribute ] page.
173
203
174
- [ RFCs] [ rfcs ]
204
+ As mentioned above, the [ Rust Internals Forum] [ internals_forum ] is dedicated to
205
+ discussing the design and implementation of Rust. A lot of discussion also
206
+ happens on Github:
175
207
176
- The RFC (request for comments) process is the main pathway through
177
- which the Rust community and the core team reach consensus on new
178
- features entering the language and standard libraries.
208
+ - The [ main repository ] [ github ] and [ issue tracker ] [ issue_tracking ] are the
209
+ front lines of the implementation work. Our reviewers strive to be friendly
210
+ and to help mentor newcomers, so don't hesitate to open a pull request!
179
211
180
- [ Team Reports] [ team_reports ]
212
+ - The [ RFC repo] [ rfcs ] tracks our Request for Comment process, the main pathway
213
+ through which the Rust community and the teams reach consensus on new
214
+ features proposed for the language and official libraries and tools.
181
215
182
- [ Issue Tracking] [ issue_tracking ]
216
+ Roughly weekly, the Rust teams produce [ team reports] [ team_reports ] tracking
217
+ team business, including the progression of proposals through the RFC and
218
+ implementation process.
183
219
220
+ [ authors ] : https://github.com/rust-lang/rust/blob/master/AUTHORS.txt
184
221
[ contribute ] : ./how_to_contribute.html
185
- [ internals ] : https://internals.rust-lang.org/
186
- [ codetriage ] : http://www.codetriage.com
187
222
[ github ] : https://github.com/rust-lang/rust
188
223
[ rfcs ] : https://github.com/rust-lang/rfcs
189
224
[ team_reports ] : https://github.com/rust-lang/subteams
0 commit comments