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.

Sign up for GitHub

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

Create CODE_OF_CONDUCT.md #899

Merged
merged 1 commit into from
Oct 9, 2020
Merged

Create CODE_OF_CONDUCT.md #899

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
76 changes: 76 additions & 0 deletions CODE_OF_CONDUCT.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,76 @@
# Contributor Covenant Code of Conduct

## 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
our community a harassment-free experience for everyone, regardless of age, body
size, disability, ethnicity, sex characteristics, gender identity and expression,
level of experience, education, socio-economic status, nationality, personal
appearance, race, religion, or sexual identity and orientation.

## Our Standards

Examples of behavior that contributes to creating a positive environment
include:

* Using welcoming and inclusive language
* Being respectful of differing viewpoints and experiences
* Gracefully accepting constructive criticism
* Focusing on what is best for the community
* Showing empathy towards other community members

Examples of unacceptable behavior by participants include:

* The use of sexualized language or imagery and unwelcome sexual attention or
advances
* Trolling, insulting/derogatory comments, and personal or political attacks
* Public or private harassment
* Publishing others' private information, such as a physical or electronic
address, without explicit permission
* Other conduct which could reasonably be considered inappropriate in a
professional setting

Copy link
Collaborator

@agilgur5 agilgur5 Oct 13, 2020 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you want to use the Contributor Covenant, I think several of these should have a clear "Good/Bad" example that specifically illustrates said behavior so there is less ambiguity.

This was very painful, but I went through some abusive instances in TSDX's history that occurred to multiple maintainers and paraphrased to make examples:

* Snarky, sarcastic, condescending, or passive-aggressive behavior:
❌  Bad: "Will you fix this issue, or should I just not use this library?"
✅  Good: "I'd like to use this library, but this issue is a blocker for me right now."

❌  Bad: "How many more breaking bugs do you need?"
✅  Good: "These bugs have been very frustrating for me, so I would appreciate if changes respected SemVer more carefully and testing were a higher priority".

❌  Bad: "_Really_?"
✅  Good: "I believe this line doesn't match up with what you said, but correct me if I'm wrong"

* Trolling, insulting/derogatory comments, and personal or political attacks
❌  Bad: "You shouldn't have closed my issue, you're a jerk"
✅  Good: "I disagree that it should be closed and think this issue is substantial for these reasons [...]. Maybe this will be reconsidered down the line"

❌  Bad: "Who put _you_ in charge??"
✅  Good: "I disagree with this approach and think it could be improved in these ways [...]. Maybe this can be reconsidered on that basis"

❌  Bad: "You're uninformed and don't know what you're talking about. Your opinion is wrong. I'll take my chances with other libraries."
✅  Good: "Here are some examples that illustrate my point [...]. I disagree with this opinion and think the reverse trade-offs are better to make. I hope these examples can better inform the community's decisions, but I feel strongly enough about these trade-offs that I'll be exploring other approaches."

On the positive side, here's a few other examples:

❌  Bad: "End of story."
❌  Bad: "Period."
❌  Bad: "My word is final."
✅  Good: "Here's a few reasons why I don't think that is a good approach [...]. The examples and evidence here are not currently enough to sway my opinion, but if there is more community support, maybe it can be reconsidered then."

❌  Bad: "I'm not going to use that"
❌  Bad: "I don't like that"
❌  Bad: "That's a bad option"
✅  Good: "I don't agree with that option because of these trade-offs: [...]. If more positive trade-offs outweigh the cons, maybe I'll reconsider"

## Our Responsibilities

Project maintainers are responsible for clarifying the standards of acceptable
behavior and are expected to take appropriate and fair corrective action in
response to any instances of unacceptable behavior.

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,
threatening, offensive, or harmful.

## Scope

This Code of Conduct applies both within project spaces and in public spaces
when an individual is representing the project or its community. Examples of
representing a project or community include using an official project e-mail
address, posting via an official social media account, or acting as an appointed
representative at an online or offline event. Representation of a project may be
further defined and clarified by project maintainers.

## Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported by contacting the project team at [email protected]. All
Copy link
Collaborator

@agilgur5 agilgur5 Oct 13, 2020 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm currently the only active maintainer and am unaffiliated with Formium -- nor consented to this repo being under a for-profit business's org -- so this feels backward to me.

In this instance, you also responded first by victim-blaming me first before investigating, then deleted your own comment after investigating, then proceeded to edit this to add a condescending remark here followed by a false equivalence victim-blame. I think that is very concerning and those actions cause significant damage to my mental health. It sounds hypocritical that someone actively violating the CoC would be policing others' actions with respect to that same CoC

complaints will be reviewed and investigated and will result in a response that
is deemed necessary and appropriate to the circumstances. The project team is
obligated to maintain confidentiality with regard to the reporter of an incident.
Further details of specific enforcement policies may be posted separately.

Project maintainers who do not follow or enforce the Code of Conduct in good
faith may face temporary or permanent repercussions as determined by other
members of the project's leadership.

## Attribution

This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html

[homepage]: https://www.contributor-covenant.org

For answers to common questions about this code of conduct, see
https://www.contributor-covenant.org/faq