Code of Conduct¶
Our pledge¶
We want participating in doction to be a good use of your time, whoever you are. Everyone involved — maintainers, contributors, people filing issues — is expected to treat the others as colleagues.
Expected behaviour¶
- Assume the other person is competent and acting in good faith.
- Critique the code, the design, or the argument. Not the person.
- Accept that "no" is a complete answer to a feature request, and that a maintainer declining scope is not hostility.
- Say what you actually mean, briefly. Directness is welcome; contempt is not.
Unacceptable behaviour¶
- Harassment, insults, or personal attacks, in issues, pull requests, or commit messages.
- Demeaning comments about someone's identity, background, or level of experience.
- Sexualised language or imagery, and unwelcome sexual attention.
- Publishing someone's private information without their permission.
- Sustained disruption: reopening settled decisions to relitigate them, or demanding unpaid work from maintainers.
Scope¶
This applies in every project space — issues, pull requests, discussions, commit messages, and the security advisory channel — and to public behaviour where someone is plausibly representing the project.
Reporting¶
Report a problem privately by opening a security advisory, which is a private channel to the maintainer, or by contacting the maintainer through their GitHub profile. Reports are handled confidentially.
Do not report conduct problems in a public issue. It rarely helps the person reporting.
Enforcement¶
The maintainer decides and acts. In rough order of escalation: a private word, a public correction, editing or deleting the offending content, a temporary block, a permanent ban from the project.
Enforcement is proportionate and does not require a formal process. A single-maintainer project cannot offer an appeals board; what it can offer is that reports get read and acted on.
Attribution¶
Adapted in spirit from the Contributor Covenant, rewritten to match how this project actually operates.