New RFC Repo #1
New RFC Repo #1
Conversation
…evious-versions00/README.md
…tandards/core/12/previous-versions00/README.md
| @@ -0,0 +1,409 @@ | |||
| --- | |||
| slug: 9 | |||
| title: 9/WAKU-RPC | |||
There was a problem hiding this comment.
Should this be included in core directory? Also, should the file name be rpc.md(spec #16 is called rpc also, waku2-rpc.md, or waku1-rpc.md?
| slug: 24 | ||
| title: 24/STATUS-CURATION | ||
| name: Status Community Directory Curation Voting using Waku v2 | ||
| status: draft |
There was a problem hiding this comment.
All Status specs are changed to draft.
status/62/payload.md
Outdated
| ### MembershipUpdateMessage and MembershipUpdateEvent | ||
|
|
||
| `MembershipUpdateEvent` is a message used to propagate information about group membership changes in a group chat. | ||
| The details are in the [Group chats specs](../56/communities.md). |
There was a problem hiding this comment.
Changed this link to 56/Communities, use to be 7/GROUP-CHAT. There are a few Status specs referencing the old https://specs.status.im/.
| slug: 57 | ||
| title: 57/STATUS-Simple-Scaling | ||
| name: Status Simple Scaling | ||
| status: draft |
There was a problem hiding this comment.
Simple scaling should be a raw RFC.
We could add a folder "raw" under status for now and put it there.
| @@ -0,0 +1,228 @@ | |||
| --- | |||
| slug: 1 | |||
| title: 1/COSS | |||
There was a problem hiding this comment.
Just as a note: we would have to adjust the COSS to the new process. (in a follow-up PR)
| slug: 25 | ||
| title: 25/LIBP2P-DNS-DISCOVERY | ||
| name: Libp2p Peer Discovery via DNS | ||
| status: deleted |
There was a problem hiding this comment.
We would have to add this status in the COSS.
Not sure if this makes sense. Let's discuss. (This does not block this PR, just as a note)
| @@ -0,0 +1,80 @@ | |||
| --- | |||
| slug: 4 | |||
There was a problem hiding this comment.
We might want to update the numbers of the RFCs in the 2-9 range (just a note, not in this PR, please put this on the to discuss list :))
Added Waku draft rfcs in own sub directory, separated by core, application, informational, and deprecated specification. Directory numbers should add a 0 in front of the number becuase when 100 is reached will cause older specifications to be placed at the end of a subdirectory list.