Change:
The , writes: Perhaps it could be a little better. What throws me off in this last sentence, is the term . I'm just a total newbie and just getting to know the terms in this language, so there's no surprise that I can't explain why I am sent one place or another for documentation. So, this is more of a question to those familiar with the constellation of terms, repositories, web sites, and so on. Could this reference explain why it refers to and not anything else. I want to contribute to documentation of what seems to be a core macro (). So, I'm not sure that reading the "Guide to Rustc Development" would be the correct thing to do (even thought I will surely personally read it at some point). The readme of this repository writes: So, in the file, I expect to be directed to instructions on contributing to all or any of the compiler, standard library and documentation. But I am directed to what seems to be — at least by title alone (I haven't read into it, yet) — solely about contributing to the rust compiler. Any suggestion regarding how to improve this — I have the intention of implementing myself. By the way, I am streaming my contribution to rust live at <!-- TRIAGEBOTSTART --<!-- TRIAGEBOTASSIGNSTART --<!-- TRIAGEBOTASSIGNDATASTARTTRIAGEBOTASSIGNDATAEND --<!-- TRIAGEBOTASSIGNEND --<!-- TRIAGEBOTEND --
I personally think should still redirect to rustc-dev-guide but I think the guide could be improved. IIRC the guide was not updated regarding the split of , and . The guide talks more about contributing to the rust compiler, but personally I think contributing to the library should be straightforward besides not knowing how to build a custom toolchain which isn't always necessary. I believe you can just create a pull request for this if you see fit to close the issue (so it doesn't hang around and become lost).
Yeah, I've very recently run into a similar issue; based on my research, it seems the original content of now lives at https://rustc-dev- which seems like a better entry point. It seems the contribution/developer docs are currently mid-transition from one approach to a new one. Related:
cc
Having just discovered that the GitHub "first issue" pop-up also links to this document, I just went ahead & created PR which links to the chapter of the dev guide that now holds the content that was previously in . <details! </detailsUntil the "Getting Started" chapter gets re-written to be less -specific, linking to it rather than "Contributing to Rust" chapter seems unnecessarily unwelcoming to new contributors, particularly those who were specifically directed there while creating an issue. (Of course, if the "first issue" link can be customised that's another option for the future.)
claim
Thank you.

Discussion:
# Contributing to Rust <del> Thank you for your interest in contributing to Rust! </del> <ins> Thank you for your interest in contributing to Rust! There are many ways to contribute and we appreciate all of them. </ins> <del> To get started, read the [Contributing to Rust] chapter of the [rustc-dev-guide]. </del> <ins> Documentation for contributing to Rust is located in the [Guide to Rustc Development](https://rustc-dev-guide.rust-lang.org/), commonly known as the [rustc-dev-guide]. Despite the name, this guide documents not just how to develop rustc (the Rust compiler), but also how to contribute to any part of the Rust project. To get started with contributing, please read the [Contributing to Rust] chapter of the guide. That chapter explains how to get your development environment set up and how to get help. ## About the [rustc-dev-guide] The [rustc-dev-guide] is meant to help document how rustc –the Rust compiler– works, as well as to help new contributors get involved in rustc development. It is recommend to read and understand the [rustc-dev-guide] before making a contribution. This guide talks about the different bots in the Rust ecosystem, the Rust development tools, bootstrapping, the compiler architecture, source code representation, and more. ## [Getting help](https://rustc-dev-guide.rust-lang.org/getting-started.html#asking-questions) There are many ways you can get help when you're stuck. Rust has many platforms for this: [internals], [rust-zulip], and [rust-discord]. It is recommended to ask for help on the [rust-zulip], but any of these platforms are a great way to seek help and even find a mentor! You can learn more about asking questions and getting help in the [Asking Questions](https://rustc-dev-guide.rust-lang.org/getting-started.html#asking-questions) chapter of the [rustc-dev-guide]. </ins> ## Bug reports

[rustc-dev-guide]: https://rustc-dev-guide.rust-lang.org/ [contributing-bug-reports]: https://rustc-dev-guide.rust-lang.org/contributing.html#bug-reports [issue template]: https://github.com/rust-lang/rust/issues/new/choose <ins> [internals]: https://internals.rust-lang.org [rust-discord]: http://discord.gg/rust-lang [rust-zulip]: https://rust-lang.zulipchat.com </ins>