Contributing to AcreetionOS

A distribution is a team sport. Every skill level has a position.

Pick your lane

If you can…	Start at
Break things methodically	Testing & QA
Write clearly	Documentation — including improving these very pages
Read/build code or recipes	Packaging · ISO builds
Speak more than one language	Translations
Reproduce failures precisely	Bug reporting — the highest-leverage entry point
Sponsor infrastructure	Support & donations

If you can…

Start at

Break things methodically

Write clearly

Documentation — including improving these very pages

Read/build code or recipes

Speak more than one language

Reproduce failures precisely

Bug reporting — the highest-leverage entry point

Sponsor infrastructure

Everything hangs off the GitHub org — layout map in Repository Layout. Docs (this site) build with Antora; content fixes are pull requests away.

Rolling-release discipline applies to contributors too — test against current, not ancient
Reproduce before reporting; document after fixing
Be excellent to each other; maintainers volunteer time like everyone else

Typos/unclear passages here → PR them (seriously, docs hunger)
Run current ISO in a VM weekly (Testing & Quality Assurance) and note regressions early
Package something from your toolkit per Packaging Guidelines