mainarch is a technical project around low-level GPU systems work. Discussion
should stay rigorous, evidence-based, and respectful so contributors can review
unsafe kernel-facing code and public performance claims without personal friction.
- Treat other contributors with respect, including when disagreeing about design, measurements, review standards, or project direction.
- Keep technical criticism focused on code, evidence, documentation, and reproducible behavior.
- Assume public benchmark and hardware claims need clear validation and negative scope.
- Redact secrets, private hardware logs, hostnames, cluster identifiers, and other sensitive operational details from public reports.
- Harassment, threats, insults, sustained disruption, or personal attacks.
- Publishing private contact information, credentials, machine identifiers, or exploit details without consent and coordination.
- Misrepresenting validation evidence, benchmark conditions, hardware state, or dependency boundaries.
- Pressuring contributors to bypass security handling, review, licensing, or release validation.
For ordinary conduct issues, contact the maintainers privately through the repository owner or maintainer channels available on GitHub. Include the relevant links, dates, participants, and a short description of the concern.
For security-sensitive issues, use SECURITY.md instead. Do not put exploit details, private logs, credentials, or identifying host information in a public issue.
Maintainers may moderate, edit, hide, or remove comments and issues that violate this code. They may also warn contributors, close threads, restrict repository access, or decline contributions when behavior prevents safe technical review.
Enforcement decisions should be proportionate, documented to the people involved where practical, and focused on protecting the project and its contributors.