Nominating @lukekarrys as a collaborator

[MylesBorins]

I would like to nominate lukekarrys as a collaborator. Luke is a member of the npm team and is focusing quite a bit on releases for npm and would like to get more involved in Node.js, especially in regards to the upcoming npm 9 release.

I am heading on parental leave for a couple months in two weeks and I think it is very important to have an npm team member how can review npm related PRs, help with any integration issues that arise, and be able to run CI. While @ruyadorno can likely support here I don't think it is fair for the npm team to rely on other folks to do this work when we have funded engineers.

While they do not currently have any contributions to Node.js directly I can vouch for their work and ethical standards. If folks are uncomfortable with making someone a collaborator until they have more explicit work directly on Node.js we could alternatively explore ways to allow Luke to run CI / CITGM without requiring a commit bit.

One thing I will advocate for, the npm team is actively working on a "sub tree" of what ships in Node.js that happens to live in another repo, npm. I believe it is extremely important for us to have more collaboration + integration between the teams. That said, totally understand if folks prefer to see more direct engagement.

[bnb]

+1 @lukekarrys is great

[Trott]

This issue has been open for a week and the nomination is now accepted. I'll email @lukekarrys privately to schedule an onboarding.

[Trott]

Argh, I just noticed now that @nodejs/collaborators were not tagged on the nomination. So that's going to restart the one-week clock, but I'll still get something scheduled.

[MylesBorins]

Argh, I just noticed now that https://github.com/orgs/nodejs/teams/collaborators were not tagged on the nomination. So that's going to restart the one-week clock, but I'll still get something scheduled.

oops, my bad 😓

[Trott]

The nomination passes. @lukekarrys has an onboarding session scheduled for Wednesday. More soon! 🎉