Skip to content
This repository was archived by the owner on Apr 11, 2026. It is now read-only.

Latest commit

 

History

History
63 lines (41 loc) · 1.83 KB

File metadata and controls

63 lines (41 loc) · 1.83 KB

Code of Conduct

Our Standard

This project is committed to a respectful, constructive, and low-drama community.

We want draftspec to be a place where people can:

  • ask questions without embarrassment
  • give and receive technical feedback directly and kindly
  • disagree about design decisions without hostility
  • collaborate across experience levels

Expected Behavior

Examples of positive behavior include:

  • being respectful in disagreements
  • assuming good intent while still being honest
  • giving actionable feedback instead of dismissive criticism
  • welcoming newcomers and clarifying context when needed
  • focusing discussion on the work rather than on people

Unacceptable Behavior

Examples of unacceptable behavior include:

  • harassment, insults, or personal attacks
  • discriminatory or demeaning language
  • intimidation, dogpiling, or sustained hostility
  • publishing private information without permission
  • bad-faith disruption, trolling, or repeated antagonistic behavior

Scope

This Code of Conduct applies to project spaces, including:

  • issues
  • pull requests
  • discussions
  • release conversations
  • other project-linked community interactions

Reporting

If you experience or witness behavior that violates this Code of Conduct:

  • for public moderation issues, open an issue or discussion if doing so is safe
  • for private reports, contact the maintainer through GitHub

Please include as much relevant context as you can.

Enforcement

Project maintainers may remove, edit, or reject comments, issues, pull requests, or other contributions that violate this Code of Conduct.

Depending on severity, responses may include:

  • a warning
  • temporary moderation actions
  • removal from project spaces

Enforcement decisions will be made with the goal of protecting contributors and keeping the project collaborative and usable.