Code of Conduct

Vix.cpp is a technical project built around reliability, clarity, and long-term maintainability. The community should reflect the same standards. This code of conduct applies to project discussions, issues, pull requests, reviews, documentation, community spaces, and any official Vix.cpp communication channel.

Expected behavior

Contributors are expected to communicate with professionalism and technical focus. Good participation means:

being respectful
being precise
staying on topic
reviewing code, not attacking people
giving actionable feedback
accepting corrections when needed
helping maintain a high technical standard

Disagreement is normal. Personal attacks are not.

Technical discussion

Vix.cpp welcomes serious technical debate. Strong opinions are acceptable when they are grounded in evidence, architecture, compatibility, performance, security, or developer experience. When disagreeing, focus on:

the code
the design
the tradeoff
the failure mode
the user impact
the maintenance cost

Avoid turning technical disagreement into personal criticism.

Review culture

Code review should improve the project. Review comments should be clear, specific, and actionable. Good review feedback explains:

what is wrong
why it matters
what should change
whether the issue is blocking or optional

Maintainers may reject contributions that are unfocused, unsafe, hard to maintain, or misaligned with the project direction. Rejection of a patch is not rejection of the person.

Unacceptable behavior

The following behavior is not acceptable:

personal attacks
harassment
threats
insults
discriminatory language
sexualized comments or imagery
deliberate intimidation
public or private abuse
trolling or repeated bad-faith disruption
publishing private information without permission

This applies regardless of seniority, contribution history, or technical skill.

Maintainer authority

Maintainers are responsible for protecting the quality, safety, and direction of the project. Maintainers may:

edit or remove inappropriate content
close hostile or unproductive discussions
reject contributions that violate project standards
limit participation from repeat offenders
ban contributors from project spaces when necessary

These actions are taken to protect the project and the community around it.

Reporting issues

If you experience or observe unacceptable behavior, report it privately to the project maintainers. Include relevant context:

what happened
where it happened
who was involved
links or screenshots if available
whether immediate action is needed

Reports will be handled with discretion. Do not use public issues for sensitive personal reports.

Enforcement

Enforcement depends on severity and pattern.

Possible actions include:

private clarification
public moderation
warning
temporary restriction
permanent removal from project spaces

The goal is to keep Vix.cpp serious, respectful, and productive.

Scope

This code of conduct applies in official Vix.cpp spaces and in situations where someone represents the project publicly. Examples include:

GitHub issues
pull requests
code reviews
documentation discussions
release discussions
community chat
official social channels
conference or event interactions related to Vix.cpp

Project standard

Vix.cpp should remain a place for builders who care about correctness, systems design, performance, reliability, and developer experience. Contributors are expected to help keep the project focused, professional, and welcoming to serious technical work.