Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
2 changed files
with
33 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
Architectural Decision Records | ||
============================== | ||
|
||
We document our architectural and design decisions for all of our components. | ||
In order to do that, there is practice called architectural decision records ("ADR"), | ||
that we can integrate into our workflow. | ||
An architectural decision record (ADR) is a document that captures an important architectural decision made along with its context and consequences. | ||
|
||
The goals are: | ||
|
||
* making decisions transparent to internal/external stakeholders and contributors. | ||
|
||
* getting feeback on decisions that we're about to make or have made | ||
|
||
* providing external contributors a framework to propose architectural changes | ||
|
||
* providing a big picture of all major decisions that were made | ||
|
||
The general process for creating an ADR is: | ||
|
||
1. cloning the repository | ||
|
||
2. creating a new file with the format `<ADR_NUMBER>-<TITLE>.rst` in the directory `doc/adr` | ||
|
||
3. adding the ADR in the table of content tree of the Readthedocs | ||
|
||
4. committing and pushing to the repository |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters