Finding Contribution Opportunities in Rust

`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 it's easy to pick up work without a large time commitment: - [Move UI tests to subdirectories](https://github.com/rust-lang/rust/issues/73494) If you find more recurring work, please feel free to add it here! ### Clippy issues The [Clippy] project has spent a long time making its contribution process as friendly to newcomers as possible. Consider working on it first to get familiar with the process and the compiler internals. See [the Clippy contribution guide][clippy-contributing] for instructions on getting started. ### Diagnostic issues Many diagnostic issues are self-contained and don't need detailed background knowledge of the compiler. You can see a list of diagnostic issues [here][diagnostic-issues]. ### Picking up abandoned pull requests Sometimes, contributors send a pull request, but later find out that they don't have enough time to work on it, or they simply are not interested in it anymore. Such PRs are often eventually closed and they receive the `S-inactive` label. You could try to examine some of these PRs and pick up the work. You can find the list of such PRs [here][abandoned-prs]. If the PR has been implemented in some other way in the meantime, the `S-inactive` label should be removed from it. If not, and it seems that there is still interest in the change,

This section provides guidance on identifying areas within the Rust project where contributions are needed, especially for beginners. It suggests looking at easy or mentored issues, recurring work coordinated through "Tracking issues," Clippy issues (known for a friendly contribution process), diagnostic issues, and picking up abandoned pull requests. Links to relevant issue searches and contribution guides are provided.