@@ -9,31 +9,37 @@ are setup so that anyone can join them if they want.
9
9
If you'd like to create a notification group, here are the steps.
10
10
First, you want to get approval from the compiler team:
11
11
12
- * Propose the group by preparing a [ Major Change Proposal] [ MCP ] . If
12
+ * Propose the group by preparing a [ Major Change Proposal] [ MCP ] . If
13
13
your group is not analogous to some existing group, it is probably
14
14
a good idea to ping compiler team leads before-hand or as part of
15
15
the MCP.
16
16
* The MCP should specify what GitHub label will be associated with the
17
17
notification group. Often this is an existing label, such as
18
18
` O-Windows ` .
19
-
19
+
20
20
Once the MCP is accepted, here are the steps to actually create the group.
21
- In some cases we include an example PR from some other group.
21
+ In some cases we include an example PR from some other group.
22
22
23
- * File a tracking issue in the rust-lang/compiler-team repository to collect
23
+ * File a tracking issue in the [ rust-lang/compiler-team] repository to collect
24
24
your progress.
25
- * Create a PR against the rust-lang/team repository adding the notification
25
+ * Create a PR against the [ rust-lang/team] repository adding the notification
26
26
group. [ Example PR.] ( https://github.com/rust-lang/team/pull/347 )
27
- * Configure the rust-lang/rust repository to accept triagebot commands
27
+ * Configure the [ rust-lang/rust] repository to accept triagebot commands
28
28
for this group. [ Example PR.] ( https://github.com/rust-lang/rust/pull/72706 )
29
29
* Create a PR for the rustc-dev-guide amending [ the notification group
30
30
section] ( https://rustc-dev-guide.rust-lang.org/notification-groups/about.html )
31
31
to mention your group.
32
- * Create a sample PR for the rust-lang/team repository showing how one can add
33
- oneself. This will be referenced by your blog post to show people how to
32
+ * Create a sample PR for the [ rust-lang/team] repository showing how one can add
33
+ oneself. This will be referenced by your blog post to show people how to
34
34
join. [ Example PR.] ( https://github.com/rust-lang/team/pull/140 )
35
+ * Create a Zulip stream for the notification group. If you don't have the permission
36
+ to do, you can ask on [ #t-compiler/wg-meta] .
35
37
* Write an announcement blog post for Inside Rust and open a PR against
36
38
[ blog.rust-lang.org] ( https://github.com/rust-lang/blog.rust-lang.org ) .
37
39
[ Example PR.] ( https://github.com/rust-lang/blog.rust-lang.org/pull/615 )
38
40
41
+ [ rust-lang/compiler-team ] : https://github.com/rust-lang/compiler-team
42
+ [ rust-lang/team ] : https://github.com/rust-lang/team
43
+ [ rust-lang/rust ] : https://github.com/rust-lang/rust
44
+ [ #t-compiler/wg-meta ] : https://rust-lang.zulipchat.com/#narrow/stream/185694-t-compiler.2Fwg-meta
39
45
[ MCP ] : ./mcp.md
0 commit comments