Create teams for committer management

[dougwilson]

This is a tracking issue around creating the teams for getting some of the members elevated to committer as talked about in the TC meeting #129

@wesleytodd volunteered, but Wes, feel free to let us know here if you would like someone else to help out :) !

[wesleytodd]

So I think we have a few things to do here:

1. Owners. There are currently some folks not active in the project or on the TC who are owners. We should probably make only the active TC members owners
2. Clean up existing teams. There are a few teams for collaborators/contributors. We should pick a name schema and stick to it then make them for all the repos
3. Clean up folks without 2fa enabled.
4. Make a plan for aligning this stuff with the new repo captains stuff

I can do this but I don't want to disrupt anything by taking away access to something. Are we concerned about that if I start changing these settings?

[wesleytodd]

Before I clean up the "owner" roles, if you are relying on this for anything and are not on the TC please reply here with how and why. If I do not hear back from you within 48 hours I am going to slim down the owners to just active TC members.

cc @joewagner @mikeal @ritch @tj @troygoode

[wesleytodd]

Ok, I just updated the owner roles to be just the currently active TC members. I moved everyone else to normal member role.

I am going to go through the existing teams next and get them sorted. I might have to ping folks in here if I have any questions about what the team was used for and how the changes I make might effect folks abilities to work on the given repos.

[wesleytodd]

Oh! I forgot to do the owner change in pillarjs and jshttp. I see now there are a bunch of other folks in those I need to ping.

pillarjs:

• @donpark
• @jasnell
• @jonathanong (and your bot @jongleberry-bot)
• @mikeal
• @ritch
• @sindresorhus

jshttp:

• @eivindfjeldstad
• @jasnell
• @jonathanong (and bot)
• @mikeal
• @Raynos
• @ritch
• @tj

[wesleytodd]

Ok, I am just going to go ahead and remove folks now. If anyone needs it back for a reason we are unaware of just ping me (if I dont see here you can dm me in the OpenJS slack and I will see it on my phone if it is an urgent matter of some sort).

[wesleytodd]

Owner is now correctly assigned across all three orgs with the exception of @crandmck who was not a member of the others. Obviously not everyone needs to do anything administrative with this role, but the important part is that we have it now in the governance on how this access is managed. If we think we want to change anything about that to add folks back in or remove folks while still being on the TC feel free to raise an issue to discuss.

[wesleytodd]

Also for anyone ping'd above, we are cleaning up the npm publish stuff as well. You might see an invite to the org where we will be managing access going forward, please accept that so you can be added to the right teams. The goal is not to remove anyone from access they need, but since this is all so old some things are unclear so if we make a mistake please jump in here and help us fix it.

[wesleytodd]

Hey folks, we are trying to setup the npm org for this and need folks to accept the invites which you should have gotten. If you do not respond within the next 48h you may loose access. If that happens and you still need it, please reach out and we can get things setup again.

Folks still needing to accept: @TooTallNate, @defunctzombie, @tj , @Fishrock123, @sheplu, @LinusU

[jonchurch]

@wesleytodd Just opened a PR with a first pass for capturing a plan for github access organization expressjs/express#5503

[TooTallNate]

You can probably remove me. Not sure what triggered me being invited here.

[defunctzombie]

I can also be removed.