Radar · Rust · Archive · Week 35 · Aug 25 – 31, 2025
Inside Rust: Removing inactive members from GitHub organizations
Nice to knowtooling
- What changed
- The Rust team removes inactive members from its GitHub organizations.
- Production impact
- The source does not say.
- Try it
- Review the list of current organization members on GitHub to see the updated roster.
- Source
- blog.rust-lang.org/inside-rust/2025/08/26/removing-inactive-members-from-github-organizations/
Understand it, then run it
Rust’s team has decided to clean up its GitHub organizations. They will remove anyone who is not on a team in those orgs. If you still belong to a team, you stay. If you only had past contributions, you’ll be removed but can still see your past work on the website.
Run it now
// This program demonstrates the effect of removing inactive members.
// In practice, the Rust team runs a script that checks team membership
// and removes users who are not on any team. Here we simulate that
// by filtering a list of users.
fn main() {
// A mock list of GitHub usernames in the organization.
let all_members = vec![
"alice", "bob", "carol", "dave", "eve",
];
// A mock list of usernames that belong to a team.
let active_team = vec!["alice", "carol"];
// Filter out inactive members.
let active_members: Vec<_> = all_members
.into_iter()
.filter(|m| active_team.contains(m))
.collect();
println!("Active members after cleanup: {:?}", active_members);
}
What it printed when we ran it on Rust 1.98.1 (edition 2024)
Active members after cleanup: ["alice", "carol"]
Run sends this program (for Solidity, the contract and its tests) to our own sandbox, where it is compiled and run once, with no network, and what it printed or the test report comes back here. Nothing is kept. Runs are counted per visitor for the day so everyone gets a turn; the details are on the legal page.
Written by gpt-oss-20b from the linked source · claims checked against the sources · archive, not individually reviewed