I'm trying to pull @gdams into help make progress on configuring our new mac infrastructure.

I'd at least like to get him access to the individual machines.

Broader access would be good and I'm thinking it might not be as much of a concern yet since the infra is not yet setup and being used in our builds. We could look at doing things like changing keys etc. after the setup is complete.

As per the regular requirements in https://github.com/nodejs/build/blob/master/doc/process/special_access_to_build_resources.md:

• Does the scope and size of the need justify providing access.
  • It is important that we make progress on bringing the mac infra online and we have not been able to progress that as fast as necessary -> Yes
• Is the invidual a collaborator. If so then access should be allowed provided the first point is satisfied.
  • He is not yet a collaborator, but has been active in the CitGM group and has already had some configuration access to the CI jobs managed by the CitGM team
• Length and consistency of involvement with Node.js working groups and/or community.
  • He has been contributing to CitGM over the last 6-12 months, and is part of the CITGM team.
• Consequences to the invidudal in case of mis-behaviour. 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 with me at IBM and there would be consequences.
• Are there collaborators who work with the individual and can vouch for them.
  • I will vouch for him. Other collaborators that may support as well include @gibfahn