This repository has been archived by the owner on Jun 29, 2022. It is now read-only.
Major reorg and introduction of spec status & governance #125
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.
WIP I suppose; I don't imagine this will be straightforward.
This is probably best assessed by viewing through the branch rather than trying to make sense of some of the diffs (especially README): https://github.com/ipld/specs/tree/rvagg/big-reorg
Inspired in part by the governance proposal at #122 (included here, but in the README) which focuses on specifications, but we have more than just specifications as #123 makes clear (as does a lot of the existing content).
Edits to README look bigger than they are because I went with a more consistent line-break strategy than we have now of break-on-sentence.