You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to GitHub about Moderators in an organization,
You can add organization members or teams as moderators for your organization. Moderators can block and unblock users from the organization, minimize comments, and manage interaction limits for all public organization repositories.
I think having the access can come in handy while running triage if I could limit interaction on spam PRs or hide spam comments etc.
If we were to do this, we could do this two ways,
allow moderation rights to the triage team, in moderation we can simply add the existing team
or create a new mod team with active triage / selective members in case we want to limit giving mod access every triage members.
The text was updated successfully, but these errors were encountered:
I like the idea, @IamLizu! This change would give the triage team the ability to manage spam PRs, which is a great addition. However, these extra capabilities will also bring additional responsibilities to the role.
In my opinion, we can move forward with this, but it might be a good idea to discuss it further in the next TC meeting, as the new responsibilities will blend moderation with triage tasks (cc: @expressjs/express-tc).
We should also document in detail how moderation should be carried out within the organization, as this change effectively delegates moderation responsibilities to the triage team.
I can draw up a Moderating Guide for your (TC) review. I guess Moderation can be a different from triage as well instead of allowing triage members moderation rights.
I suppose the we could create a separate team for Moderation and give that team moderation access in the orgs. Becoming a member of the moderation team can have requirements like,
active member of the triage team for at least 6 months
We could have the moderation rights removed for,
breaking the code of conduct.
This is just an idea, I would be very happy to draw up that moderation guide mentioning the requirements, and what it mean to be a moderator within the org. However, I would like to have a go ahead from the team (TC) to confirm whether we are moving forward with this.
According to GitHub about Moderators in an organization,
I think having the access can come in handy while running triage if I could limit interaction on spam PRs or hide spam comments etc.
If we were to do this, we could do this two ways,
The text was updated successfully, but these errors were encountered: