Use storage or server in place of data pod #365
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
matthieubosquet
approved these changes
Dec 17, 2021
There was a problem hiding this comment.
I like the simplification and distinction between server and storage.
I am wondering if the term "Solid Server" would be better than simply "Server". I know it is derived from context and I'm not sure what it means for the use of spec:Server (do we need to use solid:Server subclassOf spec:Server instead?) but it seems potentially nice to be more specific.
elf-pavlik
approved these changes
Dec 17, 2021
Co-authored-by: Matthieu Bosquet <[email protected]>
kjetilk
approved these changes
Dec 17, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Removes use of the term data pod in requirements in favour of server or storage. Leaves the the term "data pod" as is for now. It should be revisited for 1.0.