# Code of Conduct

## The short version

Be decent to people. Assume the person you are replying to is competent and
acting in good faith until they show you otherwise.

## What this means in practice

Most friction in an open source project is not abuse, it is carelessness, so
this is written about the ordinary cases rather than the dramatic ones.

**Do:**
- Critique the code. "This breaks on empty input" is useful. "This is
  garbage" is not, and it is not more honest, only louder.
- Assume the contributor knows something you do not. They usually ran it on
  hardware you do not have.
- Say when you are guessing. A confident wrong answer costs a stranger hours.
- Accept that a maintainer may decline your patch. A repo is not obliged to
  merge everything correct.

**Do not:**
- Harass anyone, publicly or privately.
- Bring someone's identity — nationality, gender, religion, employer,
  fluency in English — into a technical discussion. Nunba has contributors
  and users across many languages; poorly-worded English is not a defect in
  the person.
- Reopen a settled decision by relitigating it in every subsequent thread.
- Post someone's private information.

## Scope

Applies in this repository, in issues and PRs, and anywhere someone is
representing the project.

## Enforcement

Report to **conduct@hertzai.com**. Reports go to the maintainers and are not
shared further without your agreement.

We will respond, and the response will be proportionate: usually a private
word, sometimes an edited or removed comment, and in serious or repeated
cases a ban. We will tell you what we did. We will not pretend a report was
handled when it was not.

If a maintainer is the problem, say so in the report. It will be handled by
someone else.