Contribute

Keru is small and early, which means contributions are unusually consequential. A recipe you write may be the one a whole filesystem choice builds on. Here's how to get in.

Where things live

Repo	You'd contribute
KeruOS	Installer, profile, scripts, live init, docs, and this website.
kama	The package manager itself — and, ideally, not much. It's meant to stay small.
kama-packages	Recipes — the highest-leverage place. Busybox, runit, and a template exist.

Ways to help

• Write recipes. A <pkg>.sh in kama-packages is a package. Start from TEMPLATE.sh. The format is small.
• Test the toolchain bootstrap. The stage-0 build (gcc/glibc from nothing) is the riskiest seam; hands on real machines are gold.
• Sharpen the installer. Menu UX, network handling, stability checks — all open.
• Fix bugs. The road to 0.1 is literally a list of bugs between here and a booting ISO.
• Docs & site. This website lives in web/ in the KeruOS repo — plain HTML, no framework. Improving it is plain work on plain files.

Ground rules

• Match the ethos. Source-only, no opinion, small pieces. A PR that adds a dependency resolver to kama contradicts the project's spine.
• Stay legible. If shell can do it plainly, don't introduce machinery.
• Honesty at the edges. Unproven combinations go in with a warning, or not at all — never silently.
• AGPL-3.0. All three repos are AGPL-3.0; contributions fall under it.

Where to start

Issues, recipe ideas, and bug reports live on the three repositories, and discussion on the contact channels. If you're looking for a first move: pick a recipe, read TEMPLATE.sh, and send it.