Paper Cleanups #102
Merged
Paper Cleanups #102
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
This file had no content and was confusing.
Consensus is to document multi-writer via a DEP (RFC-like) process first, and not propose new changes in the whitepaper first.
This could probably be clarified better (minor revisions and bug-fixes vs. substantial updates), and maybe we want to pull out the original "1.0" paper for historical reference. Let's wait until DEP process settles down first.
17 tasks
|
All looks good! Thanks. |
|
@bnewbold I moved the whitepaper over https://github.com/datprotocol/whitepaper. Where there any other changes you had in mind to marked the paper as "frozen"? If it all looks good, I'll delete the paper stuff here. |
|
I think we can delete the paper here, i'll add any future notes to the docs or a DEP. |
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.
The intent of this PR is to put the whitepaper(s) in a reasonable state (no TODOs or partial documentation of mutli-writer) while we shift efforts to the DEP process.
It might be worthwhile to do one more round of small additions after this PR such that the paper correctly documents the 2017 dat protocol behavior (eg, the whitepaper doesn't mention a couple crucial details like keep-alive packets or how to delete hyperdrive entries).
r? @mafintosh @Karissa (as paper co-authors)