Repository navigation
Offboard inactive members #2390
Description
Follow on from #2357 and #2358
Checklist for the offboarding of the following members:
@LucaLanziani (build)
@maclover7 (build and jenkins)
@addaleax (build)
@gireeshpunathil (build)
Thank you all for your contributions and you will be welcomed back if you wish to return!
Offboarding issue checklist
- Remove their GPG key from
testgroup innodejs-private/secrets - Remove their GPG key from
releasegroup innodejs-private/secrets - Remove their GPG key from
infragroup innodejs-private/secrets - Remove their GPG key from
infra-macstadiumgroup innodejs-private/secrets - Remove their GPG key from
github-botgroup innodejs-private/secrets - Remove them from build teams they are a member of:
- nodejs/build
- nodejs/build-release
- nodejs/build-infra
- nodejs/jenkins-admins
- nodejs/jenkins-release-admins
- nodejs-private/build
- PR changes to README.md to move the member to emeritus status
- Run
ncu-team sync README.mdto validate the user has been removed from the build teams - Remove them from the
nodejs/emailalias
Activity
AshCripps commentedon Jul 29, 2020
@nodejs/build anyone had any experience as to when I tried to clean up these keys from secrets it deleted the inventory.yml file as well? (I did also try to clean up an old keys of georges that was still left in the folder)
jbergstroem commentedon Jul 29, 2020
@AshCripps haven't seen that. Did you use
dotgpg rmto remove the keys?AshCripps commentedon Jul 29, 2020
yep I did get some gem errors though -
rvagg commentedon Jul 30, 2020
Silly low open files limit on macos, you need to increase the limit,
ulimit -n 10000or something. There's a more advanced command that sets it permanently but I don't have that at hand. Check out a clean copy of the repo, lift the limit in your current shell and run it again.AshCripps commentedon Aug 3, 2020
Removed from the secrets repo - all except luca's key got
not a valid gpg keyfor that one.Will need someone to remove @maclover7's key from githubbot secrets as I dont have access and then someone to remove the above from the github teams as im not a maintainer.
rvagg commentedon Aug 4, 2020
done
AshCripps commentedon Oct 6, 2020
Can the one of the members of build with TSC overlord powers remove the poeple at the top of the issue from the respective teams please? @mhdawson @Trott @mmarchini
mhdawson commentedon Oct 6, 2020
@AshCripps done, does not look like there is a nodejs/build-release team, was that the right name?
AshCripps commentedon Oct 6, 2020
build-release is referring to secrets team I believe
doc: update team members with ncu-team sync
mhdawson commentedon Oct 7, 2020
@AshCripps there is no team specifically related to secrets but those in the
nodejs-private/buildteam have access to the secrets repo. I've remove the inactive members from that team so I think we should be good.mmarchini commentedon Oct 8, 2020
Is build-release referring to the private keys instead of a team?
AshCripps commentedon Oct 8, 2020
sorry yes its referring to those you have access to the keys - theres no "team" as such cause there doesnt need to be.
doc: update team members with ncu-team sync (#2458)
AshCripps commentedon Oct 8, 2020
Closing as complete.
doc: update team members with ncu-team sync (#2458)