Architecture Design Records for KDE
See https://blogs.kde.org/2020/09/11/using-architecture-decision-records-adrs-kde/
We regularly make decisions on something, often that affect multiple or all projects, but often that decision isn't written down/widely communicated. This leads to problems like a decision being implemented incompletely/inconsistently or being forgotten over time.
Examples for such decisions could be:
- "Let's use C++20"
- "All C++ code should be formatted via clang-format"
- "QML code should be deployed using qt_add_qml_module"
A system like ADRs could help there. The challenge here is to keep a balance between having some kind of discussion/review/quality process and avoiding excessive burocracy/bikeshedding.