Repository navigation
Moderation team recertification #408
Description
Activity
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.
Reacted by Richard Lau, Matteo Collina, Rich Trott, Waleed Ashraf, James M Snell, Joe Sepi, Saulo Nunes and Ahmad AwaisReacted by Jordan Harband, Matteo Collina, Rich Trott, Benjamin Gruenbaum, Waleed Ashraf, James M Snell, Tierney Cyren, Joe Sepi, Saulo Nunes and Ahmad AwaisGreat job folks!
Reacted by Jordan Harband and Tierney CyrenNo objections to recertifying here.
Reacted by Jordan Harband and Tierney CyrenNo objections. +1 to recertifying.
Reacted by Jordan HarbandTL;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.
Reacted by Rich Trott, James M Snell, Jordan Harband, Ryan H. Lewis and Waleed AshrafReacted by Benjamin GruenbaumI am interested in continuing to serve on the moderation team as well ❤️
Reacted by Jordan Harband, Ryan H. Lewis, Rich Trott and Waleed AshrafReacted by Benjamin GruenbaumOn 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 😅
Reacted by Jordan Harband, Benjamin Gruenbaum and Waleed AshrafI am unable to allocate the time needed to serve on this team and will not be continuing this year. Thank you. 💖✨
Reacted by Jordan Harband, Benjamin Gruenbaum and Waleed AshrafGood question, and it is time for me to step down.
I have too many other priorities to focus on for noow, and my work has def pulled away from this work. Certainly not doing any favors here by taking up a seat. 🤗Reacted by Jordan Harband, Benjamin Gruenbaum and Waleed AshrafWe discussed in the TSC meeting today the following proposal from Rich:
- Re-certify the following people:
- We should not re-certify these people as they have voluntarily removed themselves from the team
or have not responded, but can always be added at a later time if they decide they want to be
part of the team:
And the following people in attendance will be counted as voting +1
- Anna Henningsen @addaleax (TSC)
- Сковорода Никита Андреевич @ChALkeR (TSC)
- Colin Ihrig @cjihrig (TSC)
- Gabriel Schulhof @gabrielschulhof (TSC)
- Jeremiah Senkpiel @Fishrock123 (TSC) (Partially)
- Michael Dawson @mhdawson (TSC)
- Myles Borins @MylesBorins (TSC)
- Sam Roberts @sam-github (TSC)
- Tobias Nießen @tniessen (TSC)
@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.)
3 remaining items
In the commcomm meeting meeting today the following commcomm members voted to recertify based on the recommendation:
- Michael Dawson (@mhdawson)
- Manil Chowdhury (@keywordnew)
- Tierney Cyren (@bnb)
- Adam Miller (@amiller-gh)
- Joe Sepi (@joesepi)
- Waleed Ashraf (@WaleedAshraf)
@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.
In the commcomm meeting meeting today the following commcomm members voted to recertify based on the recommendation:
- Michael Dawson (@mhdawson)
- Manil Chowdhury (@keywordnew)
- Tierney Cyren (@bnb)
- Adam Miller (@amiller-gh)
- Joe Sepi (@joesepi)
- Waleed Ashraf (@WaleedAshraf)
@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 teamThis 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.
Reacted by Ahmad Awais and Waleed AshrafWith 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!
Reacted by Benjamin Gruenbaum and Jordan HarbandReacted by Benjamin Gruenbaum@Trott awesome super helpful. I have pinged the Ryan in the slack. And you know... if you ever feel like joining again 😉
- added a commit that references this issue
on Sep 20, 2019 - added a commit that references this issue
on Jul 16, 2024
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.