Code of Conduct
dockmesh follows a light-touch Code of Conduct based on the Contributor Covenant, simplified for a small OSS project.
Be kind. Be patient. Assume good faith. Don’t be a jerk.
Expected behavior
Section titled “Expected behavior”- Be respectful. Disagree with ideas, not people.
- Be patient. Maintainers are volunteers. Contributors may be new to Docker / Go / Svelte / open source.
- Assume good faith. If someone’s message feels off, ask for clarification before escalating.
- Stay on topic. Issues and Discussions are about dockmesh, not politics, religion, or unrelated drama.
- Give credit. Acknowledge others’ work when you build on it.
- Accept feedback gracefully. Code reviews aren’t personal attacks.
Unacceptable behavior
Section titled “Unacceptable behavior”- Personal attacks, insults, or demeaning language
- Harassment, public or private
- Discriminatory jokes or language (race, gender, sexuality, disability, etc.)
- Publishing others’ private info without permission
- Sustained disruption of discussions
- Sexual attention or advances
- Other conduct that would make a reasonable person uncomfortable
Enforcement
Section titled “Enforcement”Violations can be reported to conduct@dockmesh.dev. Reports are confidential — only the person handling the report sees them.
Responses:
| Severity | Action |
|---|---|
| Minor (unintentional, first-time) | Private clarification |
| Moderate (repeated or clearly intentional) | Public warning |
| Severe (harassment, discrimination) | Ban from the project |
Bans include GitHub repos, Discussions, and any official dockmesh community spaces.
This CoC applies in all official dockmesh spaces:
- GitHub repositories (issues, PRs, discussions)
- The official dockmesh Discord (if/when created)
- Mailing lists (if/when created)
- dockmesh-organized events (if/when held)
Interactions on private channels, personal blogs, or third-party platforms aren’t under dockmesh’s CoC — but if your behavior there spills into dockmesh community spaces, we may act on it.
Enforcement judgment
Section titled “Enforcement judgment”The maintainers have final say on CoC enforcement. We’re not perfect — if you think a decision was wrong, say so respectfully in an email to conduct@dockmesh.dev. We’ll reconsider.
Not in scope
Section titled “Not in scope”This CoC is about behavior, not opinions on technical design. You can disagree with every architectural decision dockmesh makes — that’s healthy. Disagree respectfully, with reasons.
You can also disagree with the CoC itself. Suggest changes via PR to this document.
Attribution
Section titled “Attribution”This document is adapted from the Contributor Covenant, version 2.1, simplified.
See also
Section titled “See also”- Contributing — how to contribute constructively