How to start contributing

Thank you for your interest in contributing to Rust! There are many ways to contribute, and we appreciate all of them. This document describes how you can get in touch with other Rust contributors and start contributing to Rust projects.

As a reminder, all contributors are expected to follow our Code of Conduct.

Asking Questions

First, if you have any questions regarding your potential contributions, you can ask other contributors on the following places:

• Rust Zulip server is the primary communication space for most Rust teams and contributors. It is also a great place to observe on what is going on.
  • You can check out e.g. the compiler team (t-compiler) Zulip "channel", or t-compiler/help.
• internals.rust-lang.org (IRLO) is a forum for discussing development of Rust.

See also the list of teams and working groups and the Community page on the official website for more resources.

Please ask questions! A lot of people report feeling that they are "wasting expert time", but we do not feel that 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 :)

Tip: If you're not a native English speaker and feel unsure about writing, try using a translator to help. But avoid using LLM tools that generate long, complex words. In daily teamwork, simple and clear words are best for easy understanding. Even small typos or grammar mistakes can make you seem more human, and people connect better with humans.

See also our LLM policy.

If you want to contribute substantial changes, we suggest first contacting the team relevant to these changes. Each teams has their own preferred workflow, please follow the recommended path in order to have a prior discussion and team buy-in:

• Compiler team: a Major Change Proposal (MCP) or a Request For Comment (RFC) (read more here)
• Rustdoc team: Contact the team on their Zulip channel
• Library team: open an API Change proposal (ACP) on GitHub or reach out the team on Zulip (read more here)
• Bootstrap team: ask in the team Zulip channel

In case of doubt, feel free to ask on Zulip.

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 team members get a lot of pings in a day.

How to start contributing?

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 is a (non-exhaustive) list of rust-lang projects that could serve as starting places for you to contribute. Some of them have contributor guides and issues that are marked as needing help or being good first issues.

If you want to get inspired, check all the rust-lang repositories!

Etiquette

We know that starting contributing in a FOSS¹ project could be confusing at times and we want both contributors and reviewers have the best possible experience when collaborating in our project.

To achieve this goal, we want to build trust and respect of each other's time and efforts. Our recommendation is to follow these simple guidelines:

• Start small. A big ball of code as first contribution does not help to build trust
• The work you submit is your own, meaning that you fully understand every part of it
• You take care of checking in detail your work before submitting it - ask questions or signal us (with inline comments or todo!()) the parts you're unsure about
• If you want to fix an issue but have doubts about the design, you're welcome to join our Zulip server and ask for tips
• Please respect the reviewers' time: allow some days between reviews, only ask for reviews when your code compiles and tests pass, or give an explanation for why you are asking for a review at that stage (you can keep them in draft state until they're ready for review)
• Try to keep comments concise, don't worry about a perfect written communication. Strive for clarity and being to the point
• Please use English to communicate (including e.g. commit messages) for consistency with the communication in our project (English is the accepted common language in our project). The grammar or prose does not need to be perfect at all!

See also our LLM usage policy.

Different kinds of contributions

There are various ways in which you can contribute to Rust projects:

• Writing code is the most obvious one. However, it does not have to be only in Rust! Even though most of our projects are of course written in Rust, we also use other technologies. For example, you can help improve our GitHub CI workflows, automation Python scripts or contribute to web frontends with HTML/CSS/JS (e.g. Rustdoc or Benchmark suite website). Play to your strengths!

• Improving documentation is possibly one of the easiest starting points for contributions. Did you find a typo, something that was unclear, or do you miss some useful information on this page, elsewhere in the Forge or in some other Rust (user-facing) documentation? Great, then send a pull request and you'll become a contributor! :)

  Please notice that at this time we don't accept typography/spellcheck fixes to internal documentation (usually not worth the churn or the review time) or in our testsuite (they could inadvertently cause code regressions)

• Improving tests is also very valuable, as there is never enough of them. This can include also documenting existing tests or writing tests for already fixed issues that lack a proper test.

• You can also help with improving issue trackers of our repositories, by helping with triaging issues or by reproducing old issues to find out whether they are still valid or not.

• Or, if you like programming language discussions, you could participate in our RFC process.

• You can also answer questions to help other Rust users, on users.rust-lang.org (URLO), or on StackOverflow.