Skip to content

CODE_OF_CONDUCT.md

Latest commit

 

History

History
63 lines (42 loc) · 2.18 KB

CODE_OF_CONDUCT.md

File metadata and controls

63 lines (42 loc) · 2.18 KB

Code of Conduct

Purpose

mikuproject aims to be a respectful and practical collaboration space for bug reports, feature requests, design discussion, documentation work, and code contributions.

The goal is not to avoid disagreement. The goal is to keep discussion specific, constructive, and safe for participants.

Expected Behavior

  • Be respectful.
  • Be specific.
  • Prefer concrete repro steps, fixtures, examples, and tests over vague claims.
  • Critique ideas, code, assumptions, and designs without attacking people.
  • Keep technical disagreement focused on behavior, tradeoffs, and evidence.
  • Accept that maintainers may ask to narrow scope, add tests, or clarify intent before accepting a change.

Unacceptable Behavior

  • Harassment, intimidation, or personal attacks
  • Discriminatory, hateful, or abusive language
  • Repeated hostile or bad-faith argument
  • Dismissing or insulting contributors instead of addressing the technical point
  • Publishing private or sensitive information without permission
  • Spam, trolling, or deliberately disruptive behavior

Scope

This code of conduct applies to project spaces such as:

  • Issues
  • Pull requests
  • Discussions and review comments
  • Documentation contributions
  • Other project-related public collaboration spaces managed for mikuproject

Maintainer Responsibility

Project maintainers may moderate discussions and contributions to keep the project usable and collaborative.

This may include:

  • Asking for clarification or tone adjustments
  • Hiding, editing, locking, or closing discussions when appropriate
  • Rejecting contributions that are technically unsuitable or behaviorally disruptive
  • Limiting further participation in project spaces if necessary

Reporting

If you experience or observe behavior that should be addressed, contact the project maintainer through a project channel that is appropriate for the situation.

If a public thread would make the issue worse, prefer a private contact path instead of escalating in public.

Project Style

For mikuproject, the preferred collaboration style is:

  • specific
  • respectful
  • test-oriented
  • focused on reproducible behavior

Technical rigor is welcome. Personal hostility is not.