Closed oskarth closed 4 years ago
Also see https://github.com/status-im/specs/issues/1
This issue is slightly more narrow in scope, as it only deals with the individual spec format. More formal process can come later.
I like the MVDS spec format, personally. We can get nitpicky once everything is in such a state.
Corey
On Thu, Jul 11, 2019 at 11:48 PM Oskar Thorén notifications@github.com wrote:
Also see #1 https://github.com/status-im/specs/issues/1
This issue is slightly more narrow in scope, as it only deals with the individual spec format. More formal process can come later.
— You are receiving this because you are on a team that was mentioned. Reply to this email directly, view it on GitHub https://github.com/status-im/specs/issues/26?email_source=notifications&email_token=AASYT4KEZ2O7V3VN7JKN4K3P675J3A5CNFSM4ICALQF2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZYS5VA#issuecomment-510734036, or mute the thread https://github.com/notifications/unsubscribe-auth/AASYT4NHVBLJF4XPJ7BCQRTP675J3ANCNFSM4ICALQFQ .
Done I believe
We should have a standard format of specs so they are easier to read and parse.
Here's one example that's fairly clean https://github.com/status-im/bigbrother-specs/blob/master/data_sync/mvds.md#table-of-contents
Wdyt @status-im/status-protocol