@@ -5,14 +5,14 @@ group discusison, read on! This page has all the details.
5
5
6
6
## TL;DR
7
7
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
+
16
16
You don't have to have a lot of details to start: just a few sentences
17
17
is enough. But, especially for technical design discussions, we will
18
18
typically expect that some form of more detailed overview be made
@@ -32,7 +32,7 @@ suitable for the steering meeting:
32
32
to be able to explain the work they did and request review.
33
33
34
34
Steering meetings are also a good place to discuss other kinds of proposals:
35
-
35
+
36
36
- A proposal to move some part of the compiler into an out-of-tree crate.
37
37
- A proposal to start a new working group.
38
38
@@ -97,5 +97,5 @@ meetings are not mandatory. If there aren't enough proposals in some
97
97
particular iteration, then we can just opt to not discuss anything.
98
98
99
99
[ 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