# Horosa Code of Conduct

中文说明：[CODE_OF_CONDUCT_ZH.md](CODE_OF_CONDUCT_ZH.md)

This project is being prepared for a formal open-source release. We want Horosa to be a serious, welcoming, technically rigorous place to collaborate.

## Our Pledge

We pledge to make participation in the Horosa community a respectful, professional, and harassment-free experience for everyone, regardless of background, level of experience, identity, discipline, or viewpoint.

We especially expect contributors to:

- disagree with precision instead of contempt
- review work honestly without humiliation
- treat private charts, user data, screenshots, logs, and API credentials with care
- explain tradeoffs instead of escalating avoidable conflict

## Expected Standards

Examples of behavior that help create a healthy project:

- giving clear, reproducible bug reports
- leaving constructive and technically specific review feedback
- documenting assumptions, risks, and migration impact
- being welcoming to beginners without lowering quality standards
- being respectful toward domain experts, researchers, and maintainers

## Unacceptable Behavior

- harassment, threats, intimidation, or personal attacks
- insulting, dismissive, or demeaning language
- publishing private charts, private user data, API keys, or internal logs without permission
- misrepresenting test results, release status, compatibility, or security posture
- deliberately derailing collaboration, review, or incident handling

## Scope

This Code of Conduct applies to:

- repository discussions
- issues and pull requests
- code review threads
- release planning and documentation review
- linked collaboration spaces used for Horosa maintenance

## Maintainer Responsibilities

Maintainers are expected to:

- apply this policy consistently
- protect reporters from retaliation where reasonably possible
- intervene early when conduct issues begin to affect collaboration
- favor clear boundaries, de-escalation, and documented decisions

## Reporting

Conduct concerns can currently be reported to:

- Primary conduct contact: `maxwelldhx@gmail.com`
- Backup maintainer contact: open a private maintainer message through the published repository support path in [SUPPORT.md](SUPPORT.md)

## Enforcement

Maintainers may remove comments, pause review threads, close contributions, or restrict participation when behavior violates this policy. Repeated or severe violations may lead to loss of collaboration access.

## Attribution

This document follows the structure commonly used by mature open-source communities and is tailored to Horosa’s product, privacy, and research context.