Skip to content

CODE_OF_CONDUCT.md

Latest commit

 

History

History
59 lines (43 loc) · 2.26 KB

CODE_OF_CONDUCT.md

File metadata and controls

59 lines (43 loc) · 2.26 KB
Raw

Code of Conduct

Luotsi is intended to stay boring to operate and boring to collaborate on. The goal of this repository is a technical, respectful, low-drama working environment for users, contributors, and maintainers.

Expected behavior

  • Be respectful, precise, and constructive in issues, pull requests, reviews, docs, and other project spaces.
  • Focus criticism on code, behavior, evidence, and outcomes rather than on people.
  • Assume good intent first, then ask for clarification when something is ambiguous.
  • Protect other people’s privacy and device, log, and screenshot data.
  • Keep discussions scoped to the work at hand; prolonged personal arguments, dogpiling, and bad-faith escalation are not acceptable.

Unacceptable behavior

  • Harassment, intimidation, threats, stalking, or unwanted sexual attention.
  • Discriminatory or demeaning language or conduct based on personal identity or protected characteristics.
  • Doxxing, sharing private information, or reposting private communications without permission.
  • Deliberate disruption of project discussions, reviews, or issue triage.
  • Bad-faith technical review, sealioning, or repeated hostile engagement after a maintainer asks for a discussion to stop or move.

Scope

This code of conduct applies to repository spaces such as issues, pull requests, reviews, discussions, release comments, and documentation changes. It also applies when someone is representing the project in adjacent public spaces.

Reporting

Report conduct concerns privately to the maintainers instead of opening a public issue.

Until a dedicated conduct mailbox is published, use GitHub private reporting:

If the report is not a security issue, say so clearly in the first line and it will be handled as a conduct report instead.

Maintainers will keep reports as private as practical, acknowledge receipt, review the available evidence, and decide on an appropriate response.

Enforcement

Maintainers may remove content, pause threads, reject contributions, or temporarily or permanently restrict participation when behavior violates this code of conduct.

Enforcement decisions are intended to protect the working environment of the project, not to win arguments.