-
Notifications
You must be signed in to change notification settings - Fork 44
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
docs: README update v0.3.0 #646
Conversation
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.
I like it 🙂
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.
one question, one change. Good stuff. Reads very well
README.md
Outdated
* [Early Access](#early-access) | ||
* [Installation](#installation) | ||
* [Build](#build) | ||
* [Getting Started](#getting-started) | ||
* [Add a Schema type](#add-a-schema-type) | ||
* [Create a Document Instance](#create-a-document-instance) | ||
* [Query our documents](#query-our-documents) | ||
* [Interact with Document Commits](#interact-with-document-commits) | ||
* [Query Documentation](#query-documenation) | ||
* [CLI Documentation](#cli-documentation) | ||
* [Next Steps](#next-steps) | ||
* [Licensing](#licensing) | ||
* [Contributors](#contributors) | ||
* [Further Reading](#futher-reading) | ||
* [Technical Specification Doc](#technical-specification-doc) | ||
* [Design Doc](#design-doc) |
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.
question: Why get rid of the table of contents?
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.
I thought: shorter is better, and cutting out the TOC would make it shorter lol
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.
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.
Although it's probably not a well known feature
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.
My preference is not to have a TOC and keep the README document short
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.
IMO this adds value. I wouldn't prioritize shorter length over usefulness.
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.
Let remember that this is a readme and not the full documentation. No TOC is quite ok here and I personally don't care about them on readme files. What I care about is basic usage how to and where to find more info.
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.
README.md
Outdated
The current early access release has much of the digital signature, and identity work removed, until the cryptographic elements can be finalized. | ||
Set *nodeA* to actively replicate the "Article" collection to *nodeB*: | ||
```shell | ||
defradb client rpc addreplicator "Article" /p2p/<peerID_of_nodeB> |
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.
suggestion(blocking): This needs a full format. Not just /p2p/<peerID>
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.
done
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.
oh wow I missed that even after working on that package for a week...
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.
I'm not currently sure we need the full address, i.e. it may be the case that /p2p/<peerID_of_nodeB>
just works?
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.
I'm not currently sure we need the full address, i.e. it may be the case that
/p2p/<peerID_of_nodeB>
just works?
It might work IFF the node in question has already previously been seen/connected to the given PeerID. Haven't tested locally so can't 100% confirm.
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.
Made some comments and suggestions, I was wondering though that the issue #146 mentioned about badges. I didn't see any new badges. I had some ideas:
- Discord: https://img.shields.io/badge/Discord-7289DA?style=for-the-badge&logo=discord&logoColor=white
- GoLang: https://img.shields.io/badge/Go-00ADD8?style=for-the-badge&logo=go&logoColor=white
- Go Report Card: https://goreportcard.com/
- CI build passing
We can do these later too, just checking that these aren't in scope?
One other suggestion I had is we could use collapsible (toggleable) sections if you were concerned about the length of the README.md
.
# | ||
The DefraDB is a Peer-to-Peer Edge Database, with the interface of a NoSQL Document Store. DefraDB's data model is backed by [MerkleCRDTs](https://arxiv.org/pdf/2004.00107.pdf) for a multi write-master architecture. It is the core data storage system for the [Source](https://source.network/) Ecosystem, built with [IPFS](https://ipfs.io/) technologies like [IPLD](https://docs.ipld.io/) and [LibP2P](https://libp2p.io/) and featuring Semantic web3 properties. You can read the [Technical Overview here](https://docsend.com/view/mczj7ic4i3kqpq7s). | ||
|
||
Table of Contents |
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.
suggestion: keep TOC.
EDIT: Discussed on discord.
README.md
Outdated
* [Early Access](#early-access) | ||
* [Installation](#installation) | ||
* [Build](#build) | ||
* [Getting Started](#getting-started) | ||
* [Add a Schema type](#add-a-schema-type) | ||
* [Create a Document Instance](#create-a-document-instance) | ||
* [Query our documents](#query-our-documents) | ||
* [Interact with Document Commits](#interact-with-document-commits) | ||
* [Query Documentation](#query-documenation) | ||
* [CLI Documentation](#cli-documentation) | ||
* [Next Steps](#next-steps) | ||
* [Licensing](#licensing) | ||
* [Contributors](#contributors) | ||
* [Further Reading](#futher-reading) | ||
* [Technical Specification Doc](#technical-specification-doc) | ||
* [Design Doc](#design-doc) |
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.
IMO this adds value. I wouldn't prioritize shorter length over usefulness.
|
||
You can access the official DefraDB Query Language documentation online here: [https://hackmd.io/@source/BksQY6Qfw](https://hackmd.io/@source/BksQY6Qfw) | ||
## Query language documentation |
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.
question: Wonder if we need a small @explain request
section like other main features.
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.
I think this belongs in the documentation and not really in the readme. I already feel like there is too much in here.
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.
We can debate how long the README should be. My opinion can definitely change, but I currently stand on the 'short and simple README' side which implies focusing on the simple exposition of core features only.
This PR improves the README but I believe it could be even better, i.e. shorter and clearer and more fun.
@shahzadlone badges as goal bumped to next update for v0.4: #686 |
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.
LGTM. Considering you will add the TOC with major headings.
9b8ba32
to
d9dc38a
Compare
@jsimnz ping |
Relevant issue(s)
Resolves #146 and #187
Description
Updated README
Opens as draft PR to gather feedback from team first.
Preview it using this link (which I keep up-to-date to latest commit of PR):
https://github.com/sourcenetwork/defradb/blob/b58fee1c35ec6bba4ed293761759fd6acdff007c/README.md
Tasks
How has this been tested?
Human reading.