Skip to content

Latest commit

 

History

History
70 lines (53 loc) · 2.98 KB

CODE_OF_CONDUCT.md

File metadata and controls

70 lines (53 loc) · 2.98 KB

Code of Conduct

Status: draft for the technical preview.

Our commitment

Everyone who takes part in OperateBench — contributing, reviewing, reporting a defect, or arguing that the construct is wrong — should be able to do so without harassment, and should expect to be judged on the substance of their work.

We want this project to be a place where "your benchmark does not measure what you claim" is a normal, welcome sentence, said and received without personal attack in either direction.

Expected behaviour

  • Engage with the argument, not the person making it.
  • Give and accept technical criticism directly and specifically. A rejected design is not a rejected contributor.
  • Say what you actually think about evidence, including when it undercuts the project's own claims.
  • Be explicit about uncertainty rather than confident by default.
  • Respect other people's time: search first, include reproduction steps, keep scope tight.
  • Assume good faith, and ask before concluding someone acted badly.

Unacceptable behaviour

  • Harassment, intimidation, stalking or sustained disruption.
  • Insults, demeaning comments, or attacks based on personal characteristics — including age, disability, ethnicity, gender identity or expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
  • Sexualised language, imagery or attention in any project space.
  • Publishing someone's private information without their explicit permission.
  • Deliberately submitting content the contributor knows to be non-synthetic, personal or proprietary, or knowingly misrepresenting evidence, provenance or results.
  • Retaliation against anyone who raises a concern in good faith.

Scope

This applies in all project spaces — the repository, issues, pull requests, discussions and reviews — and when someone is representing the project in public.

Reporting and enforcement

Report to dmitry@dwelly.group. Reports are handled confidentially, and the reporter's identity is not shared with the person reported without the reporter's consent.

Reports are acknowledged within 3 working days where possible. A maintainer with a conflict of interest in a report — including one who is its subject — recuses themselves from handling it.

Responses are proportionate, and typically escalate: a private explanation of what was wrong; a warning; a temporary restriction from project spaces; or a permanent ban. Where a response is applied, the reasoning is recorded, and the person affected can respond.

Governance during the preview is small and informal: Dwelly is the initial steward and currently makes these decisions. That is stated plainly rather than dressed up as a committee, and it will be revisited if the project grows.

Attribution

This document is adapted in spirit from the Contributor Covenant, version 2.1. It is not a verbatim copy, and the Contributor Covenant text at that link governs its own use.