Skip to content
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

Merged
merged 11 commits into from
Jul 29, 2022
Merged

Conversation

orpheuslummis
Copy link
Contributor

@orpheuslummis orpheuslummis commented Jul 20, 2022

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

  • I made sure the code is well commented, particularly hard-to-understand areas.
  • I made sure the repository-held documentation is changed accordingly.
  • I made sure the pull request title adheres to the conventional commit style (the subset used in the project can be found in tools/configs/chglog/config.yml).
  • I made sure to discuss its limitations such as threats to validity, vulnerability to mistake and misuse, robustness to invalidation of assumptions, resource requirements, ...

How has this been tested?

Human reading.

@orpheuslummis orpheuslummis added the documentation Improvements or additions to documentation label Jul 20, 2022
@orpheuslummis orpheuslummis added this to the DefraDB v0.3 milestone Jul 20, 2022
@orpheuslummis orpheuslummis requested a review from a team July 20, 2022 17:00
@orpheuslummis orpheuslummis self-assigned this Jul 20, 2022
@orpheuslummis orpheuslummis added the action/no-benchmark Skips the action that runs the benchmark. label Jul 20, 2022
@sourcenetwork sourcenetwork deleted a comment from source-devs Jul 22, 2022
@orpheuslummis orpheuslummis marked this pull request as ready for review July 22, 2022 14:06
@orpheuslummis orpheuslummis changed the title docs: README update for v0.3.0 docs: README update v0.3.0 Jul 22, 2022
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
Copy link
Collaborator

@fredcarle fredcarle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like it 🙂

Copy link
Member

@jsimnz jsimnz left a 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
Comment on lines 13 to 28
* [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)
Copy link
Member

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?

Copy link
Contributor Author

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

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Screen Shot 2022-07-28 at 16 33 44

Github provides a TOC

Copy link
Contributor Author

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

Copy link
Contributor Author

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

Copy link
Member

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.

Copy link
Collaborator

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.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMO, TOC is metadata that can be inferred from the sections
Another example is getting the TOC automatically from vscode's Outline panel
Screen Shot 2022-07-28 at 22 36 02

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>
Copy link
Member

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>

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

Copy link
Collaborator

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...

Copy link
Contributor Author

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?

Copy link
Member

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.

Copy link
Member

@shahzadlone shahzadlone left a 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:

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
Copy link
Member

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
Comment on lines 13 to 28
* [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)
Copy link
Member

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.

README.md Outdated Show resolved Hide resolved
README.md Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved

You can access the official DefraDB Query Language documentation online here: [https://hackmd.io/@source/BksQY6Qfw](https://hackmd.io/@source/BksQY6Qfw)
## Query language documentation
Copy link
Member

@shahzadlone shahzadlone Jul 29, 2022

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.

Copy link
Collaborator

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.

Copy link
Contributor Author

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.

@orpheuslummis
Copy link
Contributor Author

@shahzadlone badges as goal bumped to next update for v0.4: #686

Copy link
Member

@shahzadlone shahzadlone left a 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.

@orpheuslummis
Copy link
Contributor Author

@jsimnz ping

@orpheuslummis orpheuslummis merged commit f58e700 into develop Jul 29, 2022
@orpheuslummis orpheuslummis deleted the orpheus/docs/README-update branch July 29, 2022 07:01
shahzadlone pushed a commit to shahzadlone/defradb that referenced this pull request Feb 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
action/no-benchmark Skips the action that runs the benchmark. documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

README overhaul
4 participants