Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

jieyouxu
Copy link
Member

@jieyouxu jieyouxu commented Nov 2, 2024

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
Copy link
Member

or is this covered by infra

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

@jieyouxu
Copy link
Member Author

jieyouxu commented Nov 2, 2024

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

@onur-ozkan
Copy link
Member

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
Copy link
Contributor

Kobzol commented Nov 2, 2024

(me, I'm in both 😆) 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
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants