-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question regarding visibility of CoC reports #512
Comments
/ping @nodejs/tsc @nodejs/community-committee |
I am fine leaving it to the discretion of the moderation team , based on the perceived seriousness of the content and based on the discussion they have, they may decide to disclose the full content, or disclose the theme but omit the identities |
I think we should remove the requirement in the policy to open an issue. I think posting in the report to TSC/CommComm (which I currently post in the TSC meeting issues once a week) should be sufficient. I know the moderation repo is supposed to be a private repo for Node.js members and its contents are supposed to be confidential. In reality, we give access to hundreds of people around the globe with near-zero vetting for most of them. That's fine for some purposes, but for things like this, I think it's too leaky/risky to post private information there in many cases. In that repo, in particular, I don't think the moderation team should ever disclose the identities of people involved in CoC reports due to liability concerns. If a reporter is subsequently doxed or harassed, could we be sued? If someone whose actions were reported were to experience a negative career event shortly after and believed it was due to allegations in a report we post, could we be sued? I don't know the answer to these questions definitively, but I suspect the answer is "yes" and that we should act cautiously here. We have an obligation to act to make and keep Node.js a safe place for people to participate, and so we should certainly indicate when we are acting on CoC reports. And we have the right to restrict people from Node.js spaces if we believe they are failing to act in a way that is appropriate and beneficial for the project and its participants. But identities of parties involved in complaints about private communications and actions should (in my opinion, at least based on what I understand right now) never be revealed. I can imagine an exception in extraordinary circumstances, but as a rule, no, identities should not be disclosed by us. (In many cases, someone's actions are very public and people can easily figure out who it is. That's OK. We still don't have to name them semi-publicly ourselves.) |
I agree with @Trott with working to ensure we don't identify parties. I wonder if we should have a more private repo where an issue is opened instead, possibly with normally only the Moderation team having access? |
This has been merged/fixed :] If anyone feels this should stay open - feel free to reopen |
Hey,
Our moderation policy details what happens when a report is received at [email protected] :
I have a few questions and would like to clarify a few things:
All these are mostly technicalities - but I believe we should clarify those and close these (small) gaps in our process.
What should we do? cc @nodejs/moderation
The text was updated successfully, but these errors were encountered: