@@ -6,50 +6,49 @@ they are not currently an active part of the decision-making process.
6
6
Unfortunately, whenever a new person is added or someone goes into alumni
7
7
status, there are a number of disparate places that need to be updated. This
8
8
page aims to document that list. If you have any questions, or need someone with
9
- more privileges to make a change for you, a good place to ask is #rust- infra (or
10
- possibly #rust-internals) .
9
+ more privileges to make a change for you, a good place to ask is ` # infra` on
10
+ Discord .
11
11
12
- ### R+ rights
12
+ ### Team repo
13
13
14
- If just giving r+ rights, the following places need to be modified:
14
+ Membership of teams is primarily driven by the config files in the
15
+ [ rust-lang/team repo] [ team repo ] . Several systems use the team repo data to
16
+ control access:
15
17
16
- - the [ homu template on rust-central-station] [ homu ]
18
+ - the [ team website]
19
+ - bors r+ rights
20
+ - rfcbot interaction
21
+ - Mailgun email lists
22
+
23
+ Team membership is duplicated in a few other places listed below, but the
24
+ long-term goal is to centralize on the team repo.
17
25
18
26
### Full team membership
19
27
20
28
To make a full team member, the following places need to be modified:
21
29
22
- - the [ team roster page ] [ team-roster ]
30
+ - the [ team repo ]
23
31
- the [ rust-lang/TEAM] [ gh-team ] and (in some cases)
24
32
[ rust-lang-nursery/TEAM] [ gh-nursery-team ] teams on github must be updated
25
- - rfcbot has a separate list of people on a team that is maintained in a
26
- configuration file
27
- - [ here is an example commit that was adding Centril to the lang
28
- team] [ rfcbot-example ]
29
- - the easydns service has an e-mail alias (` compiler-team@rust-lang.org ` ) that
30
- needs to be updated
31
- - best here is to ask around in #rust-infra
32
33
- the
33
34
[ internals discussion board has per-team groups] ( https://internals.rust-lang.org/admin/groups/custom )
34
- - the list of reviewers highfive uses is set in [ nrc /highfive] [ highfive ]
35
+ - the list of reviewers highfive uses is set in [ rust-lang /highfive] [ highfive ]
35
36
- the configs are set per-repo; some teams are listed in ` rust.json ` , whereas
36
37
those that span multiple repos are set in ` _global.json `
37
38
38
39
### Team member departure
39
40
40
41
Remove the team member from any and all places:
41
42
42
- - [ highfive] [ ]
43
- - [ reviewers list] [ homu ]
44
- - rfcbot ([ example] [ rfcbot-example ] )
43
+ - [ highfive]
45
44
- 1password
46
45
- The [ GitHub team] [ gh-team ] , [ GitHub nursery team] [ gh-nursery-team ]
47
- - email aliases (as above)
48
- - [ team roster page ] [ team-roster ]
46
+ - [ team repo ]
47
+ - [ toolstate notifications ]
49
48
50
- [ homu ] : https://github.com/alexcrichton/rust-central-station/blob/master/homu.toml.template
51
- [ team-roster ] : https://github.com/rust-lang/rust-www/blob/master/_data/team.yml
52
49
[ gh-team ] : https://github.com/orgs/rust-lang/teams
53
50
[ gh-nursery-team ] : https://github.com/orgs/rust-lang-nursery/teams
54
- [ highfive ] : https://github.com/nrc/highfive/tree/master/highfive/configs
55
- [ rfcbot-example ] : https://github.com/anp/rfcbot-rs/commit/cd54241359cf65742ed5a0fba58ea5114de06f2b#diff-100115fcbdda685c37ba8f73727b0987
51
+ [ highfive ] : https://github.com/rust-lang/highfive/tree/master/highfive/configs
52
+ [ team repo ] : https://github.com/rust-lang/team/tree/master/teams
53
+ [ team website ] : https://www.rust-lang.org/governance
54
+ [ toolstate notifications ] : https://github.com/rust-lang/rust/blob/master/src/tools/publish_toolstate.py
0 commit comments