Alexandre Teixeira
a0137b47d1
Adapt the agreed maintainer responsibilities and risk-based review policy for the public repository. Add evidence-driven security review, CodeQL triage, release guidance and a discoverable contributing link.
2.3 KiB
Code of Conduct
Odysseus project spaces should remain respectful, useful, and focused on the project. Technical disagreement is welcome; personal hostility is not.
Expected conduct
- Be professional and constructive. Critique ideas, evidence, and implementations, not people.
- Treat people fairly regardless of experience, background, identity, or role.
- Explain disagreement with reproducible evidence when possible, and acknowledge uncertainty.
- Keep project spaces relevant to Odysseus, software engineering, AI, and project work.
- Help de-escalate discussions that stop being productive, and respect moderation decisions while they are reviewed.
Unacceptable conduct
- Harassment, discrimination, threats, intimidation, or personal attacks.
- Trolling, baiting, sustained disruption, or targeted hostility.
- Doxxing, publishing private correspondence or personal information without permission.
- Political campaigning, ideological or culture-war disputes, and repeated highly polarizing arguments unrelated to project work.
- Retaliation against someone who reports a concern in good faith.
These expectations apply to everyone, including administrators and maintainers. Disagreeing about project decisions or criticizing code in good faith is not a violation.
Scope
This applies across official Odysseus spaces, including GitHub, Matrix, Plane, maintainer channels, and other project-managed community spaces, and to representatives acting on the project's behalf.
Reporting and enforcement
Report conduct concerns to a Repository Admin or Organization Owner using an appropriate project communication channel. For sensitive concerns, ask for a private channel rather than posting personal details publicly. Security vulnerabilities follow SECURITY.md, not the public conduct-reporting process.
Maintainers may redirect or pause unproductive conversations. Repository Admins handle serious moderation or access decisions, consulting others when appropriate and avoiding conflicts of interest.
Actions may include a reminder, warning, temporary restriction, removal from project spaces, or removal of elevated access. Responses should be proportionate to the behavior and circumstances, with privacy respected and an opportunity to provide context where practical. Retaliation is prohibited.