@@ -21,8 +21,12 @@ chapter on how to build and run the compiler](./building/how-to-build-and-run.md
21
21
22
22
## Asking Questions
23
23
24
- If you have questions, please make a post on [ internals.rust-lang.org] [ internals ] or
25
- hop on the [ Rust Discord server] [ rust-discord ] or [ Rust Zulip server] [ rust-zulip ] .
24
+ If you have questions, please make a post on the [ Rust Zulip server] [ rust-zulip ] or
25
+ [ internals.rust-lang.org] [ internals ] . If you are contributing to Rustup, be aware they are not on
26
+ Zulip - you can ask questions in ` #wg-rustup ` [ on Discord] [ rust-discord ] .
27
+ See [ the Community page] [ community ] on the official website for more resources.
28
+
29
+ [ community ] : https://www.rust-lang.org/community
26
30
27
31
As a reminder, all contributors are expected to follow our [ Code of Conduct] [ coc ] .
28
32
@@ -48,6 +52,12 @@ compiler, [consult this "experts map"][map].
48
52
It's not perfectly complete, though, so please also feel free to ask questions
49
53
even if you can't figure out who to ping.
50
54
55
+ Another way to find experts for a given part of the compiler is to see who has made recent commits.
56
+ For example, to find people who have recently worked on name resolution since the 1.68.2 release,
57
+ you could run ` git shortlog -n 1.68.2.. compiler/rustc_resolve/ ` . Ignore any commits starting with
58
+ "Rollup merge" or commits by ` @bors ` (see [ CI contribution prodcedures] ( ./contributing.md#ci ) for
59
+ more information about these commits).
60
+
51
61
[ map ] : https://github.com/rust-lang/compiler-team/blob/master/content/experts/map.toml
52
62
53
63
### Etiquette
0 commit comments