You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Provide temporary access to @gireeshpunathil to AIX CI machines #463
Length and consistency of involvement with Node.js working groups and/or community.
He has commit to node.js as far back as: Dec 5, 2015 and involvement on issues as far back
as far back as March 2015.
Consequences to the individual in case of mis-bahaviour. For example, would they potentially lose their job if they were reported as mis-behaving to their employer ? Would being banned from involvement in the Node.js community negatively affect them personally in some other way
He works at IBM in the Node.js Runtime technologies group. Being banned would
definitely have an impact
Are there collaborators who work with the individual and can vouch for them.
I'll add his public key to one of the AIX machines and co-ordinate with respect to other interaction required. Since the AIX builds only run once a night the co-ordination with existing builds should be limited.
Activity
jbergstroem commentedon Aug 10, 2016
Sounds good to me. Will you handle his pubkey and show him the ropes? (copy repo, take bot out of action, etc)
joaocgreis commentedon Aug 10, 2016
@mhdawson sounds good to me as well!
mhdawson commentedon Aug 11, 2016
I'll add his public key to one of the AIX machines and co-ordinate with respect to other interaction required. Since the AIX builds only run once a night the co-ordination with existing builds should be limited.
gireeshpunathil commentedon Apr 7, 2017
@mhdawson - the purpose of this temporary access is achieved, and the access can now be revoked. Thanks to the approvers and endorsers.
maclover7 commentedon Nov 8, 2017
@mhdawson Can you confirm access has been revoked?
mhdawson commentedon Nov 16, 2017
Deleted the user I had setup for @gireeshpunathil