Access for @KevinEady to debian 8 test VM

[mhdawson]

We've had trouble recreating a CI failure in nodejs/node-addon-api#1150.

While it seems to occur regularly in CI runs on debian 8, we can't recreate locally. I'd like to request temporary access for @KevinEady based on section nodejs/node-addon-api#1150 of our goverance.

In terms of:

• Does the scope and size of the need justify providing access.
• Is the individual a collaborator. If so then access should be allowed provided the first point is satisfied.
• Length and consistency of involvement with Node.js working groups and/or community.
• Consequences to the individual in case of misbehaviour. 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 ?
• Are there collaborators who work with the individual and can vouch for them.

I believe the need justifies the scope of the access requested (1 test machine), he's a long time contributor to the Node-api effort, and I'm confident he will take appropriate care while using the machine.

[mhdawson]

@nodejs/build any concerns or +1s?

[richardlau]

+1

[mhdawson]

@KevinEady, I'm out until next Tuesday and we should probably avoid release day. Would 10 ET on Wednesday the 20th be a good time to take a look together? In advance of that if you send me your ssh key I can add to one of the machines in case you have a chance to investigate before then?

[KevinEady]

Hi @mhdawson , I have sent you my public key over email. I will have time this long weekend over the holiday so if you can set up access on the machine I can take a look.

20 April does not work for me as I have a lot of work meetings on that Wednesday. The following Thursday, 21 April works for me.

[mhdawson]

@KevinEady sorry must have been after I left for the weekend. Will plan to add your key today.

[mhdawson]

I've added @KevinEady 's key to test-digitalocean-debian8-x64-1 and set up his own directory/user. I have not disabled the machine from the CI since we only have 2 debian8 machines in the ci.

[mhdawson]

@KevinEady I think you are done with the machine. If you can confirm I'll remove your key and clean up the directory I created for you.

[github-actions]

This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made.

[mhdawson]

Checked today his key is no longer there, closing.