Open-source project

Improve the
whole system.

Cix welcomes bug reports, documentation improvements, tests, and code contributions. Start with the public source mirror, read the project rules, and choose a change you can verify.

Contribution path

Make a change that can land.

Cix is maintainer-led. A useful contribution includes the evidence, documentation, and tests needed to understand its effect on the API and the machine. Public questions and non-sensitive bug reports belong in the issue tracker.

01 / Understand

Read before changing.

Read the contribution guide and the relevant guide or ADR. The API-first boundary matters: update OpenAPI before clients.

Contribution guide ↗
02 / Propose

Report the real problem.

Use the issue tracker for a focused bug, documentation gap, test improvement, or design question. Include the version, source revision, reproduction, and expected result.

Open issues ↗
03 / Implement

Keep the contract visible.

Make the smallest coherent change, update tests and documentation with it, and avoid credentials, private keys, generated output, or unlicensed code.

Browse the source ↗
04 / Sign off

Preserve provenance.

Contributors retain copyright. Each commit must carry a DCO sign-off confirming that the contribution can be distributed under Apache-2.0.

Read the licence ↗

Project boundary

Open source, maintainer-led.

Cix is led and maintained by Omar Sakka. The maintainer makes final decisions about accepting changes, releases, and the official Cix distribution.