rust-lang / team

Rust teams structure
Apache License 2.0
312 stars 287 forks source link

Allow T-bootstrap to have write access to rustc-dev-guide repo #1603

Open jieyouxu opened 2 weeks ago

jieyouxu commented 2 weeks ago

T-bootstrap maintains the build system, it makes no sense why bootstrap doesn't have write acccess (unless this is covered by T-infra...?)

cc @spastorino and @onur-ozkan

I guess also cc @rust-lang/bootstrap for FYI.

Noratrieb commented 2 weeks ago

or is this covered by infra

No, y'all are not in infra: https://github.com/orgs/rust-lang/teams/infra

jieyouxu commented 2 weeks ago

bootstrap is a subteam of infra, but yeah I think the perms don't carry over to subteam

onur-ozkan commented 2 weeks ago

bootstrap is a subteam of infra, but yeah I think the perms don't carry over to subteam

Off topic, but I hardly see any connection between the Infra and Bootstrap teams.

Kobzol commented 2 weeks ago

(me, I'm in both :laughing:) But seriously, I think they are related. One of the big responsibilities of t-infra is the maintenance of CI in the rust-lang org, and the most important CI is rust-lang/rust's CI. And that essentially consists of running bootstrap + a few additional scripts on top. More generally, bootstrap is an important piece of infrastructure that sustains the development of the compiler.

onur-ozkan commented 2 weeks ago

Any team can be connected/related to another in that sense. To me, compiler team seems like a better fit for the bootstrap team to be a sub-team.