A short preface
People will disagree here. That's the point. A body of knowledge gets better when someone says "I don't think that's right" and explains why.
So argue with ideas, never with people. Assume the other person knows something you don't. Someone new to the work deserves the same patience you'd want.
What we adopt
We adopt the Contributor Covenant, version 2.1 in full, by reference. Its pledge, standards, enforcement responsibilities and enforcement guidelines all apply. We don't paraphrase it here, so there's only one text to read.
The Contributor Covenant is by Coraline Ada Ehmke and contributors, and is licensed under CC BY 4.0.
Where it applies
Everywhere the practice lives:
- the GitHub repository: issues, discussions, pull requests and reviews;
- the LinkedIn group;
- the site's comment address;
- any event or call held in the practice's name.
Two additions for this practice
These sit alongside the Covenant. They come from the kind of work we do.
- No one else's secrets. Don't share confidential information from an employer, client or vendor, and don't press others to. Asking "can you share the real number?" is out of bounds. See HOW_IT_GROWS.md.
- No selling. Don't use the practice's spaces to pitch products, services or yourself for hire. Sharing your public work when it's relevant is fine.
Reporting
Write to cpp@anacay.org with "Conduct" in the subject. Conduct reports are handled only by the people who enforce this code. If your report involves one of them, say so, and it will go to someone else. For now the founder is the only editor and handles reports himself. A report about him can go to GitHub instead, with Report content on the post or comment. EDITORS.md explains this, and names an independent reviewer once there is one.
Reports are kept confidential. We'll reply to say we got it, and act following the Covenant's enforcement guidelines: correction, warning, temporary ban or permanent ban.