Repository navigation
Removing org members who are on 0 teams #230
Description
Barring objections from @nodejs/tsc or @nodejs/community-committee, I'm going to remove members from the org who are on 0 teams. (I've done this once or twice before.) This usually happens when someone is on some teams, and then leaves the teams or the teams get removed due to inactivity or whatever. It is trivial to add someone back if there's a good reason to do so, so this is a low risk move.
I'll email the four people who are on zero teams to let them know so they aren't surprised when they get the GitHub email saying they've been removed. It will also give them the opportunity to say "Oh, I should be on the fhqwhgads translation team!" or whatever in case being on zero teams is a mistake or something.
Activity
Trott commentedon Sep 8, 2018
(I'll do this after 72 hours.)
refack commentedon Sep 8, 2018
Just a general reminder, membership in the github org, has 3 privileges:
IMHO it is reasonable that all of those should be based on active contribution to the project. Maybe with exception of emeriti, so maybe have an emeriti team?
ljharb commentedon Sep 8, 2018
Such a team could be deprived access to the moderation repo, and not included in “members”, so that it would allow folks to retain the badge forever if they wished.
addaleax commentedon Sep 8, 2018
Just to clarify, access to the nodejs/moderation and nodejs/members repositories is only granted to the nodejs/members team, not by membership in the github org itself.
jakeNiemiec commentedon Sep 9, 2018
Details
Sorry, misread the first message.@Trott While you are seeking to clean up inactive members, you should also consider removing any members match the criteria for "automatic removal" per the end of Section 4 of both charters:Trott commentedon Sep 9, 2018
@jakeNiemiec Those criteria for removal have never been met by anyone since being adopted, at least not on the TSC side. I'm not a member of CommComm so I can't speak to that. I definitely watch out for this stuff on the TSC. All current members of the TSC, except for the member who was only added this week, participated in nodejs/TSC#569, so there's nobody on the TSC who qualifies for automatic removal at this time.
Trott commentedon Sep 13, 2018
All done! Thanks!