Getting Started with Rust Contribution

# Getting Started Thank you for your interest in contributing to Rust! There are many ways to contribute, and we appreciate all of them.  If this is your first time contributing, the [walkthrough] chapter can give you a good example of how a typical contribution would go. This documentation is _not_ intended to be comprehensive; it is meant to be a quick guide for the most useful things. For more information, [see this chapter on how to build and run the compiler](./building/how-to-build-and-run.md). ## Asking Questions If you have questions, please make a post on the [Rust Zulip server][rust-zulip] or [internals.rust-lang.org][internals]. If you are contributing to Rustup, be aware they are not on Zulip - you can ask questions in `#wg-rustup` [on Discord][rust-discord]. See the [list of teams and working groups][governance] and [the Community page][community] on the official website for more resources. As a reminder, all contributors are expected to follow our [Code of Conduct][coc]. The compiler team (or `t-compiler`) usually hangs out in Zulip [in this "stream"][z]; it will be easiest to get questions answered there. **Please ask questions!** A lot of people report feeling that they are "wasting expert time", but nobody on `t-compiler` feels this way. Contributors are important to us. Also, if you feel comfortable, prefer public topics, as this means others can see the questions and answers, and perhaps even integrate them back into this guide :) ### Experts Not all `t-compiler` members are experts on all parts of `rustc`; it's a pretty large project. To find out who could have some expertise on different parts of the compiler, [consult triagebot assign groups][map]. The sections that start with `[assign*` in `triagebot.toml` file. But also, feel free to ask questions even if you can't figure out who to ping. Another way to find experts for a given part of the compiler is to see who has made recent commits. For example, to find people who have recently worked on name resolution since the 1.68.2 release, you could run `git shortlog -n 1.68.2.. compiler/rustc_resolve/`. Ignore any commits starting with "Rollup merge" or commits by `@bors` (see [CI contribution procedures](./contributing.md#ci) for more information about these commits). ### Etiquette We do ask that you be mindful to include as much useful information as you can in your question, but we recognize this can be hard if you are unfamiliar with contributing to Rust. Just pinging someone without providing any context can be a bit annoying and just create noise, so we ask that you be mindful of the fact that the `t-compiler` folks get a lot of pings in a day. ## What should I work on? The Rust project is quite large and it can be difficult to know which parts of the project need help, or are a good starting place for beginners. Here are some suggested starting places. ### Easy or mentored issues If you're looking for somewhere to start, check out the following [issue search][help-wanted-search]. See the [Triage] for an explanation of these labels. You can also try filtering the search to areas you're interested in. For example: - `repo:rust-lang/rust-clippy` will only show clippy issues - `label:T-compiler` will only show issues related to the compiler - `label:A-diagnostics` will only show diagnostic issues Not all important or beginner work has issue labels. See below for how to find work that isn't labelled. ### Recurring work Some work is too large to be done by a single person. In this case, it's common to have "Tracking issues" to co-ordinate the work between contributors. Here are some example tracking issues where

This section provides a guide for new contributors to the Rust project, including how to ask questions on the Rust Zulip server or internals forum, adhering to the Code of Conduct, and finding suitable tasks to work on, such as easy or mentored issues labeled as 'help wanted'. It also suggests consulting triagebot assign groups to find experts and encourages providing sufficient context when asking questions.