Good Citizen Guide

Technical communities succeed or fail on culture. This guide explains what we expect from everyone who participates — not as a legal agreement, but as a shared understanding of how to make this space work for everyone, including you.

Core expectations

These apply in every context: issue tracker, pull requests, documentation edits, and any other Nyxever-affiliated space.

  • Engage in good faith. Assume people are here to learn or contribute, not to waste your time. If something looks wrong, ask before assuming the worst.
  • Be direct, not dismissive. Disagreement is fine. "That approach won't work because X" is useful. "That's obviously wrong" is not. The difference is whether you help the other person move forward.
  • Share what you know. If you solved a problem, write it down somewhere others can find it. The work you did to figure something out has value that doesn't disappear once you know the answer.
  • Give credit. If you build on someone else's work, configuration, or documentation, say so. Attribution costs nothing and matters to people.
  • Respect different contexts. A startup with three people and a 15-year-old enterprise running SAP on bare metal have genuinely different constraints. Advice that ignores context is rarely useful.
  • Acknowledge when you don’t know. "I'm not sure, but here's what I'd try" is more useful than confident-sounding guesses that send someone in the wrong direction for an afternoon.

Contributing effectively

A contribution doesn't have to be code. Documentation improvements, bug reports with enough context to reproduce, and well-formed questions that expose gaps in existing documentation all move the project forward.

  • Read before opening an issue. Check whether your question or bug has been reported already. Duplicate issues fragment discussion and take time to triage.
  • Provide context in bug reports. What environment, what version, what you did, what you expected, what actually happened. A report without reproduction steps is much harder to act on.
  • Read the architecture decisions first. The ADR directory documents decisions and their reasons. A proposal that contradicts an ADR without acknowledging it will need to address the underlying reasoning — not just the conclusion.
  • Scope your pull requests. A PR that fixes one thing is easier to review than a PR that fixes four. Small, focused changes land faster and are easier to revert if something goes wrong.
  • Write commit messages that explain the why. The diff shows what changed. The commit message should explain why it needed to change.
  • Don’t add features that aren’t asked for. If you fix a bug and notice something adjacent that could be improved, open a separate issue. Bundling unrelated changes makes code review harder and authorship blurry.
On documentation If a section of the Nyxever docs doesn't explain the why — only the how — that's a documentation bug worth filing. Infrastructure decisions without context become cargo cult configurations over time. Clear documentation that builds understanding is one of the most valuable contributions you can make.

What we don’t tolerate

Most of what makes a community work is described above. The things that break communities are worth naming directly.

  • Harassment, personal attacks, or targeted hostility of any kind
  • Dismissing questions because the answer seems obvious to you — it wasn't obvious before you knew it
  • Promoting products, services, or consulting offers without genuine contribution first
  • Misrepresenting your experience, credentials, or affiliation
  • Posting content that would create legal exposure for the project (unlicensed code, defamatory claims, intentional misinformation)
  • Dogmatic advocacy — treating a technology choice as a moral position and dismissing anyone who disagrees

Moderation in a small community is informal. If something is going wrong, say so — directly if appropriate, or by using the contact form. Patterns that persist will result in removal from the space.


Terms of Use

By using Nyxever software, documentation, or community spaces, you agree to the following terms. These are written plainly. If something is unclear, ask.

Provided as-is

Nyxever software and documentation are provided as-is, without warranty of any kind, express or implied. This includes, but is not limited to, warranties of merchantability, fitness for a particular purpose, accuracy, and non-infringement. The authors and contributors are not liable for any claim, damage, or other liability arising from your use of or reliance on anything published under the Nyxever name.

You are responsible for evaluating whether Nyxever is appropriate for your use case, validating configuration in your specific environment, and maintaining backups and recovery procedures for your own infrastructure.

License

The license for Nyxever software is to be determined. Until a license is formally declared in the repository, no rights to reproduce, distribute, or create derivative works are granted beyond personal evaluation and contribution to the project. If you need clarification for a specific use case, use the contact form.

Contributions

By submitting a contribution (code, documentation, configuration, or other content) to any Nyxever project, you confirm that you have the right to submit it, that it does not knowingly infringe any third-party rights, and that the project may use it under whatever open-source license is ultimately adopted for the project.

Community spaces

Participation in Nyxever community spaces (issue trackers, repositories, and any future forums or channels) is subject to the conduct expectations described in this document. The maintainers reserve the right to remove content or users that violate those expectations, at their discretion.

Changes to these terms

These terms may change as the project matures. Material changes will be noted in the project changelog. Continued use after changes are published constitutes acceptance. If you disagree with a change, the appropriate response is to stop using the project and, if you like, to say why in the issue tracker.

This is not legal advice These terms are written in plain language and intended to be understood by the people using this project. They are not a substitute for legal counsel if you are deploying Nyxever in a regulated environment or making significant business decisions based on it. Verify with a qualified professional as appropriate.