Tuskers' Code of Conduct
Tusk's Tomes is built for kitchen-table tabletop groups, and the community around it should feel like one: welcoming, generous with help, and happy to see new faces — whether you're a 20-year DM or a brand-new player opening your first terminal.
Our pledge
We — maintainers, contributors, and community members — pledge to make participation in the Tusk's Tomes project and any future community spaces (a Discord server is on the roadmap) a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
What we expect
- Be kind. Most people asking for setup help have already tried for an hour. Assume good faith.
- Be patient with newcomers. Tusk's Tomes is explicitly aimed at DMs
who've never run
git pull. If a question sounds basic, answer it graciously — that's the audience. - Be specific. "It doesn't work" is hard to help with; logs, OS, Node/Python versions, and the exact step that broke are gold.
- Disagree well. Critique ideas, not people. PR reviews and roadmap debates should leave the other person wanting to come back.
- Give credit. If someone's chronicle, glossary, or PR taught you something, say so.
What is not OK
- Harassment, insults, slurs, or personal attacks of any kind
- Sexualised language or imagery, or unwelcome sexual attention
- Doxxing, sharing other people's private information, or posting their campaign material without consent
- Sustained disruption of issues, PRs, or any future community threads
- Advocating for or encouraging any of the above
Scope
This Code of Conduct applies in all project spaces — the GitHub repo (issues, PRs, discussions, code comments), the feedback form, and any other channel that represents the project (including the community Discord once it launches — see the roadmap). It also applies when an individual is officially representing the project in public spaces.
Enforcement
Report violations through GitHub's private vulnerability reporting (repository → Security tab → Report a vulnerability) — it works for conduct reports too and keeps the report private with the maintainers. Alternatively, use the feedback form for non-sensitive concerns. Once the community Discord launches, a DM-to-a-moderator route will be added; this section will be updated to include it. All reports will be reviewed and investigated promptly and fairly.
Maintainers may take any action they deem appropriate, up to and including a permanent ban from the project and community spaces.
Attribution
Adapted from the Contributor Covenant, version 2.1.