-
Short: We think to revert https://github.com/adr/madr/issues/41 to strengthen "Architecturally Significant".
- "Any": Too broad
- "Architectural": Maybe too narrow?
Is going back to "Markdown A…
-
This is also probably a good time to recommend documenting architecture decisions in the project. The project itself is very opinionated (which is great!), so all of that should be documented to help…
-
Purely IP, linux and LXC-oriented (pod definition explicitly references a subset of linux kernel namespaces), with additional environment and security posture assumptions:
- "Each app in a pod will st…
-
Really interesting approach/idea. Not sure I agree with all the decisions, but I like the approach.
https://www.lullabot.com/articles/improving-team-efficiency-architecture-decision-records
https:…
-
See for details:
- http://thinkrelevance.com/blog/2011/11/15/documenting-architecture-decisions
- https://speakerdeck.com/vanto/a-brief-introduction-to-architectural-decision-records
- https://adr.…
-
Here we can discuss and post decisions about the 9th topic of the documentation.
Important, expensive, critical, large scale or risky architecture decisions including rationales.
https://docs.ar…
-
## Is your feature request related to a problem? Please describe.
During the initial implementation of caikit we iterated through quite a few design choices, and landed on some important ones after…
-
We need an up to date architecture diagram that is inclusive of the direction we are heading with Localeyz. There are key problems we need to solve, I believe the starting point for solving these is u…
-
I’m opening this issue to summarize the major changes between `linter-eslint` and this package, and to decide what else is worth changing.
Some of the changes are necessary because of the new archi…
-
I think we should briefly document the major architecture design decision, eg code organization, bootstrap sequence, architectural components. This can be very brief. The important thing is to have a …