Contributing

Bug reports, documentation fixes, translations, testing on real hardware and code are all welcome.

Ways to help

Try it and report what breaks. Hardware reports for laptops, GPUs and Wi-Fi are especially valuable now. See Get help.
Improve these docs. Every page has an Edit page link at the bottom. Fix a typo, clarify a step or add what you wish you had known.
Translate. The website and docs are in English and Simplified Chinese. If you would like to add a language, start a conversation on Discord first so we can set it up.
Write code. Look for issues labelled good first issue or help wanted in the kleinia-os organisation.

Before you start on something big

Open an issue before writing a large change, a new component or anything that touches a public interface: the agent:// scheme, D-Bus APIs, command-line options or configuration formats. A short design note saves everyone a rewrite.

Pull requests

One logical change per pull request.
Commit messages follow Conventional Commits, for example fix(gateway): retry on 429.
Sign off every commit to certify the Developer Certificate of Origin: git commit -s.
Kernel changes follow the upstream Linux submitting patches rules.

The full guide is in CONTRIBUTING.md in each repository.

AI-assisted contributions

Kleinia is a system for agents, so using AI tools to help you write code or docs is fine. You are still the author: review and test everything you submit, make sure you have the right to contribute it, and be ready to explain it in review.

Code of Conduct

Everyone taking part in Kleinia, on GitHub, Discord or anywhere else, is expected to follow our Code of Conduct, based on the Contributor Covenant.