@@ -6,50 +6,49 @@ they are not currently an active part of the decision-making process.
66Unfortunately, whenever a new person is added or someone goes into alumni
77status, there are a number of disparate places that need to be updated. This
88page 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 .
1111
12- ### R+ rights
12+ ### Team repo
1313
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:
1517
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.
1725
1826### Full team membership
1927
2028To make a full team member, the following places need to be modified:
2129
22- - the [ team roster page ] [ team-roster ]
30+ - the [ team repo ]
2331- the [ rust-lang/TEAM] [ gh-team ] and (in some cases)
2432 [ 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
3233- the
3334 [ 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 ]
3536 - the configs are set per-repo; some teams are listed in ` rust.json ` , whereas
3637 those that span multiple repos are set in ` _global.json `
3738
3839### Team member departure
3940
4041Remove the team member from any and all places:
4142
42- - [ highfive] [ ]
43- - [ reviewers list] [ homu ]
44- - rfcbot ([ example] [ rfcbot-example ] )
43+ - [ highfive]
4544- 1password
4645- 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 ]
4948
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
5249[ gh-team ] : https://github.com/orgs/rust-lang/teams
5350[ 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