Update Moderator List

[benjamingr]

As refack has stepped down as a moderator a while back and we've updated the other list - it makes sense to keep this one updated.

As this is an administrative change to sync up this list with the one in the private moderation repo - I'm going to go ahead and land it directly. If anyone feels strongly against this please do feel free to speak up and suggest a revert. This is per our policy for stepping down from https://github.com/nodejs/admin/blob/master/Moderation-Policy.md

cc @nodejs/moderation

[refack]

@benjamingr you do not have write permission to this repo. You merged this change by using your owner privs you got through the mod team.
Also IMHO PRs should be open 72 hours, at least as a means to notify stakeholder of the change.

[benjamingr]

@refack that is not our process as I understood it from the policy and https://github.com/nodejs/moderation/pull/212/files - I am not aware of anything in our process requiring PRs to be open for 72 hours except for in the nodejs/node repository.

That said, if you prefer another process then do feel free to ask and I will revert this change and wait for that discussion to settle. I encourage you to speak up on PR #212 (again, whose content I cannot discuss outside the private repo) and suggest a process that is more comfortable for you.

This is entirely new territory for us. This was brought up in issue #213 in the private moderation repo which I cannot discuss here due to our policy almost a month ago - so I thought it was concluded.

[bnb]

I am -1 on reverting this change.

This is simple maintenance to reflect reality rather than misrepresenting the current status of the Moderation Team membership, which is important for community safety. Further, it is directly related to the work that the Moderation team and the meta body of work around it.

[benjamingr]

Actually, reading everything again - it is subtle, our policy says:

At any time a Moderation Team member may notify the team that they will no longer be serving. Either the resigning member or an active member will file an issue notifying the Admin group that the team member is stepping down. An active team member will take necessary steps to remove resigning team member from respective permissions and private access.

From what I understand the part I did was:

An active team member will take necessary steps to remove resigning team member from respective permissions and private access.

What we maybe did not follow correctly is:

Either the resigning member or an active member will file an issue notifying the Admin group that the team member is stepping down.

Which I believe I did in issue #213 in the private moderation repo.

Again - given you haven't been a moderation team member for about a month and the other list has been updated accordingly I thought this would not be an objectionable change - but if you object to the way this was updated - what policy would make you more content?

Also cc @nodejs/moderation

[refack]

@refack that is not our process as I understood it from the policy and nodejs/moderation/pull/212/files - I am not aware of anything in our process requiring PRs to be open for 72 hours except for in the nodejs/node repository.

@benjamingr this is not the moderation repo. This is the admin repo.

1. You do not have write permissions here.
2. This PR did not get proper review, and as a consequence the emeriti policy was not followed.

I see this as equivalent to the procedural errors that were done in a similar issue three weeks ago.

[benjamingr]

@refack I consider this action was strictly an action taken to enforce the CoC based on our moderation policy - see Tierney's message above explaining this.

I defer to my fellow moderators and the TSC/CommComm for the discussion around it and am disengaging at this point. I will also bring this up in the next moderation team meeting. I hope the discussion with them will be more fruitful.