Skip to content

Commit 4219e04

Browse files
authored
Added some explicit links to the tagging syntax one uses to ping the ICE breakers. (#543)
(Yes, the "#join" link *also* goes to the same page (but a different section). But as a reader, I am not going to realize that.)
1 parent cef94c6 commit 4219e04

File tree

2 files changed

+15
-3
lines changed

2 files changed

+15
-3
lines changed

posts/inside-rust/2019-10-22-LLVM-ICE-breakers.md

Lines changed: 12 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,14 +14,19 @@ At its heart, the LLVM ICE-breaker group is just a list of people who would like
1414

1515
[open a PR]: https://rustc-dev-guide.rust-lang.org/ice-breaker/about.html#join
1616

17-
There are a few other things associated with the group too, however. For example, we've got a [guide] that offers some tips for how to fix LLVM-related bugs and may help you get started (particularly if you're not that familiar with rustc).
17+
There are a few other things associated with the group too, however. For example, we've got a [guide][llvm guide] that offers some tips for how to fix LLVM-related bugs and may help you get started (particularly if you're not that familiar with rustc).
1818

19-
[guide]: https://rustc-dev-guide.rust-lang.org/ice-breaker/llvm.html
19+
[llvm guide]: https://rustc-dev-guide.rust-lang.org/ice-breaker/llvm.html
2020

2121
### What kind of bugs are we talking about?
2222

2323
The goal is to identify "self-contained" bugs that are unlikely to require large-scale compiler refactorings or to get entangled in other big projects.
2424

25+
As Rust developers triage bugs and tag them for the ICE-breakers,
26+
they will [ping][tag syntax] the group on Github.
27+
28+
[tag syntax]: https://rustc-dev-guide.rust-lang.org/ice-breaker/about.html#tagging-an-issue-for-an-ice-breaker-group
29+
2530
### Who should join?
2631

2732
This group is a great fit for anyone who is familiar with LLVM and who would like to learn more about Rust or to get more involved in the Rust project. Even if you don't have time to open PRs against rustc, there are many other ways to help:
@@ -45,6 +50,11 @@ But of course we also hope that these ICE-breaker groups can help people to get
4550

4651
I certainly hope so! As I mentioned before, this is an experiment, but presuming that it works out well we fully intend to create more ICE-breaker groups.
4752

53+
The current list of ICE-breaker groups is documented in the
54+
[rustc development guide][rustc dev guide]
55+
56+
[rustc dev guide]: https://rustc-dev-guide.rust-lang.org/ice-breaker/about.html
57+
4858
### So how do I sign up again?
4959

5060
Easy! Just [open a PR]!

posts/inside-rust/2020-02-06-Cleanup-Crew-ICE-breakers.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,11 +33,13 @@ This kind of cleanup is invaluable in getting bugs fixed.
3333
It can be done by anybody who knows Rust, without any particularly deep
3434
knowledge of the compiler. If you want to be part of it and be notified
3535
about things to do, just [add yourself to the list][instructions here]! When we come across a suitable
36-
bug, we'll write a message that `@`-mentions every Github user on that
36+
bug, we'll [write a message][tag syntax] that `@`-mentions every Github user on that
3737
team. If you have some time, maybe you can provide some useful
3838
information.
3939

4040
[instructions here]: https://rustc-dev-guide.rust-lang.org/ice-breaker/about.html#join
4141

42+
[tag syntax]: https://rustc-dev-guide.rust-lang.org/ice-breaker/about.html#tagging-an-issue-for-an-ice-breaker-group
43+
4244
You can find more information about the group on it's [rustc-dev-guide
4345
section](https://rustc-dev-guide.rust-lang.org/ice-breaker/cleanup-crew.html).

0 commit comments

Comments
 (0)