-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Cleanup readme #8177
Comments
Regulations around crypto are fuzzy at best. We'll continue to follow the advice of our legal team and navigate the space conservatively. Regarding the architectural diagram, we can add that, but it won't get you too far. What's implemented here is complex. Sounds like you came to this project looking for particular information. What is that? The novel tech? Check out Proof of History. |
You are the first (of 20? ) projects to have such an "overcrowded" readme, and a legal disclaimer. Anyways, I just came to get a feeling of the codebase, and possibly to try a build. nothing more. Your readme needs to be reduced, it's scary. Remove the "Introduction" etc., go straight to the "Build from Source" point. Install from binaries is stuff for the manual (just link to it).
It is not.
went already through it, sounds really nice. |
(note that the "readme-problem" is a general one, see e.g. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
This stale issue has been automatically closed. Thank you for your contributions. |
This issue has been automatically locked since there has not been any activity in past 7 days after it was closed. Please open a new issue for related bugs. |
This, and many other writings, do not belong into the Readme.
Focus on usual stuff, compact.
no! provide an archetuctaral overview diagram to llok at, and point to it from the readme.
The text was updated successfully, but these errors were encountered: