Distribution Development

Beyond apps and packages lies the distribution itself: the installer, system configuration, theming, and the repository infrastructure that holds it all together. This section covers how those pieces are built and maintained.

Component ownership

Who maintains what, and how a change travels from issue to release.

Installer development

Working on the Parch Calamares flavor and archinstall-rs.

System configuration

base-config, parch-config, and the defaults shipped on installed systems.

Theming & branding

SDDM, GRUB, Plymouth, wallpapers, and the Arts pipeline.

Repository infrastructure

Running world and Void: tooling, promotion, and integrity.

Release management

How editions ship, rollback, and communicate change.

The lifecycle of a change

issue → RFC (if cross-cutting) → branch → implement → test
      → pull request → review → merge → release (ISO tag or repo push)

Every distribution change starts from a real problem in an issue tracker. Cross-cutting changes (new edition, default-package changes, installer behavior) start in the rfcs repo first; the contribution workflow explains the doors.

Where the risk lives

Continue in Distribution Development

Component ownershipWho maintains what, and how a change travels from issue to release.Installer developmentWorking on the Parch Calamares flavor and the Rust installer generation.System configurationbase-config, parch-config, and the defaults shipped on installed systems.Theming & brandingSDDM, GRUB, Plymouth, wallpapers, and the Arts pipeline.Repository infrastructureRunning world and Void: tooling, promotion, and integrity.Release managementHow editions ship, roll back, and communicate change on a rolling release.