Add basic ADR doc setup and first LVM ADR #149
Closed
b12f wants to merge 1 commit from
adr/01-lvm-on-luks
into main
pull from: adr/01-lvm-on-luks
merge into: pub-solar:main
pub-solar:main
pub-solar:hensoko-no-digga
pub-solar:momo/fix-lib-deploy-rs
pub-solar:momo/main
pub-solar:flora-6-forgejo-actions-ci
pub-solar:teutat3s
pub-solar:infra
pub-solar:hensoko
pub-solar:b12f
pub-solar:pub.solar/nougat-2
pub-solar:momo/keycloak
pub-solar:feature/fix-modules
pub-solar:momo/infra-poc
pub-solar:b12f-bash
pub-solar:update/gitea-docker
pub-solar:feature/fix-correct-unit
pub-solar:fix/nvfetcher-rebuild
pub-solar:feature/ci-runner-experiment
pub-solar:teutat3s-drone-exec-runner
pub-solar:feature/fake-branch
pub-solar:hensoko-pre-rebase-bak
pub-solar:feature/ci-runner
pub-solar:vlalentim
pub-solar:feature/swaynotificationcenter
pub-solar:feature/wayvnc
pub-solar:feature/atomic-pre-commit
pub-solar:devos
pub-solar:pkg/wlstreamer
1 commit
Author | SHA1 | Message | Date | |
---|---|---|---|---|
Benjamin Bädorf |
6fca77a69f
|
Add basic ADR doc setup and first LVM ADR
This commit introduces Architectural Decision Records. To quote: > Architectural Decision Records (ADRs) > > An Architectural Decision (AD) is a software design choice that > addresses a functional or non-functional requirement that is > architecturally significant. An Architecturally Significant > Requirement (ASR) is a requirement that has a measurable effect on a > software system’s architecture and quality. An Architectural Decision > Record (ADR) captures a single AD, such as often done when writing > personal notes or meeting minutes; the collection of ADRs created > and maintained in a project constitute its decision log. All these > are within the topic of Architectural Knowledge Management (AKM), but > ADR usage can be extended to design and other decisions (“any > decision record”). Taken from https://adr.github.io/ This commit also adds the first ADR; both as an example as well as a serious proposal. This ADR is a product of discussions around encrypted swap, hibernation, onboarding of new devices, and fragmentation. |