Skip to content

Latest commit

 

History

History
229 lines (151 loc) · 5.57 KB

File metadata and controls

229 lines (151 loc) · 5.57 KB

Code of Conduct

Vix.cpp Community Code of Conduct

Our Pledge

We as contributors, maintainers, and community members pledge to make participation in the Vix.cpp project a respectful, welcoming, and productive experience for everyone.

Vix.cpp is an open source project built around collaboration, technical excellence, learning, and long-term engineering quality.

We are committed to providing a community environment that is free from harassment, intimidation, discrimination, personal attacks, or abusive behavior.


Our Standards

Examples of behavior that contributes to a positive environment include:

  • being respectful and professional,
  • giving and receiving constructive feedback,
  • focusing on the technical problem instead of attacking people,
  • being patient with beginners and new contributors,
  • explaining decisions clearly,
  • accepting that different people may have different levels of experience,
  • helping improve documentation, tests, examples, and code quality,
  • recognizing the work and time of contributors.

Examples of unacceptable behavior include:

  • harassment, threats, or intimidation,
  • insults, personal attacks, or mocking,
  • discriminatory language or behavior,
  • sexualized language or unwanted attention,
  • trolling, repeated disruption, or bad-faith arguments,
  • publishing private information without permission,
  • deliberately derailing technical discussions,
  • pressuring maintainers or contributors aggressively,
  • disrespectful behavior in issues, pull requests, discussions, commits, or community channels.

Technical Discussions

Vix.cpp is a technical project. Disagreement is normal and often useful.

However, technical disagreement must remain respectful.

Acceptable:

I think this design may create a lifetime issue because the future can remain unresolved.

Not acceptable:

This code is stupid and the author clearly does not understand C++.

When reviewing code, focus on:

  • correctness,
  • safety,
  • performance,
  • maintainability,
  • clarity,
  • tests,
  • documentation,
  • compatibility.

Do not attack the contributor.


Maintainer Responsibilities

Project maintainers are responsible for clarifying and enforcing acceptable behavior.

Maintainers may take action when behavior harms the project, contributors, users, or the wider community.

Maintainer actions may include:

  • asking for clarification,
  • warning a participant,
  • editing or removing inappropriate comments,
  • closing or locking discussions,
  • rejecting contributions,
  • temporarily or permanently banning a participant from project spaces.

Maintainers should apply this Code of Conduct fairly and consistently.


Contributor Responsibilities

All contributors are expected to follow this Code of Conduct when participating in the Vix.cpp project.

This applies to:

  • GitHub issues,
  • pull requests,
  • code reviews,
  • discussions,
  • commits,
  • documentation,
  • examples,
  • benchmarks,
  • CI conversations,
  • release discussions,
  • community chats or public project channels.

Contributors should help keep discussions focused, respectful, and useful.


Reporting Problems

If you experience or witness unacceptable behavior, please report it to the project maintainers.

You may contact the maintainer at:

adastrablockchain@gmail.com

When reporting an incident, include as much relevant information as possible:

  • where it happened,
  • what was said or done,
  • who was involved,
  • links to issues, pull requests, discussions, or messages,
  • screenshots if available,
  • whether the behavior is ongoing.

Reports will be reviewed as privately and respectfully as possible.


Enforcement Guidelines

Maintainers may apply the following enforcement actions depending on the situation.

1. Correction

For minor or unintentional issues, maintainers may ask the participant to correct their behavior.

Example:

Please keep the discussion focused on the code and avoid personal remarks.

2. Warning

For repeated or more serious behavior, maintainers may issue a formal warning.

The warning may describe:

  • what behavior was unacceptable,
  • what change is expected,
  • what may happen if the behavior continues.

3. Temporary Restriction

For serious or repeated violations, maintainers may temporarily restrict participation.

This may include:

  • temporary issue or PR restrictions,
  • temporary discussion restrictions,
  • temporary removal from project communication spaces.

4. Permanent Ban

For severe, abusive, threatening, or repeated harmful behavior, maintainers may permanently ban a participant from project spaces.


Scope

This Code of Conduct applies within all official Vix.cpp project spaces.

It may also apply outside official spaces when a person's behavior directly affects the project, its contributors, its users, or its community.


Good Faith Participation

The Vix.cpp project welcomes:

  • questions,
  • bug reports,
  • feature requests,
  • documentation improvements,
  • tests,
  • examples,
  • benchmark results,
  • performance investigations,
  • design discussions,
  • constructive criticism.

Good faith participation is always welcome.

Bad faith behavior, harassment, or abuse is not.


Project Values

Vix.cpp values:

  • technical honesty,
  • careful engineering,
  • respectful collaboration,
  • reproducible benchmarks,
  • reliable CI,
  • clean APIs,
  • strong tests,
  • maintainable code,
  • open learning,
  • long-term project quality.

The goal is to build a serious C++ runtime while keeping the community healthy and respectful.


License

This Code of Conduct is provided as part of the Vix.cpp project documentation.