Updates the community code of conduct (#15164)
* Updates to the Community Code of Conduct Fleshes out the Code of Conduct, with adaptations from the Contributor Covenant and the Elastic.co Community Code of Conduct. * Better format subsections * Use strong emphasis instead of sections * Set subsections correctly and add newline after strong emphasis
This commit is contained in:
Allyson Bowles
Brian Coca
parent
af8258cdf2
commit
7f500ce6b9
1 changed files with 134 additions and 8 deletions
|
|
@ -297,20 +297,146 @@ Every bit of effort helps - if you're wishing to expedite the inclusion of a P3
|
|||
is help close P2 bug reports.
|
||||
|
||||
Community Code of Conduct
|
||||
-------------------------
|
||||
=========================
|
||||
|
||||
Ansible’s community welcomes users of all types, backgrounds, and skill levels. Please treat others as you expect to be treated,
|
||||
keep discussions positive, and avoid discrimination of all kinds, profanity, allegations of Cthulhu worship, or engaging in
|
||||
controversial debates (except vi vs emacs is cool).
|
||||
Every community can be strengthened by a diverse variety of viewpoints, insights,
|
||||
opinions, skillsets, and skill levels. However, with diversity comes the potential for
|
||||
disagreement and miscommunication. The purpose of this Code of Conduct is to ensure that
|
||||
disagreements and differences of opinion are conducted respectfully and on their own
|
||||
merits, without personal attacks or other behavior that might create an unsafe or
|
||||
unwelcoming environment.
|
||||
|
||||
The same expectations apply to community events as they do to online interactions.
|
||||
These policies are not designed to be a comprehensive set of Things You Cannot Do. We ask
|
||||
that you treat your fellow community members with respect and courtesy, and in general,
|
||||
Don't Be A Jerk. This Code of Conduct is meant to be followed in spirit as much as in
|
||||
letter and is not exhaustive.
|
||||
|
||||
Posts to mailing lists should remain focused around Ansible and IT automation. Abuse of these community guidelines will not be
|
||||
tolerated and may result in banning from community resources.
|
||||
All Ansible events and participants therein are governed by this Code of Conduct and
|
||||
anti-harassment policy. We expect organizers to enforce these guidelines throughout all events,
|
||||
and we expect attendees, speakers, sponsors, and volunteers to help ensure a safe
|
||||
environment for our whole community. Specifically, this Code of Conduct covers
|
||||
participation in all Ansible-related forums and mailing lists, code and documentation
|
||||
contributions, public IRC channels, private correspondence, and public meetings.
|
||||
|
||||
Ansible community members are...
|
||||
|
||||
**Considerate**
|
||||
|
||||
Contributions of every kind have far-ranging consequences. Just as your work depends on
|
||||
the work of others, decisions you make surrounding your contributions to the Ansible
|
||||
community will affect your fellow community members. You are strongly encouraged to take
|
||||
those consequences into account while making decisions.
|
||||
|
||||
**Patient**
|
||||
|
||||
Asynchronous communication can come with its own frustrations, even in the most responsive
|
||||
of communities. Please remember that our community is largely built on volunteered time,
|
||||
and that questions, contributions, and requests for support may take some time to receive
|
||||
a response. Repeated "bumps" or "reminders" in rapid succession are not good displays of
|
||||
patience. Additionally, it is considered poor manners to ping a specific person with
|
||||
general questions. Pose your question to the community as a whole, and wait patiently for
|
||||
a response.
|
||||
|
||||
**Respectful**
|
||||
|
||||
Every community inevitably has disagreements, but remember that it is
|
||||
possible to disagree respectfully and courteously. Disagreements are never an excuse for
|
||||
rudeness, hostility, threatening behavior, abuse (verbal or physical), or personal attacks.
|
||||
|
||||
**Kind**
|
||||
|
||||
Everyone should feel welcome in the Ansible community, regardless of their background.
|
||||
Please be courteous, respectful and polite to fellow community members. Do not make or
|
||||
post offensive comments related to skill level, gender, gender identity or expression,
|
||||
sexual orientation, disability, physical appearance, body size, race, or religion.
|
||||
Sexualized images or imagery, real or implied violence, intimidation, oppression,
|
||||
stalking, sustained disruption of activities, publishing the personal information of
|
||||
others without explicit permission to do so, unwanted physical contact, and unwelcome
|
||||
sexual attention are all strictly prohibited. Additionally, you are encouraged not to
|
||||
make assumptions about the background or identity of your fellow community members.
|
||||
|
||||
**Inquisitive**
|
||||
|
||||
The only stupid question is the one that does not get asked. We
|
||||
encourage our users to ask early and ask often. Rather than asking whether you can ask a
|
||||
question (the answer is always yes!), instead, simply ask your question. You are
|
||||
encouraged to provide as many specifics as possible. Code snippets in the form of Gists or
|
||||
other paste site links are almost always needed in order to get the most helpful answers.
|
||||
Refrain from pasting multiple lines of code directly into the IRC channels - instead use
|
||||
gist.github.com or another paste site to provide code snippets.
|
||||
|
||||
**Helpful**
|
||||
|
||||
The Ansible community is committed to being a welcoming environment for all users,
|
||||
regardless of skill level. We were all beginners once upon a time, and our community
|
||||
cannot grow without an environment where new users feel safe and comfortable asking questions.
|
||||
It can become frustrating to answer the same questions repeatedly; however, community
|
||||
members are expected to remain courteous and helpful to all users equally, regardless of
|
||||
skill or knowledge level. Avoid providing responses that prioritize snideness and snark over
|
||||
useful information. At the same time, everyone is expected to read the provided
|
||||
documentation thoroughly. We are happy to answer questions, provide strategic guidance,
|
||||
and suggest effective workflows, but we are not here to do your job for you.
|
||||
|
||||
Anti-harassment policy
|
||||
----------------------
|
||||
Harassment includes (but is not limited to) all of the following behaviors:
|
||||
|
||||
- Offensive comments related to gender (including gender expression and identity), age, sexual orientation, disability, physical appearance, body size, race, and religion
|
||||
- Derogatory terminology including words commonly known to be slurs
|
||||
- Posting sexualized images or imagery in public spaces
|
||||
- Deliberate intimidation
|
||||
- Stalking
|
||||
- Posting others' personal information without explicit permission
|
||||
- Sustained disruption of talks or other events
|
||||
- Inappropriate physical contact
|
||||
- Unwelcome sexual attention
|
||||
|
||||
Participants asked to stop any harassing behavior are expected to comply immediately.
|
||||
Sponsors are also subject to the anti-harassment policy. In particular, sponsors should
|
||||
not use sexualized images, activities, or other material. Meetup organizing staff and
|
||||
other volunteer organizers should not use sexualized attire or otherwise create a
|
||||
sexualized environment at community events.
|
||||
|
||||
In addition to the behaviors outlined above, continuing to behave a certain way after you
|
||||
have been asked to stop also constitutes harassment, even if that behavior is not
|
||||
specifically outlined in this policy. It is considerate and respectful to stop doing
|
||||
something after you have been asked to stop, and all community members are expected to
|
||||
comply with such requests immediately.
|
||||
|
||||
Policy violations
|
||||
-----------------
|
||||
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by
|
||||
contacting codeofconduct@ansible.com, to any channel operator in the community IRC
|
||||
channels, or to the local organizers of an event. Meetup organizers are encouraged to
|
||||
prominently display points of contact for reporting unacceptable behavior at local events.
|
||||
|
||||
If a participant engages in harassing behavior, the meetup organizers may take any action
|
||||
they deem appropriate. These actions may include but are not limited to warning the
|
||||
offender, expelling the offender from the event, and barring the offender from future
|
||||
community events.
|
||||
|
||||
Organizers will be happy to help participants contact security or local law enforcement,
|
||||
provide escorts to an alternate location, or otherwise assist those experiencing
|
||||
harassment to feel safe for the duration of the meetup. We value the safety and well-being
|
||||
of our community members and want everyone to feel welcome at our events, both online and
|
||||
offline.
|
||||
|
||||
We expect all participants, organizers, speakers, and attendees to follow these policies at
|
||||
our all of our event venues and event-related social events.
|
||||
|
||||
The Ansible Community Code of Conduct is licensed under the Creative Commons
|
||||
Attribution-Share Alike 3.0 license. Our Code of Conduct was adapted from Codes of Conduct
|
||||
of other open source projects, including:
|
||||
|
||||
* Contributor Covenant
|
||||
* Elastic
|
||||
* The Fedora Project
|
||||
* OpenStack
|
||||
* Puppet Labs
|
||||
* Ubuntu
|
||||
|
||||
Contributors License Agreement
|
||||
------------------------------
|
||||
==============================
|
||||
|
||||
By contributing you agree that these contributions are your own (or approved by your employer) and you grant a full, complete, irrevocable
|
||||
copyright license to all users and developers of the project, present and future, pursuant to the license of the project.
|
||||
|
|
|
|||
Loading…
Reference in a new issue