Skip to content
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

Closed
ajklein opened this issue Mar 11, 2017 · 7 comments
Closed

Should we offer a means of anonymous reporting? #16

ajklein opened this issue Mar 11, 2017 · 7 comments

Comments

@ajklein
Copy link

ajklein commented Mar 11, 2017

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.

@ljharb
Copy link
Member

ljharb commented Mar 11, 2017

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.

@gnarf
Copy link

gnarf commented Mar 13, 2017

👍 to the general idea. Chromium's uses a google form, is that something we could use?

@leobalter
Copy link
Member

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.

@hackygolucky
Copy link

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.

@ctcpip
Copy link
Member

ctcpip commented Jun 22, 2023

committee discussed on 2023-06-22 - quorum (@ctcpip, @hemanth, @mpcsh) is in favor of this, probably via a Google Forms form (or equivalent), but first step is to draft the change to the CoC itself, and get that through committee (and Ecma?)

@ctcpip
Copy link
Member

ctcpip commented Aug 31, 2023

committee discussed 2023-08-31 and felt that the path forward here may be to recommend the person to create a throwaway/anonymous email account and use the existing reporting mechanism. this allows them to remain anonymous and allows for follow-up communication.

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

@tabatkins
Copy link
Contributor

Ping for PR review (no rush, of course).

@ctcpip ctcpip closed this as completed in 0911f76 Sep 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants