-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
57/STATUS-Simple-Scaling: Short Summary #633
Conversation
@kaiserd this abstract display two COSS format specs and link to them. Is this good for the short summary? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the description.
The reference changes should be reverted though.
content/docs/rfcs/57/README.md
Outdated
@@ -5,16 +5,16 @@ name: Status Simple Scaling | |||
status: raw | |||
category: Informational | |||
tags: waku/application | |||
editor: Daniel Kaiser <danielkaiser@status.im> | |||
description: Describes how to scale Status Communities and Status 1-to-1 Chat using existing Waku v2 protocols and components. | |||
editor: Jimmy Debe <jimmy@status.im> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As discussed, please do not change the editors of RFCs that were already under Vac org. (Only put yourself as an editor for the RFCs that you ported from status.im to Vac org).
content/docs/rfcs/57/README.md
Outdated
This document describes how to scale [56/STATUS-COMMUNITIES](/spec/56/) as well as [55/STATUS-1TO1-CHAT](/spec/55/) | ||
using existing Waku v2 protocols and components. | ||
It also adds a few new aspects, where more sophisticated components are not yet researched and evaluated. | ||
This document describes how to scale [56/STATUS-COMMUNITIES](https://rfc.vac.dev/spec/56/) as well as [55/STATUS-1TO1-CHAT](https://rfc.vac.dev/spec/55/) using existing Waku v2 protocols and components. It also adds a few new aspects, where more sophisticated components are not yet researched and evaluated. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why did you remove sembr here?
Please revert this back to a sembr.
content/docs/rfcs/57/README.md
Outdated
[56/STATUS-COMMUNITIES](/spec/56/) as well as [55/STATUS-1TO1-CHAT](/spec/55/) use Waku v2 protocols. | ||
Both use Waku content topics (see [23/WAKU2-TOPICS](/spec/23/)) for content based filtering. | ||
|
||
[56/STATUS-COMMUNITIES](https://rfc.vac.dev/spec/56/) as well as [55/STATUS-1TO1-CHAT](https://rfc.vac.dev/spec/55/) use Waku v2 protocols. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please revert these changes. Specs should be referenced relatively.
This is how all refs to Vac RFCs should look like:
56/STATUS-COMMUNITIES
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thank you :)
This document describes how to scale 56/STATUS-COMMUNITIES as well as 55/STATUS-1TO1-CHAT using existing Waku v2 protocols and components.