KDE Linux
TODO: background, motivation
Goals
See 🍌
Target audience and use cases
See 🍌#Target audience and use cases
Architecture
See 🍌#Architecture
Related projects
Differences from other immutable distros
(e.g. Kinoite, MicroOS, SteamOS)
Principally, that it is distributed by KDE. This has several advantages:
- The chain of responsibility is never gated on a third party
- KDE and KDE e.V. can have a direct relationship with third parties using it, e.g. hardware OEMs
- KDE can explicitly recommend it without "picking favorites" from among other distro partners
TODO: differences on a technical level (e.g. another approach to updates / isolation? i.e. why this is not just a copy of Kinoite distributed by KDE)
Prior art
KDE Neon, KDE's first version of a self-made OS. Neon fulfills the "distributed by KDE" requirement, but fails on the reliability angle due to the Ubuntu LTS base that ironically becomes unstable because it needs to be tinkered with to get Plasma to build on it, breaking the LTS promise.
Roadmap
TODO (milestones)
Long-term maintenance
TODO (team and infrastructure requirements for long-term sustainability after release; update cycles; testing infrastructure; architectural future-proofness)
Governance
TODO
Promotion
TODO (name and branding, public image, effect on relations with other distros and hardware partners)
Communication
Prototype
The code is currently located here. Note that it is not representative of the final product and exists solely as an experimental playground for now.