Skip to content

Code of conduct

When discussing implementation, reporting problems, or reviewing contributions, focus on observable behavior and evidence so people with different experience, backgrounds, and communication styles can keep collaborating.

Formal adoption of the Contributor Covenant and a private conduct-reporting contact have not yet been published. The following provides practical discussion expectations; the formal policy needs maintainer confirmation.

Make discussions easier to resolve

  • Include versions, platforms, reproductions, or specific passages so others can act on a report.
  • Explain the impact and acceptable changes in code review without judging a contributor's ability or identity.
  • When views differ, restate the problem both sides need to solve, then compare options and acceptance results.
  • Give newcomers necessary context and allow questions, corrections, and uncertainty.

Insults, harassment, discrimination, threats, disclosure of private information, and persistent personal attacks undermine collaboration. Keep technical disagreement focused on proposals.

Responding to inappropriate interactions

You can pause a conversation and retain relevant links, timestamps, and records without escalating the conflict. If you already have a private maintainer contact, ask about the appropriate reporting route. Public issues can discuss process improvements, but should not disclose affected people's identities, private messages, or sensitive incident details.

The project still needs to publish an available private conduct-reporting channel, responsible people, recusal process, and response times. The vulnerability channel is for security vulnerabilities; follow Disclosure policy for those reports.

Scope

These discussion expectations apply to issues, PRs, reviews, and community exchanges. Technical discussions can retain differing views while allowing participants to contribute and receive responses.

Formal conduct incident handling requires a private channel and responsible people. No dedicated contact is currently published; the repository's vulnerability channel continues to follow the security disclosure policy.