What we expect
- Use respectful, specific, and inclusive language.
- Assume good intent while addressing the effect of an action.
- Give feedback about the work, not a person's identity.
- Explain a problem with enough detail to help someone act on it.
- Protect schedules, credentials, and personal information.
What is not allowed
Harassment, discrimination, threats, doxxing, sexualized conduct, impersonation, and deliberate exposure of private timetable data are not allowed. Do not publish another person's private information or use project spaces to target them.
Choose the right report channel
- Use the public issue tracker for a reproducible bug or feature request. Use synthetic or redacted data.
- Use the private vulnerability form for a suspected security problem. Do not include credentials, private schedules, or personal data in a public issue.
- For a conduct concern, use the private contact listed in SUPPORT.md. Include only the details needed to review the concern.
How reports are handled
Maintainers review reports and protect reporter privacy where practical. They may remove content, limit participation, or take other action that keeps the project safe. Public explanations will not expose private schedule data or personal information.
This page follows the project's full code of conduct and the Contributor Covenant principles.