Specification repository

Code of Conduct

Our Commitment#

We are committed to making participation in this project a respectful, harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socioeconomic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.

We commit to acting and interacting in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.

Expected Behavior#

Examples of behavior that contributes to a positive community include:

  • demonstrating empathy and respect toward other people;
  • giving and accepting constructive technical feedback;
  • focusing disagreement on observable behavior, evidence, and interoperability;
  • acknowledging mistakes, correcting them, and learning from the experience;
  • respecting privacy, confidentiality, and responsible disclosure boundaries;
  • prioritizing the health of the project and community over individual preferences.

Unacceptable Behavior#

Unacceptable behavior includes:

  • sexualized language, imagery, attention, or advances;
  • trolling, insults, derogatory comments, or personal or political attacks;
  • public or private harassment, intimidation, or threats;
  • publishing another person's private information without explicit permission;
  • impersonation or deliberate misrepresentation of another contributor;
  • knowingly submitting credentials, private data, malicious content, or undisclosed security exploits;
  • sustained disruption of reviews, issues, discussions, or project operations;
  • other conduct that could reasonably be considered inappropriate in a professional setting.

Good-faith disagreement about specification design is not harassment. It must remain relevant, evidence-based, and respectful.

Scope#

This code applies in repository issues, pull requests, reviews, discussions, commits, automation, and other project spaces. It also applies when someone officially represents the project in public or private spaces.

Automated agents and their operators are subject to the same standards. The human directing an agent is responsible for its project interactions.

Reporting#

Report conduct concerns privately to the repository maintainers using a private contact method listed on their GitHub profiles. Do not disclose sensitive report details in a public issue. If no safe maintainer contact is available, use GitHub's abuse reporting tools.

Reports should include the relevant URLs, dates, participants, description, and any supporting evidence. Maintainers will protect the reporter's privacy as far as reasonably possible and will disclose information only as needed to evaluate and address the report. Knowingly false or retaliatory reports violate this code.

Enforcement#

Maintainers are responsible for clarifying and enforcing these standards. They may remove, edit, or reject comments, commits, code, issues, and other contributions that violate this code.

Responses will be proportionate to the behavior, context, impact, and history:

  1. Correction: private explanation and request to correct the behavior.
  2. Warning: formal warning with conditions for continued participation.
  3. Temporary restriction: time-limited restriction from project interaction.
  4. Permanent restriction: permanent removal from project participation.

Immediate restriction may be used for credible threats, severe harassment, exposure of private information, malicious activity, or risks to participant safety. Retaliation against a reporter or participant in an investigation is prohibited.

Maintainers involved in a report must recuse themselves when reasonably possible. Enforcement decisions and appeals should be reviewed by an uninvolved maintainer. If none is available, the remaining maintainers will document and manage the conflict as transparently as privacy permits.

Attribution#

This code is adapted from the Contributor Covenant, version 2.1.