Repository navigation
Node.js Build working group audit #2357
Description
5 months after #2140 im finally getting round to this.
@nodejs/build Please comment here if you are planning to remain active within the working group or are happy to be moved to emeritus.
I plan to wait ~2 weeks before pinging members who havent responded individually. After a month member will be automatically moved to emertius.
Reminder as per our Governance emeritus members will be welcomed back if they wish to return.
Activity
richardlau commentedon Jun 17, 2020
Am planning to remain active.
mmarchini commentedon Jun 17, 2020
I haven't been much active in the WG in a while except for occasionally responding to incidents (i.e. rebooting machines mostly). I'll try to remain active, but can't really promise anything at the moment. If folks think it's better for me to move to emeritus I'm fine with that as long as I can retain access to test machines, as it has been quite useful to unblock PRs when there's an infra issue.
AshCripps commentedon Jun 17, 2020
@mmarchini Personally im not looking for everyone to be active-active. (contributing to the node org as whole is good enough for me), this is more to clean up our access from people who have left the project.
MylesBorins commentedon Jun 17, 2020
I have not been super active but do appreciate the permissions that I get in CI from being a member. Happy to move to emeritus if folks prefer, but would like to remain a member if there are no complaints
jbergstroem commentedon Jun 17, 2020
I would like to stay around if possible.
AshCripps commentedon Jun 17, 2020
@MylesBorins that's completely your choice with regards to moving to emeritus, the Jenkins access is separate so it's just whether you would like to keep the machine access and recieving pings when something goes wrong.
@jbergstroem as a member of build infra I don't think we could afford to lose you :).
phillipj commentedon Jun 18, 2020
I'd like to be able to maintain and access the host where @nodejs-github-bot is located.
Sadly don't have time to contribute in other build concerns. If you'd prefer removing me from the build team to reduce my privileges and insight, that would be fine with me as long as I can ping others to get help with updating my SSH key etc when needed.
rvagg commentedon Jun 18, 2020
active
mhdawson commentedon Jun 18, 2020
active
Trott commentedon Jun 19, 2020
active (or at least active-ish)
joaocgreis commentedon Jun 22, 2020
active (though not much this month)
AshCripps commentedon Jun 29, 2020
Ping those who havent responded yet:
@LucaLanziani
@bnoordhuis
@addaleax
@Starefossen
@maclover7
@joyeecheung
@gireeshpunathil
bnoordhuis commentedon Jun 29, 2020
Active(ish)
LucaLanziani commentedon Jun 29, 2020
Thanks for the ping @AshCripps , I've tried my best but it's proven hard to find the time so I think it's for the best if I get removed from the working group.
Thanks everyone for the opportunity and sorry for not coming forward sooner about this. Hopefully things will change in the future and I will be able to help a bit here ;).
Starefossen commentedon Jun 29, 2020
I haven’t been much active lately but if there are interest for moving more of the build and test infrastructure towards Infrastructure as Code with Terraform and/or Kubernetes I would love to help out with that.
AshCripps commentedon Jul 16, 2020
FInal warning ping:
@addaleax
@maclover7
@joyeecheung
@gireeshpunathil
Ill start the removal processes on monday if I havent heard otherwise
joyeecheung commentedon Jul 17, 2020
I plan to remain active(ish)
AshCripps commentedon Jul 23, 2020
Audit complete. Offboarding being tracked in #2390.