Be decent. Disagree on the substance. Assume good faith until you can't.
- Be specific, not personal. "This API breaks the contract on X" beats "this is bad". Critique code, not people.
- Help newer contributors land their first PR. If a contribution needs work, say what specifically and link to the relevant code or doc. Don't gatekeep with vague disapproval.
- Disagree in public, escalate privately. Technical disagreements happen on the issue or PR. Personal frictions go to eric@elizes.dev and stay there.
- No harassment. Sustained negative comments toward a person, slurs, threats, deliberate misgendering, or doxing are grounds for an immediate ban.
- Harassment, threats, or sustained personal attacks against any contributor.
- Publishing someone else's private info without consent.
- Spamming the issue tracker with unrelated content (crypto, "PR for stickers" farms, etc.).
- Posting prompt-injection bait or credential-stealing content in issues or PRs.
Bans are issued by the maintainer (Eric Elizes) and take effect immediately. There's no formal appeals process for v1; if you believe a ban was a mistake, email eric@elizes.dev with what happened and we'll talk.
For anything that needs handling outside of public issue/PR threads, email eric@elizes.dev. We will read every report and respond within a few days.