m/yino
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add upstream tracking goal and section to FSD

Browse Source 
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Michael Smith 2026-02-15 22:42:06 +01:00
parent 0d726f6dee
commit b8a002eb50
1 changed files with 10 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/yino-fsd.md
View File

@ -23,6 +23,7 @@ instead of Arch Linux.
- Remove anything that can be removed that has been added to Omarchy in order to deal with its possibly unstable,
rolling release base of Arch Linux
- Just like Omarchy, produce an ISO image that can perform a complete offline installation of Yino
- Maintain ongoing feature parity by tracking upstream Omarchy development and porting relevant changes
## 3. Architecture
@ -49,4 +50,12 @@ This should match Omarchy's architecture (see [Omarchy Analysis](Omarchy.md) for
- QEMU should be used for testing and demo virtual machines
- Keep a cache of downloaded assets (e.g. Debian installation ISO) in this repository's `download` directory
## 6. Changelog
## 6. Upstream tracking
- Track the upstream [basecamp/omarchy](https://github.com/basecamp/omarchy) repository for new releases and changes
- Omarchy's `dev` branch is where active development happens; `master` is the stable branch
- Evaluate new Omarchy releases and port applicable changes to Yino
- Keep the [Omarchy Analysis](Omarchy.md) document up to date as upstream evolves
- Translate Arch-specific changes to their Debian equivalents per the package and command mapping in [Omarchy Analysis](Omarchy.md) section 14
## 7. Changelog