"Architectural Decisions" to strengthen "Architecturally Significant"
Closed this issue · 3 comments
koppor commented
Short: We think to revert #41 to strengthen "Architecturally Significant".
- "Any": Too broad
- "Architectural": Maybe too narrow?
Is going back to "Markdown Architectural Decision Records" a good idea?
koppor commented
Note: spotify backstage uses docs/architecture-decisions
as path.
jonthenerd commented
For what it's worth, I think it's relevant to keep MADR related to architecture. Architecture implies significance. Going through the labor of establishing a decision record is really only warranted when that decision will have a significant impact. Hence, why you wouldn't do it for "any" decision. While you could you probably shouldn't and most wouldn't.
koppor commented
IMHO, we changed everything in our developer branch, we need to check.