Moderation team recertification #408
Comments
|
I think it's also a good time to thank the moderation team members for all the hard work over the last year. I think the've been doing a great job. |
|
Great job folks! |
|
No objections to recertifying here. |
|
No objections. +1 to recertifying. |
|
TL;DR: Hey, @bnb, @dshaw, @gdams, @gibfahn, @hackygolucky, @thefourtheye: can you folks indicate whether you are active in Moderation these days and wish to remain on the team? Whatever your answer, thank you for doing the hard Moderation Team work this year! Current Moderation Team members are: Of those team members, @benjamingr and @ryanmurakami are active based on activity in the moderation repository.@othiym23 chimed in on behalf of Moderation Team not that long ago. @ljharb affirmed their activity/engagement too. AFAICT, Moderation Team has not had a public meeting for a long time and I don't know where their minutes are kept. I suspect most of the conversations happen in the private Slack channel. So, rather than try to dig through a public record that I don't know where to find, I'm just flat-out asking folks if they've been doing stuff. |
|
I am interested in continuing to serve on the moderation team. |
|
I am interested in continuing to serve on the moderation team as well ❤️ |
|
On activity: we’re in an interesting place where reactions happen very rapidly and are taken care of by the time I get to them. As such, I don’t engage as I’ve found dogpiling is not an effective strategy for moderation 😅 |
|
I am unable to allocate the time needed to serve on this team and will not be continuing this year. Thank you. 💖✨ |
|
Good question, and it is time for me to step down. |
|
We discussed in the TSC meeting today the following proposal from Rich:
And the following people in attendance will be counted as voting +1
@nodejs/tsc if you are able to the meeting, please add your vote to approve or reject the re certification as proposed. |
|
+1 |
|
+1 as well. With my vote, that brings us to 11 TSC votes (out of 20 TSC members) to recertify these people: All members of Moderation Team must be re-certified by both CommComm and TSC. Since those are the only individuals being re-certified by TSC, they are also the only individuals that CommComm needs to consider at this time. @nodejs/community-committee: If you could confirm certification for those five people, we can close this out. (A subsequent issue to nominate/recruit new members would be good, but can be a separate thing.) |
|
@Trott I will abstain, but will bring this up in today's CommComm meeting. |
|
@Trott first of all thank you for doing this 🙇 I am concerned that this means there is no TSC representation in the moderation team which I think is important for establishing trust between the moderation team and various bodies. Would it be possible to ask for volunteers in the next TSC meeting? |
@benjamingr Yes, definitely! |
|
In the commcomm meeting meeting today the following commcomm members voted to recertify based on the recommendation:
@nodejs/community-committee could those of you who could not make the meeting please cast your vote in this issue or contact me with your concerns if you don't feel comfortable adding them to the issue. |
Aside, but a relevant and important one: @mhdawson https://github.com/nodejs/community-committee lists 13 CommComm members but @nodejs/community-committee has 14 members. Which (if either) is correct? The README lists @ahmadawais but they're not on the GitHub team. Meanwhile, the GitHub team includes @jemjam and @Tiriel, but they are listed as Emeriti in the README. So I'd guess that the README is correct and the team needs to be updated? |
|
+1 from me |
|
+1 from me
…On Thu, Sep 19, 2019 at 1:38 PM Matteo Collina ***@***.***> wrote:
+1 from me
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#408?email_source=notifications&email_token=AADZYV6K2KS2RCAOL4MM5FDQKO2J3A5CNFSM4ISJRLJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7EIGHQ#issuecomment-533234462>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AADZYV5LCIVXB4VTK3Q2VPLQKO2J3ANCNFSM4ISJRLJA>
.
|
|
🙌
+1 from me as well for the moderation team recertification. Mad props on
all the work you folks do.
Stuck at the Embassy for a couple of days, just returning back so
couldn't make it to the meeting but watched it on YouTube just now.
The README lists @ahmadawais <https://github.com/ahmadawais> but they're not on the GitHub team
This has come before, I am not sure how to fix this. Is there anything I
need to do? Otherwise, please add me there to sort this through.
Looking forward, peace! ✌️
|
|
@ahmadawais / @Trott: Fixed. |
|
@bnb thanks, I was going to hope you answered Rich's question/concerns. |
|
With this, it appears that the five members are recertified. I"m going to close this. If I'm wrong to do that because CommComm's procedure is different than I imagine, please re-open. |
|
P.S. @nodejs/moderation I've taken care of all the documented Moderation Team offboarding tasks except for removing the offboarded folks from the Moderation Team Slack because I do not have access to that Slack. Please do that! Thanks! |
|
@Trott awesome super helpful. I have pinged the Ryan in the slack. And you know... if you ever feel like joining again 😉 |
The last time @nodejs/community-committee and @nodejs/tsc certified members of @nodejs/moderation was August-October of 2018. (See nodejs/community-committee#361 for CommComm.)
They need to be certified annually. So, I'm adding this to the agenda for both TSC and CommComm.
In addition to certifying (or not certifying, and thus removing) members of the Moderation Team, it might also be a good time to either think about people we might ask to serve and/or put a call out for volunteers.
The text was updated successfully, but these errors were encountered: