Skip to content

Community, support, and project decisions

Kuration is developed in the open. Use the repository's issue tracker for reproducible bugs, documentation problems, and scoped feature proposals. Use GitHub Discussions only if it is enabled for the repository (it is not at the moment); otherwise start with an issue.

Read the repository policies before opening a report:

  • Support policy — supported questions, information to include, and response expectations.
  • Contributing guide — development setup, extension boundaries, tests, and pull-request requirements.
  • Governance — how maintainers make compatibility and roadmap decisions.
  • Security policy — the private vulnerability-reporting path and runtime trust boundaries.

Do not include credentials, private datasets, unreleased vulnerability details, or proprietary logs in a public issue. Reduce examples to synthetic data whenever possible.

The documentation published from main describes the next release. A packaged release's API and compatibility contract is the documentation at its Git tag; release notes identify migrations and deprecations between versions.