Django Commons Code of Conduct
Our Pledge
We as members, contributors, and leaders pledge to make participation in our
community a harassment-free experience for everyone, regardless of age, body
size, visible or invisible disability, ethnicity, sex characteristics, gender
identity and expression, level of experience, education, socio-economic status,
nationality, personal appearance, race, caste, color, religion, or sexual
identity and orientation.
We pledge to act and interact in ways that contribute to an open, welcoming,
diverse, inclusive, and healthy community.
Our Standards
Examples of behavior that contributes to a positive environment for our
community include:
- Demonstrating empathy and kindness toward other people
- Being respectful of differing opinions, viewpoints, and experiences
- Giving and gracefully accepting constructive feedback
- Accepting responsibility and apologizing to those affected by our mistakes,
and learning from the experience
- Focusing on what is best not just for us as individuals, but for the overall
community
Examples of unacceptable behavior include:
- The use of sexualized language or imagery, and sexual attention or advances of
any kind
- Trolling, insulting or derogatory comments, and personal or political attacks
- Public or private harassment
- Publishing others’ private information, such as a physical or email address,
without their explicit permission
- Other conduct which could reasonably be considered inappropriate in a
professional setting
Enforcement Responsibilities
Community leaders are responsible for clarifying and enforcing our standards of
acceptable behavior and will take appropriate and fair corrective action in
response to any behavior that they deem inappropriate, threatening, offensive,
or harmful.
Community leaders 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, and will communicate reasons for moderation
decisions when appropriate.
Scope
This Code of Conduct applies within all community spaces, and also applies when
an individual is officially representing the community in public spaces.
Examples of representing our community include using an official email address,
posting via an official social media account, or acting as an appointed
representative at an online or offline event.
Making a report
If you believe someone is violating the code of conduct we ask that you report it
to the django-commons CoC team by emailing [email protected].
All reports will be kept confidential. In some cases we may determine that a public
statement will need to be made. If that’s the case, the identities of all victims
and reporters will remain confidential unless those individuals instruct us otherwise.
If you believe anyone is in physical danger, please notify appropriate law enforcement
first. If you are unsure what law enforcement agency is appropriate,
please include this in your report and we will attempt to notify them.
What to include in your report
In your report please include:
- Your contact info (so we can get in touch with you if we need to follow up)
- Names (real, nicknames, or pseudonyms) of any individuals involved. If there were other
witnesses besides you, please try to include them as well.
- When and where the incident occurred. Please be as specific as possible.
- Your account of what occurred. If there is a publicly available record please include a link.
- Any extra context you believe existed for the incident.
- If you believe this incident is ongoing.
- Any other information you believe we should have.
What happens after you file a report?
You will receive an email from the Django Commons admins acknowledging
receipt as quickly as we can.
The organizers will immediately meet to review the incident and determine:
- What happened.
- Whether this event constitutes a code of conduct violation.
- Who the bad actor was.
- Whether this is an ongoing situation, or if there is a threat to anyone’s physical safety.
If this is determined to be an ongoing incident or a threat to physical safety, the
organizers’ immediate priority will be to protect everyone involved. This means we
may delay an “official” response until we believe that the situation has ended and
that everyone is physically safe.
Once the admins have a complete account of the events they will make a
decision as to how to response. Responses may include:
- Nothing (if we determine no violation occurred).
- A private reprimand from the working group to the individual(s) involved.
- A public reprimand.
- A permanent or temporary ban from Django Commons’s platforms and/or the
organization itself.
- A request for a public or private apology.
- An escalation to the Django Code of Conduct Working Group for action
within the broader Django community.
We’ll respond within one week to the person who filed the report with
either a resolution or an explanation of why the situation is not yet resolved.
Once we’ve determined our final action, we’ll contact the original
reporter to let them know what action (if any) we’ll be taking. We’ll
take into account feedback from the reporter on the appropriateness of
our response, but we don’t guarantee we’ll act on it.
Making a report to Django’s Code of Conduct Working Group
While Django Commons operates autonomously with its own Code of Conduct reporting process, reports can be made directly to the Django Code of Conduct working group
in the following scenarios:
- The report concerns a Django Commons Admin and/or CoC team.
- The Django Commons CoC team fails to respond to a report
- As a point of appeal within 30 days of the original decision
Enforcement Guidelines
Community leaders will follow these Community Impact Guidelines in determining
the consequences for any action they deem in violation of this Code of Conduct:
1. Warning
Community Impact: Use of inappropriate language or other behavior deemed
unprofessional or unwelcome in the community.
Consequence: A warning with consequences for continued behavior. No
interaction with the people involved, including unsolicited interaction with
those enforcing the Code of Conduct, for a specified period of time. This
includes avoiding interactions in community spaces as well as external channels
like social media. Violating these terms may lead to a temporary or permanent
ban.
2. Temporary Ban
Community Impact: A serious violation of community standards, including
sustained inappropriate behavior.
Consequence: A temporary ban from any sort of interaction or public
communication with the community for a specified period of time. No public or
private interaction with the people involved, including unsolicited interaction
with those enforcing the Code of Conduct, is allowed during this period.
Violating these terms may lead to a permanent ban.
3. Permanent Ban
Community Impact: Demonstrating a pattern of violation of community
standards, including sustained inappropriate behavior, harassment of an
individual, or aggression toward or disparagement of classes of individuals.
Consequence: A permanent ban from any sort of public interaction within the
community.
Reporting
Transparency reports will be published publicly on an annual basis. They will be made
available on the django-commons.org website and in this repository. These reports
should be created according to the Django Code of Conduct Working Group’s
guidelines.
Incident reports will be filed with the Django Code of Conduct Working Group according to
their guidelines.
Reports should include the date of the incident, a brief description of the facts, the
actions taken, and the outcome. Names and identifiable information should only be
included when necessary for escalation purposes.
Attribution
This Code of Conduct is adapted from the Contributor Covenant,
version 2.1, available at
https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
Community Impact Guidelines were inspired by
Mozilla’s code of conduct enforcement ladder.
For answers to common questions about this code of conduct, see the FAQ at
https://www.contributor-covenant.org/faq. Translations are available at
https://www.contributor-covenant.org/translations.
