And even in the compiler itself there's plenty of work to be done that doesn't even come close to the LLVM and that have mentoring instructions[1]. The point of

And even in the compiler itself there's plenty of work to be done that doesn't even come close to the LLVM and that have mentoring instructions[1]. The point of entry that I personally found successful when starting to contribute was modifying and expanding the compiler's diagnostic output[2], as it gives you something to grep for and work it out from there. Also, be aware that beyond just asking questions in the issue tracker and on the official #rust IRC channel, each Working Group has a room on gitter[3] where there are people more than eager to help any newcomers. My advice would be to look out for anything that you might find interesting, ask for help whenever you get stuck and just read the code. There's plenty of opportunities to make an impact[4] :) [1]: https://github.com/rust-lang/rust/labels/E-mentor https://github.com/rust-lang/rust/labels/E-mentor [2]: https://github.com/rust-lang/rust/issues?utf8=%E2%9C%93&q=is%3Aopen%20label%3AE-mentor%20label%3AA-diagnostics https://github.com/rust-lang/rust/issues?utf8=%E2%9C%93&q=is... [3]: https://gitter.im/rust-impl-period/ https://gitter.im/rust-impl-period/ [4]: https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.m...