Contributing
OpenDome’s open core is Apache-2.0 and built in the open. Contributions to the platform, the spec and the docs are welcome.
The canonical contributor guide is
CONTRIBUTING.md
in the repository — dev setup, the merge-request workflow and the CI gates live
there. The essentials are below.
Where things live
Section titled “Where things live”- Platform (cells, OSL engine, connectors, charts, orchestration) —
gitlab.com/opendome.eu/platform, Apache-2.0. Issue and MR templates are provided; usage questions go through the Question template (seeSUPPORT.md). - OSL spec —
spec/osl/in the same repository. Changes follow the RFC process. - These docs — summaries that link out to the repository docs
(
docs/,docs/osl/), which are the engineering source of truth.
Ground rules
Section titled “Ground rules”- OSS never references our private domains. A self-hoster exposes the cell
however they like; the open source carries no
opendome.eu-specific assumptions. - Additive, versioned changes. Don’t break existing YAML or API contracts — extend them. Removals wait for a major version.
- Pin versions. No floating
:latesttags anywhere — images, charts and deps pin to concrete stable versions.
Spec changes
Section titled “Spec changes”RFC processPropose a change to the OSL spec — problem, alternatives, impact, rollback, and sign-off.
Reporting security issues
Section titled “Reporting security issues”Do not open a public issue for a vulnerability. Follow
SECURITY.md:
a GitLab confidential issue is the preferred channel, with
security@opendome.eu as the email alternative. See also the
Security posture page.