Introduce ADRs
This commit is contained in:
parent
f876e9243c
commit
f9bafe092d
2 changed files with 20 additions and 0 deletions
1
.adr-dir
Normal file
1
.adr-dir
Normal file
|
@ -0,0 +1 @@
|
||||||
|
docs/adr/
|
19
docs/adr/0001-record-architecture-decisions.md
Normal file
19
docs/adr/0001-record-architecture-decisions.md
Normal file
|
@ -0,0 +1,19 @@
|
||||||
|
# 1. Record architecture decisions
|
||||||
|
|
||||||
|
Date: 2019-12-25
|
||||||
|
|
||||||
|
## Status
|
||||||
|
|
||||||
|
Accepted
|
||||||
|
|
||||||
|
## Context
|
||||||
|
|
||||||
|
We need to record the architectural decisions made on this project.
|
||||||
|
|
||||||
|
## Decision
|
||||||
|
|
||||||
|
We will use Architecture Decision Records, as [described by Michael Nygard](http://thinkrelevance.com/blog/2011/11/15/documenting-architecture-decisions).
|
||||||
|
|
||||||
|
## Consequences
|
||||||
|
|
||||||
|
See Michael Nygard's article, linked above. For a lightweight ADR toolset, see Nat Pryce's [adr-tools](https://github.com/npryce/adr-tools).
|
Loading…
Reference in a new issue