We want AsterDrive to be a professional, technically focused, and welcoming project for contributors, users, and maintainers.
Examples of behavior that help build that environment include:
- being respectful in technical discussion, even when disagreeing
- giving feedback that is specific, actionable, and tied to the work
- assuming good intent before escalating conflict
- being considerate of different experience levels, backgrounds, and communication styles
- respecting privacy, boundaries, and project security practices
- keeping discussions on-topic in issues, pull requests, discussions, review comments, and other project spaces
The following behavior is not acceptable in this project or its community spaces:
- harassment, discrimination, or hateful conduct of any kind
- personal attacks, insults, intimidation, threats, or sustained hostility
- sexualized language, unwanted sexual attention, or inappropriate imagery
- trolling, baiting, deliberate provocation, or repeatedly derailing conversations
- doxxing or sharing someone else's private information without explicit permission
- impersonation, fraud, or intentionally misleading other contributors or users
- spam, abusive advertising, or unrelated self-promotion
- encouraging or coordinating harmful behavior against individuals or the project
- any conduct that would reasonably make participation unsafe, hostile, or exhausting
This Code of Conduct applies to:
- GitHub issues, pull requests, discussions, review comments, and wiki or documentation contributions
- project chat, email, and other communication channels used for AsterDrive collaboration
- public spaces where someone is representing the project, its maintainers, or its community
If you experience or witness behavior that violates this Code of Conduct, report it to:
report@esaps.net
Please include relevant context when possible, such as links, screenshots, timestamps, and a short description of what happened.
For safety and privacy reasons, do not use public GitHub issues or discussions to report conduct incidents involving harassment, abuse, or private information.
Project maintainers are responsible for reviewing reports and deciding an appropriate response.
Possible actions include:
- asking for a change in behavior
- editing or removing comments, posts, or other content
- locking threads or ending discussions
- rejecting contributions associated with the behavior
- temporary suspension from project spaces
- permanent ban from participation in project spaces
Maintainers will review reports in good faith, aim to protect affected people, and handle personal information as confidentially as reasonably possible.
When evaluating a report, maintainers will consider:
- the severity of the behavior
- whether the conduct was repeated or targeted
- the impact on community safety and collaboration
- whether an immediate protective action is necessary
This document was written for AsterDrive and was informed by common open source community moderation practices, including Contributor Covenant.