Skip to content

Contributing and Collaboration Policy

HybridOps is published as an evidence-backed reference implementation and product documentation. To keep releases reproducible and the verification chain stable, contribution paths are intentionally limited.

HybridOps.Core is a licensed runtime distributed as versioned release packages. Public repositories and documentation remain open for review and reuse under their stated licenses.

Contribution paths

HybridOps.Docs (documentation portal)

  • Issues: accepted (clarifications, corrections, broken links).
  • Pull requests: accepted when scoped to documentation quality and site maintenance.

HybridOps.Workloads (GitOps desired state)

  • Issues: accepted (bug reports, requests, compatibility notes).
  • Pull requests: accepted on a case-by-case basis when aligned to module contracts and when changes remain environment-neutral.

HybridOps.Core (licensed runtime)

  • Issues: accepted (defects, usability feedback, feature requests).
  • Pull requests: not accepted.

Issues and reports

When opening an issue, include:

  • A short problem statement.
  • Steps to reproduce (commands, environment assumptions, versions).
  • Expected vs observed behaviour.
  • Relevant logs or records (redact secrets).

Reuse and forks

  • Licensing is per-repository. See each repository’s LICENSE (and NOTICE where present).
  • You may fork and adapt public components under the applicable license terms.
  • Attribution is appreciated where reasonable and where the license permits.

Security

Do not disclose vulnerabilities publicly. Follow SECURITY.md for responsible reporting.

Commercial engagement

For implementation support, reviews, or delivery programmes, see: