-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introduce Architecture Decision Records #13
Conversation
A |
docs/README.md
Outdated
@@ -0,0 +1,3 @@ | |||
# Documentation | |||
|
|||
* Technical [Architecture](architecture.md): Main entry point for technical details about Hydra node implementation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This indirection is not required IMO, I'd just put the technical architecture document in place here until we have other docs.
docs/architecture.md
Outdated
Please refer to each component's internal documentation for details. | ||
|
||
* The [HydraNode](../hydra-node/src/Hydra/Node.hs) is a handle to all other components' handles | ||
* This handle is used by the main loop to `processNextEvent` and `processEffect` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Anything referring to actual identifiers should be in the module haddock IMO. But this is out of scope for this PR and I gladly help in moving these things and make it coherent :)
## Decision | ||
|
||
* We will use _Architecture Decision Records_, as described by Michael Nygard in this article: http://thinkrelevance.com/blog/2011/11/15/documenting-architecture-decisions | ||
* We will follow the convention of storing those ADRs as Markdown formatted documents stored under `docs/adr` directory, as exemplified in Nat Pryce's [adr-tools](https://raw.githubusercontent.com/npryce/adr-tools). This does not imply we will be using `adr-tools` itself. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Broken link to adr-tools
|
||
## Consequences | ||
|
||
See Michael Nygard's article, linked above. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wouldn't it be helpful to extract the bits we deem as important here? or do we expect anyone to read the article anyway?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Architecture Decision Records, or ADRs, are a form of lightweight documentation of the architecture, or more generally technical, decisions made or revoked during the development of a system.