Skip to content

CODE_OF_CONDUCT.md

Latest commit

 

History

History
78 lines (60 loc) · 3.42 KB

CODE_OF_CONDUCT.md

File metadata and controls

78 lines (60 loc) · 3.42 KB
Raw

Code of Conduct

Database Tycoon is a small team, and this is a public project. It only works if people feel comfortable showing up: asking a basic question, filing a rough bug, disagreeing about a design. This document is the short version of how we keep it that way. It applies to everyone who shows up in an issue, a pull request, or a discussion.

What we expect

Assume the person on the other end is smart and acting in good faith, even when they're new, even when they're wrong. Be direct about the work without being sharp with the person. Concretely, that means:

  • Give feedback on the code, the idea, or the decision — not the human.
  • Take disagreement as normal. Explain your reasoning; accept that someone might explain theirs back.
  • When you're wrong, say so and move on. Nobody here is keeping score.
  • Make room for people who know less than you do. You were there once.

What we won't accept

  • Harassment of any kind, public or private.
  • Sexualized language, imagery, or attention.
  • Personal, political, or identity-based attacks — insults or dismissiveness aimed at who someone is rather than what they said.
  • Trolling, deliberate derailing, or sustained disruption.
  • Publishing someone's private information without their explicit permission.
  • Anything else that a reasonable person would read as harassment in a professional setting.

This applies 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 orientation.

Where this applies

Everywhere the project lives — issues, pull requests, discussions, commit history — and anywhere someone is representing the project in public, like an official account or an event.

Reporting

If something crosses a line, tell us. Email info@databasetycoon.com with what happened. You don't need to have it perfectly documented; send a rough account and we'll take it from there.

We'll look into every report promptly and fairly, and we'll keep the reporter's identity private. Reporting something in good faith will never count against you, full stop.

What happens after a report

Maintainers are responsible for enforcing this, and we'll match the response to what actually happened:

  1. A quiet word. For a one-off — language or behavior that was out of line but not serious — a private note explaining what was wrong and why. Sometimes with a request to apologize.
  2. A warning. For a clearer violation or a repeat: a warning, plus a period of no interaction with the people involved, across project spaces and outside them. Ignoring that leads to a ban.
  3. A temporary ban. For a serious violation or sustained bad behavior: time away from all project interaction. Breaking the terms of the ban makes it permanent.
  4. A permanent ban. For a pattern of violations, harassment of an individual, or hostility toward a group.

We'll explain our reasoning when it makes sense to, and we'll act consistently whether the person involved is a first-time contributor or a maintainer.

Attribution

Adapted from the Contributor Covenant, version 2.1. The enforcement tiers draw on Mozilla's code of conduct enforcement ladder. For common questions, see the Contributor Covenant FAQ.