-
Notifications
You must be signed in to change notification settings - Fork 196
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
Fixes #1651 - adding Code of Conduct #1660
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
Can you add a link to this doc in README.md in the Contributing section somewhere?
https://github.com/webcompat/webcompat.com/#contributing
FYI @webcompat/core-developers. |
codeofconduct.md
Outdated
## Our Pledge | ||
|
||
In the interest of fostering an open and welcoming environment, we as | ||
contributors and maintainers pledge to making participation in our project and |
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
codeofconduct.md
Outdated
|
||
## Our Standards | ||
|
||
Examples of behavior that contributes to creating a positive environment |
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
codeofconduct.md
Outdated
Project maintainers have the right and responsibility to remove, edit, or | ||
reject comments, commits, code, wiki edits, issues, and other contributions | ||
that are not aligned to this Code of Conduct, or to ban temporarily or | ||
permanently any contributor for other behaviors that they deem inappropriate, |
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
codeofconduct.md
Outdated
|
||
## Enforcement | ||
|
||
Instances of abusive, harassing, or otherwise unacceptable behavior may be |
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
Added a few grammatical comments. Re. the reporting procedure, wouldn't it be better to have a general inbox (e.g. [email protected] or similar) rather than a single personal address? |
@tagawa you should probably file language-related issues upstream at https://github.com/ContributorCovenant/contributor_covenant, although I can recall at least some of your points being discussed before, and it turns out those were perfectly legal and "more right" when watched from a linguistic point of view. I'm torn between having a generic inbox vs. having a person who is responsible for handling complains. I've heard questions in the past if mails end up on a public mailing list or people being concerned about who can rad complain mails, which isn't really an issue if there is a dedicated person, since people know this is the only person who will have direct access to the mail. No objection against trusting @zoepage with that job from my side. Also, thanks for doing this. ❤️ |
@tagawa Thanks! I agree with @denschub on filing issues. :) re:general address @denschub ofc <3 |
Thanks for the comments about upstream changes. I'll take a look at the main project and see what the past discussions were. I see your point about a personal address seeming more welcoming than a generic address, and I also agree that it mustn't be a public mailing list. This could perhaps be made clear in note in the Code of Conduct. I also have no doubts or prejudices regarding any of the WebCompat team to act as the point of contact. My concerns are:
Incidentally, I don't think we should be making generalisations about which gender is preferable for the point of contact, as this depends on the individual filing a complaint. Probably best to not make assumptions about people's preferences. A compromise might be to set up a mailbox with a neutral human name, e.g. [email protected] but that could be seen as deceptive. Anyway, there are pros and cons to both approaches so interested to hear other opinions. |
I agree. What about we add @denschub as a second person as he is also very experienced in CoC matters? Would also solve the holiday / legal issue.
This is not a generalization or assumptions, but drawn from my experience being a CoC person for years in the FLOSS community. As the most reports (from my experience and from studies I've read > 95%) come from non "cis males", it should be safe to assume a female person as point of contact is crucial those incidents get reported. As such matters can be very delicate and in the "wrong hands" create a really hurtful backlash to the reporters professional as well as personal life, it is important to create a safe space for everyone and build a base of trust. When those who report know, who they are reporting to and can even do a bit of research for that person on the web, to make sure the person is trustworthy, it will increase the chance of getting a report immensely. This is why, I'd also not just add the email adress, but also the GitHub handle to the CoC. |
I think we can pull in @tagawa's suggested edits in the meantime. |
Also, if @denschub agrees, I think it's preferable to have 2 contacts. |
No objections, have been doing the same in other projects for quite a while now. |
Added suggested changes. |
Thanks @zoepage! |
r? @miketaylr