Skip to content

Latest commit

 

History

History
80 lines (58 loc) · 2.77 KB

File metadata and controls

80 lines (58 loc) · 2.77 KB

WorkIt Code of Conduct

Purpose

WorkIt is built for professional, reliable software work. The project expects technical disagreement to stay constructive, evidence-based, and respectful.

Scope

This code of conduct applies to project spaces, including the repository, issues, pull requests, discussions, release channels, community chat, events, and any other official project forum.

Expected Behavior

  • Be respectful and direct.
  • Discuss ideas, designs, code, and evidence rather than attacking people.
  • Give and receive review feedback with care.
  • Assume good intent where reasonable, and ask for clarification before escalating conflict.
  • Respect maintainers' time, project priorities, and release boundaries.
  • Disclose conflicts of interest when they affect project decisions.
  • Keep private information private.

Unacceptable Behavior

  • Harassment, threats, intimidation, stalking, or sustained disruption.
  • Discriminatory language or conduct.
  • Sexualized language, imagery, or unwanted attention.
  • Public or private sharing of another person's private information without explicit permission.
  • Personal attacks, insults, or repeated bad-faith arguments.
  • Attempts to pressure maintainers into unsafe releases, hidden behavior, or unsupported claims.
  • Spam, coordinated manipulation, or abuse of project infrastructure.

Reporting

Report concerns through the private contact channel listed by the project maintainers. If the project is hosted on GitHub and private vulnerability or maintainer contact features are enabled, use those channels when appropriate.

Reports should include:

  • the behavior or incident being reported
  • where and when it happened
  • relevant links or screenshots, if safe to share
  • whether immediate action is needed

Maintainers should handle reports with confidentiality, minimize access to sensitive details, and avoid public disclosure unless required for safety or project integrity.

Enforcement

Maintainers may take action proportional to the behavior and risk, including:

  • a private clarification or warning
  • moderation of comments or discussions
  • temporary or permanent restriction from project spaces
  • rejection or closure of issues, pull requests, or discussions
  • escalation to platform administrators when required

Enforcement decisions should be based on observable behavior, project safety, and the need to keep collaboration productive.

No Retaliation

Retaliation against a person who reports a concern in good faith is not acceptable. Maintainers should treat retaliation as a separate conduct issue.

Maintainer Responsibility

Maintainers are responsible for applying this code consistently and for correcting their own behavior when they fall short of it.