-
Notifications
You must be signed in to change notification settings - Fork 16
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
Should we offer a means of anonymous reporting? #16
Comments
Yes. The goal should always be that everyone feels comfortable reporting publicly. The only way to be sure that is true is if there is an equally accessible way to report anonymously and privately. |
👍 to the general idea. Chromium's uses a google form, is that something we could use? |
As soon as we have the subcommittee formed w/ the proper email we use, we can also define something to address this. I believe this should be the first group task for the CoC subcommittee. |
If anonymous reporting is allowed, there may need to be a disclaimer on the form that actions may be limited by not being able to do further reach out for the report and enforcement. I know y'all said that it's already been mentioned that it's difficult to execute on anonymous reports--and I've had to do it. It's very, very difficult. |
committee discussed next step is to draft an update to the CoC re: this guidance. need to get this through plenary as well, so would be good to combine this draft with #49 action: @tabatkins has volunteered to draft this |
Ping for PR review (no rush, of course). |
The Chromium code of conduct does this, for example. They do note that it may be harder to take action on an anonymous report.
But it still seems like it could be valuable to encourage people to speak up even if they don't feel comfortable bringing something to the advisory committee with their name attached.
The text was updated successfully, but these errors were encountered: