Michael Dawson

@bnb can you confirm that it is an option in npm to change the name of an existing account and that it will have no unwanted side effects ?

> generate new keys everywhere. What keys? The user account was added as a backup and is basically not used in day-to-day work.

I think creating a new account, and transitioning over makes sense. That also means that anybody can do that, along with working to get the password shared though a mechanism...

@bnb sounds good. I think you could create a new npm account with the right name, have the credentials shared through 1password and then we can ask the teams publishing...

> I'd be happy to do this, but not sure if that's what you were suggesting :P That was what I was suggesting.

@joaocgreis do we already use Azure for some of our Windows builds and if so would we want to apply to this for additiona/continuing credits ?

We have VMs in Azure so I think this can be closed. Please let us know if that was not the right thing to do.

If/when the change lands in the main repo we'll look at upgrading.

Sent email to Moss Uchida asking if the referenced PR is going to land.

@gabrielschulhof do you mean an option when you run the job which can add the --debug or not? That might work, although I think in many cases we'd want Node.js...