Nyxora Sync is a learning space. People arrive with different backgrounds, languages, time zones, and confidence levels. The rules below exist so that asking a basic question never costs anyone their dignity.
Our pledge
We pledge to make participation welcoming for everyone, regardless of experience level, age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
Expected behavior
- Be respectful of differing viewpoints and experiences.
- Give specific, actionable feedback: point at the sentence or line, not the person.
- Assume good faith, then ask a clarifying question before escalating.
- Respect privacy. Do not share someone's code, error logs, or personal details without permission.
- Credit sources when you reuse an explanation, diagram, or resource.
- Accept correction gracefully. Being wrong about an API is normal; doubling down is a choice.
Unacceptable behavior
- Harassment, intimidation, stalking, or following someone across threads after they asked you to stop.
- Discriminatory jokes, slurs, or imagery, including “just a joke” versions.
- Sexual attention or advances in any community space.
- Publishing private information (doxxing), including addresses, emails, or credentials.
- Deliberate misinformation, plagiarism, or presenting someone else's project as your own.
- Spam, undisclosed promotion, recruiting, or repeated off-topic links.
- Posting malware, phishing links, or code intended to harm a reader's machine.
- Retaliating against someone who reported a problem.
Scope
This code applies in lesson discussions, the project showcase, public profiles, GitHub issues and pull requests, contact messages, and any space where you are representing Nyxora Sync.
Reporting
Report conduct problems through the contact form and choose the “Code of conduct report” topic. Include what happened, where, when, and links or screenshots if you have them. If the report involves a maintainer, say so; they will be excluded from handling it.
Reports are kept confidential within the people handling them. We will acknowledge a report as soon as we can and avoid acting on conflicts of interest. We may not be able to act on an anonymous report that lacks enough detail to identify the behavior.
For security vulnerabilities, do not open a public issue. Use the repository's security reporting flow and see the contact page for the current route.
Enforcement
Enforcement is proportional to impact and history. A typical progression:
- Correction. A private note explaining what was inappropriate and why, with a request to change the behavior.
- Warning. A recorded warning with consequences for repeating the behavior.
- Temporary ban. A time-limited removal from community spaces, with the length matched to severity.
- Permanent ban. Removal for severe or repeated violations, harassment, or retaliation.
Severe behavior can skip directly to a temporary or permanent ban. Decisions are documented so they stay consistent, and the person affected is told what happened unless doing so would expose the reporter to harm.
Attribution
This code is adapted from the Contributor Covenant, version 2.1, available under CC BY 4.0. The enforcement section is shortened for a small open-source project.