Skip to content

README.md

Latest commit

 

History

History
74 lines (54 loc) · 2.58 KB

README.md

File metadata and controls

74 lines (54 loc) · 2.58 KB
Raw

Developer OS proof of concept

This monorepo builds the first Developer OS image: Fedora Atomic KDE with one branded Plasma Wayland session and Xwayland compatibility.

Developer OS is a working name. The image ID (developer-os) is deliberately stable and non-marketing so that the final product name can change later.

Status

The repository is an executable Phase 1 scaffold. It includes:

  • a digest-pinned Fedora Kinoite 44 base image;
  • a product session RPM;
  • a first-login Plasma profile with a top panel and bottom dock;
  • an upstream-maintained SDDM theme with Developer OS artwork;
  • image policy checks that reject exposed X11 or extra Wayland sessions;
  • a resumable OCI cache path for unreliable registry connections;
  • a QEMU disk-image build path using the current unified Image Builder CLI;
  • CI checks for source policy and container-image composition;
  • manual GitHub-hosted container and bootable-disk build pipelines.

The host used to create this scaffold is macOS and has no Podman or Linux image builder installed, so a full 3+ GB image build must run on Fedora 44 or in CI.

Quick start

./scripts/build-container.sh
./scripts/verify-container.sh

The container scripts automatically select Podman or Docker and build the x86_64 target by default. Override with CONTAINER_RUNTIME or IMAGE_PLATFORM. On an unreliable connection, populate the resumable base cache first:

./scripts/fetch-base.sh

Disk-image generation requires Fedora 44:

sudo dnf install -y podman image-builder qemu-kvm
./scripts/build-disk.sh

The disk artifact is written below output/. See docs/BUILDING.md for VM boot and release-input details.

Repository map

  • image/ — bootable container definition
  • packages/ — product-owned RPM sources
  • desktop-profile/ — Plasma first-login defaults
  • artwork/ — temporary, non-brand assets
  • tests/ — static and image-level smoke tests
  • scripts/ — reproducible build entry points
  • docs/ — prototype decisions and build documentation

The authoritative product foundation remains in the repository-level Docs/ directory.

Current verification evidence and the remaining VM/hardware gates are tracked in docs/STATUS.md.

For poor local connections, GitHub Actions can perform the full image downloads and builds remotely. See docs/CI.md.

Project decisions

The architecture in Docs/02_ARCHITECTURE_DECISIONS.md is authoritative. Prototype-specific choices and their replacement conditions are recorded in docs/POC_DECISIONS.md.