# Code of Conduct
RustUse expects public collaboration to stay technical, respectful, and
constructive across the canonical GitHub repository and any public mirrors.
## Expected behavior
- Focus feedback on code, docs, tests, and project direction.
- Assume good intent, but be precise when something is incorrect or risky.
- Keep review comments actionable and grounded in the code or documented policy.
- Respect different experience levels and explain constraints when rejecting an
approach.
- Preserve authorship and attribution when work is ported from mirrors.
## Unacceptable behavior
- Harassment, intimidation, or personal attacks.
- Discriminatory language or exclusionary behavior.
- Repeatedly derailing technical discussion after a decision is documented.
- Publishing private information without permission.
- Abusive behavior in issues, pull requests, discussions, release notes, or
mirror-hosted collaboration surfaces.
## Scope
This policy applies to repository discussions, issues, pull requests,
discussions, release planning, mirror-hosted collaboration tied to this
workspace, and direct maintainer interactions that are clearly about the
project.
## Reporting
Report conduct concerns privately to ferris@rustuse.org. Include links,
screenshots, or other context that will help maintainers review the report.
Do not use this channel for security vulnerabilities. Follow [SECURITY.md](SECURITY.md)
for private vulnerability reporting.
## Enforcement
Maintainers may edit, hide, lock, or remove content, or limit repository access
when behavior violates this policy. When practical, maintainers will acknowledge
reports within 3 business days and follow up after reviewing the available
context.