Co-authored-by: samricotta <37125168+samricotta@users.noreply.github.com> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> Co-authored-by: Marko <marbar3778@yahoo.com> Co-authored-by: samricotta <samanthalricotta@gmail.com>
This commit is contained in:
co-authored by
samricotta
Marko
samricotta
parent
0428c48339
commit
a980bf720e
+4
-1
@@ -13,7 +13,7 @@ discussion that might otherwise only be recorded in an ad-hoc way (for example,
|
||||
via gists or Google docs) that are difficult to discover for someone after the
|
||||
fact. An RFC _may_ give rise to more specific architectural _decisions_ for
|
||||
the Cosmos SDK, but those decisions must be recorded separately in
|
||||
[Architecture Decision Records (ADR)](../architecture/).
|
||||
[Architecture Decision Records (ADR)](../architecture).
|
||||
|
||||
As a rule of thumb, if you can articulate a specific question that needs to be
|
||||
answered, write an ADR. If you need to explore the topic and get input from
|
||||
@@ -36,3 +36,6 @@ sections.
|
||||
## Table of Contents
|
||||
|
||||
<!-- - [RFC-NNN: Title](./rfc-NNN-title.md) -->
|
||||
|
||||
* [RFC-002: Zero Copy Encoding](./rfc-002-zero-copy-encoding.md)
|
||||
|
||||
|
||||
@@ -1,5 +0,0 @@
|
||||
{
|
||||
"label": "RFCs",
|
||||
"position": 12,
|
||||
"link": null
|
||||
}
|
||||
Reference in New Issue
Block a user