# Code of Conduct

Backuparr should be a place where anyone can ask a question, report a bug or
send a pull request without being made to feel small. Everyone started
somewhere - there's no expectation that you already know how Radarr, rclone or
Docker work. If your first instinct when someone asks a basic question is to
make yourself look clever rather than make them feel helped, this isn't the
place for you.

## What we expect

- **Be kind and generous.** Assume good intent, help people get unstuck, and
  keep an open mind about approaches you wouldn't have taken.
- **Disagree about ideas, not people.** Argue about designs, defaults and
  trade-offs as much as you like. Criticism of the project and its maintainers
  is welcome too - tell us when something is broken, confusing or just bad.
- **Stay on topic and in good faith.** No spam, self-promotion, trolling or
  deliberately misleading advice.

## Zero tolerance for bigotry

This project will not tolerate bigotry or harassment of any kind. That
includes slurs, "jokes", dog whistles and demeaning comments targeting anyone's
age, body, disability, ethnicity, gender identity or expression, nationality,
neurodiversity, race, religion, sex, sexual orientation, socioeconomic status
or level of experience.

People's identities and their right to exist are not up for debate here.
Framing bigotry as "just an opinion", "free speech" or "just asking questions"
doesn't change what it is.

## Where this applies

Everywhere in the project: issues, pull requests, reviews, discussions, commit
messages, and anywhere someone is representing Backuparr. How much you've
contributed doesn't exempt you.

## Reporting

Email **conduct@tripplehelix.net**. Reports are read by the maintainer and kept
confidential. You can also use GitHub's **Report content** option on any
issue, pull request or comment.

## Enforcement

- **Bigotry, harassment or doxxing:** the content is removed and the person is
  permanently blocked from the project. There's no warning first.
- **Anything else in this code:** a private word the first time, a public
  warning the second time, and a block the third time.

The maintainer has the final say on what crosses the line, and may remove,
edit or reject comments, commits, issues and pull requests that don't follow
this code.