Skip to content

Latest commit

 

History

History
51 lines (38 loc) · 2.25 KB

CODE_OF_CONDUCT.md

File metadata and controls

51 lines (38 loc) · 2.25 KB

Code of conduct

What this is

A short statement of how people are expected to treat each other in this repository's issues, discussions, and pull requests. It is not a legal document and there is no committee behind it; the maintainers apply it directly.

Expected behaviour

  • Discuss code and decisions, not people. "This allocates on the paint path" is useful; "you clearly do not understand performance" is not.
  • Assume the other person is trying to make the project better. Most disagreements here are about a tradeoff, and a tradeoff stated plainly is easier to settle than one argued about.
  • Say what you measured. A claim about speed, size, or platform behaviour carries much more weight with the machine, the build mode, and the method attached.
  • Accept that a maintainer may say no. Viva has a stated scope, a set of performance budgets, and a framework-versus-application boundary; a change can be declined because it does not fit them, and that is not a judgement about you.
  • Be patient with people working in a second language, on an unfamiliar platform, or in a timezone that is not yours.

Unacceptable behaviour

  • Harassment, insults, and personal attacks, in public or in private.
  • Discriminatory comments about who someone is.
  • Sexualised language or imagery, and unwelcome attention of that kind.
  • Publishing someone's private information without their consent.
  • Deliberately wasting reviewers' time: argument for its own sake, or reopening a settled decision without new information.
  • Sustained disruption of a discussion after being asked to stop.

Scope

This applies in the repository's issues, pull requests, discussions, and commit messages, and in any space where someone is representing the project.

Reporting

Tell a maintainer privately — through their GitHub profile rather than a public thread. Reports are handled as confidentially as the situation allows.

Maintainers may edit or delete a comment, close a thread, or block an account, in proportion to what happened. Someone asked to stop a behaviour is expected to stop it; continuing is treated as a separate problem.

Attribution

This is written for this project rather than adopted from a template. It does not require a signature or an acknowledgement to participate.