- Revert moving of ports and branching strategy because those are
actively preventing questions and PR difficulty
- Remove travis badge because we no longer use travis
- Fix formulation throughout the document
- Rewrite the contribution section
- Switch from Dogecoin devs twitter to Dogecoin twitter under
communities
- Add Q&A board to FAQ section
- Fix document language selector
- Bring tables back to "mining information"
Author: AbcSxyZ <rossi.sim@outlook.com>
Cherry-picked and squashed from:
20480d33b README: change social media position
39a209b98 README: Change section order
bdb727981 README: reorganize social medias, split dev specific
& and more community related in 2 sections
bbc6c921c Add emote to titles
e39256825 Install.md : Improve first title
ebef882c5 Fix typo
1cec6b16b Extract FAQ and INSTALL into respective files
314b6f8e2 Add developement & contribution information directly
on readme
a7e556924 Remove original block reward schedule
8cb73041a Move licence section at README bottom
Made the README much wow. Centered the title, logo, and badges. Added two badges that redirect to the website: "dogecoin" and "much wow" and removed the period that was included in the website's hyperlink.
Update
"Early 2015 (approximately a year and a half after release) there were
approximately 100,000,000,000 coins."
to
"Early 2015 (approximately a year and a half after release) there were
approximately 100,000,000,000 coins."
because that was 6 years ago and is now the past. Were makes more sense than will be at this point.
- Removed dead image links.
- Updated Travis ci badge link to direct to the master branch and the new Travis website url.
- Added Emojis to headers for clarity and to get the feel of dogecoin for newcomers.
- Bolded some sub headers for clarity. e.g. block reward sections.
- Code formatting.
plodder: cherry pick notes:
- Cherry-picked and sanitized to resolve conflicts
- fixed some very long lines
- removed tip4commit
- changed header for mining/subsidy info
Refer to the right file in the top-level README.md.
Having only one file with test documentation saves some confusion about
where things are documented.
If ZMQ is enabled, check whether it's installed before running ZMQ tests.
If it isn't, disable ZMQ and print a warning.
Also add dependency info to test docs, so users know ZMQ is required
before running tests, and so they know how to install it.
When following the build instructions before this change then trying
to run the RPC tests, a unix user would get an error when python
tried to import zmq.
There may be other dependencies that should be added to the docs,
particularly ones for non-unix systems. This is the only unlisted
dependency I encountered using linux.