-
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…
-
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:…
-
## Description
Placeholder ticket for outputs of event storm re: stake decoupling and ERC20 vote weight. Will determine the architectural decisions for implementing https://github.com/hicommonwealt…
-
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…
-
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…
-
## 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…
-
Several OEPs were authored aspirationally, and then never implemented. Other were partially implemented, but have stalled or diverged from reality. Yet others should be followed by the community, but …
-
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…
-
New to project, so feel free to ignore, but the following is my proposition seeing little in the way of documentation and some sort of 'in-progress' architecture around build, CI / CD, etc.
Proposa…
-
Features to import/discuss:
- [ ] where should the examples live / repo structure
- [ ] separate the scheduler and the communication mechanism.
- [ ] RosMsgs
- [ ] ZMQ
- [ ] Compatibility with ex…