Skip to content

Conversation

apiraino
Copy link
Contributor

@apiraino apiraino commented Apr 2, 2025

As discussed with T-compiler leads, we are removing WGs that are not active anymore

The list of retired WGs matches that in the forge documentation (the second table)

cc @davidtwco @wesleywiser (for an ack)

thanks

@apiraino apiraino requested a review from a team as a code owner April 2, 2025 16:40
Copy link
Contributor

@senekor senekor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't this be changed in https://github.com/rust-lang/team/ ? We get the information from there and don't update it manually here. If these WGs updated accordingly in the team repo, they should automatically disappear from the website.

@apiraino
Copy link
Contributor Author

apiraino commented Apr 2, 2025

The question is legit. The rust-lang/team is the Source of Truth for Everything and I am not sure about the cascading consequences of deleting a subteam, specifically in terms of permissions changes to its members on repositories or other machinery of the infra. Are you confident that it is safe @senekor ?

@senekor
Copy link
Contributor

senekor commented Apr 2, 2025

Well no, but I don't manage the teams repo. I just think you should open a PR there. Those people will know. In the unlikely case that the teams repo can't be adjusted in a way that makes the problem go away on the website automatically, I'm happy to help figure out a general solution. But hard coding a list of defunct working groups in our source code doesn't sit right with me.

@apiraino
Copy link
Contributor Author

apiraino commented Apr 2, 2025

ok, will ask our T-infra friends and then be back 🙂

@senekor
Copy link
Contributor

senekor commented Apr 2, 2025

I will close this for now, on the assumption that the website shouldn't need any changes. Feel free to reopen in case of new information.

@senekor senekor closed this Apr 2, 2025
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.

2 participants