81 lines
3.0 KiB
Markdown
81 lines
3.0 KiB
Markdown
# Code of Conduct
|
|
|
|
## Our commitment
|
|
|
|
Xget aims to be a welcoming, respectful, and technically constructive open
|
|
source project. Contributors, maintainers, and community members are expected to
|
|
help create an environment where people can ask questions, share ideas, and
|
|
collaborate without harassment or hostility.
|
|
|
|
## Scope
|
|
|
|
This code of conduct applies to project spaces, including:
|
|
|
|
- GitHub issues, pull requests, reviews, and discussions
|
|
- Documentation, examples, and other repository content
|
|
- Community spaces or events that are explicitly presented as part of Xget
|
|
|
|
## Expected behavior
|
|
|
|
- Be respectful and professional, even in disagreement
|
|
- Focus feedback on code, design, documentation, and behavior, not on people
|
|
- Share context, evidence, and reproduction steps when raising concerns
|
|
- Welcome contributors with different backgrounds, skill levels, and use cases
|
|
- Accept constructive feedback and course-correction gracefully
|
|
|
|
## Unacceptable behavior
|
|
|
|
- Harassment, intimidation, threats, or personal attacks
|
|
- Discriminatory or demeaning language
|
|
- Deliberate disruption, trolling, or bad-faith engagement
|
|
- Publishing private information without explicit permission
|
|
- Sexualized language or imagery in project spaces
|
|
- Repeatedly ignoring project rules, review boundaries, or moderator direction
|
|
|
|
## Enforcement responsibilities
|
|
|
|
Project maintainers are responsible for clarifying and enforcing these
|
|
standards. They may take any action they consider appropriate to protect the
|
|
community, including editing or removing content, closing discussions, rejecting
|
|
contributions, temporarily restricting participation, or permanently banning a
|
|
participant from project spaces.
|
|
|
|
## Reporting concerns
|
|
|
|
If you experience or witness behavior that violates this code of conduct, report
|
|
it privately to the maintainer using the contact information published on the
|
|
maintainer contact page:
|
|
|
|
- <https://xi-xu.me/#contact>
|
|
|
|
Please include:
|
|
|
|
- A description of what happened
|
|
- Links, screenshots, or other relevant evidence
|
|
- When and where the incident occurred
|
|
- Any immediate safety or privacy concerns
|
|
|
|
If the report concerns the current primary maintainer, use another private
|
|
contact method listed on the same contact page, or GitHub's site-wide reporting
|
|
tools when the incident took place on GitHub.
|
|
|
|
## Enforcement process
|
|
|
|
- Reports will be reviewed as confidentially as practical
|
|
- Maintainers will investigate in good faith and evaluate context carefully
|
|
- Outcomes may include a warning, content removal, temporary restriction, or
|
|
permanent ban
|
|
- Retaliation against someone for making a good-faith report is itself a code of
|
|
conduct violation
|
|
|
|
## Project responsibility
|
|
|
|
Maintainers are expected to apply this policy fairly and consistently. Not every
|
|
disagreement is a code of conduct violation, but behavior that makes the project
|
|
unsafe, exclusionary, or hostile will be addressed.
|
|
|
|
## Attribution
|
|
|
|
This document is informed by the practices recommended by Open Source Guides and
|
|
other established open source community standards.
|