Skip to content

Latest commit

 

History

History
63 lines (46 loc) · 3.04 KB

File metadata and controls

63 lines (46 loc) · 3.04 KB

Code of conduct

The short version

Be decent to people. Argue with the work, not the person. Assume the other party is trying.

Scope

This applies in the issue tracker, pull requests, discussions, commit messages, and any other space that belongs to this project, plus anywhere someone is representing the project in public.

What is expected

  • Criticize the artifact. "This benchmark does not support that claim" is exactly the contribution this project wants. "You are incompetent" is not the same sentence and does not carry the same information.
  • Be specific enough to be checkable. A disagreement with a file and a line in it can be settled. One without cannot.
  • Take the correction. When you are shown to be wrong, say so and move on. This repo's own documentation retires its own headline claim, so nobody here gets to treat being wrong as an insult.
  • Respect a "no." A maintainer declining a feature is a scoping decision, not a personal one.

What is not acceptable

  • Harassment, whether public or private. Sexual attention or advances of any kind.
  • Insults, slurs, or demeaning comments, including about someone's identity, nationality, background, experience level, or the tooling they use.
  • Publishing anyone's private information without their explicit permission.
  • Sustained disruption: reopening settled decisions to wear people down, or escalating a technical disagreement into a personal one.
  • Using an issue or PR to advertise something unrelated.

AI-assisted contributions are welcome and do not need a disclaimer. What is not acceptable is submitting output you have not read. If you cannot answer a question about a diff you opened, that is the problem, not the tool that produced it.

Reporting

Report a concern through GitHub's private reporting form, which is private until published, or by opening an issue titled conduct contact request with no detail in it, and you will be given somewhere private to write.

Be aware of who you are reporting to. This project has a single maintainer, so a report about the maintainer goes to the maintainer. That is a real limitation and worth stating rather than papering over: if that is not acceptable for your situation, GitHub's own abuse reporting is independent of this repo and is the right channel.

Reports are handled privately. The reporter's identity is not shared without their consent.

Consequences

The maintainer may edit or delete comments, close issues or PRs, and block accounts, in proportion to what happened and with a stated reason. A first, isolated lapse usually gets a warning. Harassment and deliberate disruption do not need one.

Attribution

Written for this project rather than adopted wholesale. It borrows the scope and enforcement structure of the Contributor Covenant v2.1 without inheriting its text, so the wording above is the actual policy and there is no second document to consult.