Code of conduct.

How we treat each other in the dojo. In plain words.

Developer Dojo is free and open to everyone. This code of conduct applies to every place the dojo exists: this website, our repositories, challenge submissions, live sessions and the community space when it opens.

Our pledge

We want everyone to take part without being harassed, whatever their age, body size, disability, ethnicity, sex characteristics, gender identity or expression, level of experience, education, income, nationality, appearance, race, religion, or sexual identity and orientation, and whatever their first language.

We promise to act and interact in ways that make our community open, welcoming, diverse, inclusive and healthy.

Our standards

What we do

  • Show kindness and patience, especially to people who are new or who are still learning English.
  • Respect different opinions, viewpoints and experiences.
  • Give feedback that is specific and useful, and accept it gracefully.
  • Take responsibility for our mistakes, apologise, and learn from them.
  • Think about the whole community, not only ourselves.
  • Say honestly when we have used AI to help with our work, as The Way asks.

What we do not accept

  • Sexual language or images, and unwanted attention or advances of any kind.
  • Trolling, insulting or put-down comments, and personal or political attacks.
  • Public or private harassment.
  • Sharing other people's private information, such as an address or email, without their clear permission.
  • Passing off someone else's work as your own.
  • Anything else that a reasonable person would think is not right in a learning community.

Enforcement responsibilities

The people who run Developer Dojo are responsible for making these standards clear and for acting fairly when they are broken. They may remove, edit or reject comments, commits, issues, submissions and other contributions that do not follow this code, and will explain why when it is appropriate.

Scope

This code applies in every dojo space. It also applies when someone is officially representing the dojo in public, for example when using an official account or speaking at an event on its behalf.

Reporting a problem

If you see or experience behaviour that breaks this code, please tell us. Use the Curiosity Research Corporation contact form and start your subject with Conduct. See also our contact page. A dedicated conduct email address is coming soon.

All reports are reviewed promptly and fairly. We respect the privacy and safety of the person who reports.

Enforcement guidelines

These are the steps we follow. We pick the one that fits the harm.

1. Correction

What happened: inappropriate language or behaviour that was not welcoming. What we do: a private, written note that explains what was wrong and why. A public apology may be asked for.

2. Warning

What happened: a single serious incident, or a pattern of smaller ones. What we do: a warning with consequences if it continues. No contact with the people involved for a set time, including in shared spaces and on social media. Breaking these terms can lead to a temporary or permanent ban.

3. Temporary ban

What happened: serious breaking of community standards, including sustained inappropriate behaviour. What we do: a temporary ban from all public and private contact with the community for a set time. Breaking these terms can lead to a permanent ban.

4. Permanent ban

What happened: a pattern of breaking community standards, including harassment of a person or attacks on groups of people. What we do: a permanent ban from all public contact with the community.

Attribution

This code of conduct is adapted from the Contributor Covenant, version 2.1, which is available under the Creative Commons Attribution 4.0 International licence (CC BY 4.0). We rewrote it in plainer language and added points about learners and AI use. Community Impact Guidelines were inspired by Mozilla's code of conduct enforcement ladder, as credited by the Contributor Covenant. For answers to common questions about codes of conduct, see the Contributor Covenant FAQ at contributor-covenant.org/faq.