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

Alternative contact for coc violation #2

Open
pngwn opened this issue Dec 9, 2021 · 1 comment
Open

Alternative contact for coc violation #2

pngwn opened this issue Dec 9, 2021 · 1 comment

Comments

@pngwn
Copy link
Member

pngwn commented Dec 9, 2021

If a community member wishes to make a complain about a CoC violation and the individual they wish to report are on the [email protected] mailing list, they may not feel comfortable making the complaint.

It would be good if there was an alternate contact that they could use in this case.

This issue to is to gather thoughts on the following:

  • general feedback about the problem stated. Is it valid? Is it important?
  • How would a user know who is even on the coc mailing list? Should we keep a list of everyone the mailing list?
  • What should this/these alternate contact(s) be? Maintainers?
  • How do we ensure there is no overlap between the two groups?

cc @Rich-Harris @kevmodrome @sw-yx @brittneypostma @ghostdevv @coderinheels @StephDietz

@brittneypostma
Copy link
Collaborator

brittneypostma commented Dec 10, 2021

As a short term solution for ours, I included on the Sirens about page, if there is ever an issue to feel free to reach out to 1 of us directly or at the email, [email protected]. The problem being, we don't have any contact info other than the email directly on the site. Unless they know our handles in discord, it becomes difficult for someone to reach out if there is a problem. So, we need to make sure we are making it as easy as possible for someone to get in touch with a person who can handle the issue. I'll look up what other communities are doing in this regard. I know some just post a CoC on the site and leave it at that with a support email.

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

2 participants