The Rust Community

The Rust programming language has many qualities, but Rust’s greatest
strength is the community of people who come together to make working
in Rust a rewarding experience.

We are committed to providing a friendly, safe and welcoming
environment for all, regardless of gender, sexual orientation,
disability, ethnicity, religion, or similar personal
characteristic. Our code of conduct sets the standards for
behavior in all official Rust forums.

If you feel you have been or are
being harassed or made uncomfortable by a community member, please
contact any of the Rust Moderation Team
immediately. Whether you are a regular contributor or a newcomer, we
care about making the community a safe space for you.

Getting Started

The most important community resources for those new to Rust are:

#rust-beginners, an IRC channel that
loves answering questions at any depth.

You may also find help on the question and answer site, Stack Overflow.

News

This Week in Rust collects the latest news, upcoming events
and a week-by-week account of changes in the Rust language and
libraries. The Rust Blog is where the Rust team makes
announcements about major developments. And nearly everything happening in
Rust is discussed on the unofficial subreddit, /r/rust.

We also have a Twitter account.
If you can’t read English, You can also follow our Weibo for Chinese.

Discussion Forums

The Users Forum, a space for asking questions, posting code
snippets, talking about Rust projects, and so on.

The Internals Forum, a space dedicated to design and
implementation discussion about Rust itself (which includes Cargo, the
standard library, and other core bits of infrastructure).

YouTube Channel

Rust has a YouTube channel where presentations
given at user groups and conferences by members of the Rust community
are uploaded.

User Groups and Meetups

There are more than 90 Rust User Groups worldwide in
over 35 countries. Rustaceans meet periodically in Rust User Groups.
Its a great introduction to the community and a great way to learn and
socialize with other people with a similar interest. Meetings are
usually held monthly and very informal. Meetings are open to everyone.

The Rust Team

Rust has a community-driven development process where most decisions are made
through open discussion and consensus, under the stewardship of various
teams:

The Core Team is responsible for steering the design and
development process, overseeing the introduction of new features, and ultimately
making decisions for which there is no consensus (this happens rarely).

The Language Team is responsible for the
design of new language features.

The Library Team is responsible for the Rust standard
library, rust-lang crates, and conventions.

The Compiler Team is responsible for compiler internals and
optimizations.

The Dev tools team is responsible for setting the overall
direction of tools for working with Rust code.

The Cargo team is responsible for the design and implementation of Cargo.

The Infrastructure Team is responsible for infrastructure that supports
the project itself: CI, release generation, bots, and metrics.

The Community Team is responsible for coordinating events,
outreach, commercial users, teaching materials, and exposure. They can also
direct inquiries to the correct parties when its not clear who to contact
about something Rusty.

In addition to the official team rosters, most teams also have a larger set
of reviewers who are knowledgeable about the area and can sign off on
code. If you’re interested in getting involved in one of these teams,
feel free to reach out to the team leader or any other member, who can
help get you started.

Rust Development

As mentioned above, the Rust Internals Forum is dedicated to
discussing the design and implementation of Rust. A lot of discussion also
happens on GitHub:

The main repository and issue tracker are the
front lines of the implementation work. Our reviewers strive to be friendly
and to help mentor newcomers, so don’t hesitate to open a pull request!

The RFC repo tracks our Request for Comment process, the main pathway
through which the Rust community and the teams reach consensus on new
features proposed for the language and official libraries and tools.