Skip to content

Commit 65a45a8

Browse files
authored
Merge pull request #46 from davidtwco/rust-teams-procedure-update
Mention updating rust-lang/team
2 parents 96b5976 + 01ed7ea commit 65a45a8

File tree

2 files changed

+9
-1
lines changed

2 files changed

+9
-1
lines changed

procedures/form-new-working-group.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -98,7 +98,14 @@ The basic steps to setup a working group are as follows:
9898
working groups start out with relatively little structure but
9999
define it early on.
100100
- **Add an entry to the compiler team calendar:** If you have a regular meeting,
101-
ping somebody on `#t-compiler`[cp] to add an entry to the compiler team calendar.
101+
ping somebody on `#t-compiler`[cp] to add an entry to the compiler team calendar.
102+
- Add a file to the [`rust-lang/team`][team_repo] repository. Only working group leads should be
103+
listed and a link to their directory in this repository should also be included. See the
104+
traits working group [as an example][team_repo_example]. This will ensure that the working groups
105+
are listed on the website.
106+
107+
[team_repo]: https://github.com/rust-lang/team
108+
[team_repo_example]: https://github.com/rust-lang/team/blob/master/teams/wg-traits.toml
102109

103110
[README]: ../README.md
104111
[template]: ../working-groups/.template

working-groups/mir-opt/README.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,7 @@ writing MIR optimizations.
88
- **Meeting Notes:** [All](NOTES.md)
99

1010
[status]: https://img.shields.io/badge/status-active-brightgreen.svg?style=for-the-badge
11+
[oli-obk]: https://github.com/oli-obk
1112

1213
## What is the goal of this working group?
1314
This working group aims to accomplish the following:

0 commit comments

Comments
 (0)