@@ -5,14 +5,14 @@ group discusison, read on! This page has all the details.
55
66## TL;DR
77
8- In short, all you have to do is
9-
10- * [ open an issue on the compiler-team repository] [ ct issues ]
11- * use the template for meeting proposals
12- * you only need a few sentences to start, but by the time the meeting
13- takes place we typically expect a more detailed writeup, e.g.
14- using [ this template] (
15-
8+ In short, all you have to do is
9+
10+ - [ open an issue on the compiler-team repository] [ ct issues ]
11+ - use the template for meeting proposals
12+ - you only need a few sentences to start, but by the time the meeting
13+ takes place we typically expect a more detailed writeup, e.g.
14+ using [ this template] [ template ]
15+
1616You don't have to have a lot of details to start: just a few sentences
1717is enough. But, especially for technical design discussions, we will
1818typically expect that some form of more detailed overview be made
@@ -32,7 +32,7 @@ suitable for the steering meeting:
3232 to be able to explain the work they did and request review.
3333
3434Steering meetings are also a good place to discuss other kinds of proposals:
35-
35+
3636- A proposal to move some part of the compiler into an out-of-tree crate.
3737- A proposal to start a new working group.
3838
@@ -97,5 +97,5 @@ meetings are not mandatory. If there aren't enough proposals in some
9797particular iteration, then we can just opt to not discuss anything.
9898
9999[ ct issues ] : https://github.com/rust-lang/compiler-team/issues
100- [ template ] : XXX
101-
100+ [ template ] : https://github.com/rust-lang/compiler-team/blob/master/templates/steering-meeting-proposal.md
101+ [ minutes ] : https://github.com/rust-lang/compiler-team/tree/master/content/minutes
0 commit comments