Doc: general updates to multiple files. (PR #959)

The following files are removed:
    - doc/gitian-building.md
    - doc/release-notes-pr12924.md
    - doc/travis-ci.md

    General updates to multiple other files to reflect the current workflow.

Author: fdoving

CONTRIBUTING.md

@@ -26,7 +26,7 @@ To contribute a patch, the workflow is as follows:
 
   - Fork repository
   - Create topic branch
-  - Commit patches
+  - Create pull request
 
 The project coding conventions in the [developer notes](doc/developer-notes.md)
 must be adhered to.
@@ -55,9 +55,12 @@ about Git.
 The title of the pull request should be prefixed by the component or area that
 the pull request affects. Valid areas as:
 
+
+  - *Build* for changes to the build-system
   - *Consensus* for changes to consensus critical code
+  - *Depends* for changes to depends
   - *Docs* for changes to the documentation
-  - *Qt* for changes to raven-qt
+  - *GUI* for changes to raven-qt
   - *Mining* for changes to the mining code
   - *Net* or *P2P* for changes to the peer-to-peer network code
   - *RPC/REST/ZMQ* for changes to the RPC, REST or ZMQ APIs
@@ -78,7 +81,7 @@ Examples:
 
     Consensus: Add new opcode for RIP-XXXX OP_CHECKAWESOMESIG
     Net: Automatically create hidden service, listen on Tor
-    Qt: Add feed bump button
+    GUI: Add feed bump button
     Trivial: Fix typo in init.cpp
 
 Note that translations should not be submitted as pull requests, please see
@@ -169,11 +172,11 @@ workload on reviewing.
 "Decision Making" Process
 -------------------------
 
-The following applies to code changes to the Raven Core project (and related
-projects such as libsecp256k1), and is not to be confused with overall Raven
+The following applies to code changes to the Ravencoin project (and related
+projects) and is not to be confused with overall Ravencoin
 Network Protocol consensus changes.
 
-Whether a pull request is merged into Raven Core rests with the project merge
+Whether a pull request is merged into Ravencoin rests with the project merge
 maintainers and ultimately the project lead.
 
 Maintainers will take into consideration if a patch is in line with the general
@@ -191,7 +194,7 @@ In general, all pull requests must:
   - Where bugs are fixed, where possible, there should be unit tests
     demonstrating the bug and also proving the fix. This helps prevent regression.
 
-Patches that change Raven consensus rules are considerably more involved than
+Patches that change Ravencoin consensus rules are considerably more involved than
 normal because they affect the entire ecosystem and so must be preceded by
 extensive mailing list discussions and have a numbered RIP. While each case will
 be different, one should be prepared to expend more time and effort than for
@@ -232,9 +235,9 @@ higher in terms of discussion and peer review requirements, keeping in mind that
 mistakes could be very costly to the wider community. This includes refactoring
 of consensus critical code.
 
-Where a patch set proposes to change the Raven consensus, it must have been
-discussed extensively on the mailing list and Discord, be accompanied by a widely
-discussed RIP and have a generally widely perceived technical consensus of being
+Where a patch set proposes to change the Ravencoin consensus, it must have been
+discussed extensively, be accompanied by a widely discussed RIP and 
+have a generally widely perceived technical consensus of being
 a worthwhile change based on the judgement of the maintainers.
 
 ### Finding Reviewers
@@ -263,7 +266,7 @@ about:
     [Git Blame feature](https://help.github.com/articles/tracing-changes-in-a-file/). Simply
     find the person touching the code you are touching before you and see if you can find
     them and give them a nudge. Don't be incessant about the nudging though.
-  - Finally, if all else fails, ask on IRC or elsewhere for someone to give your pull request
+  - Finally, if all else fails, ask on Discord or elsewhere for someone to give your pull request
     a look. If you think you've been waiting an unreasonably long amount of time (month+) for
     no particular reason (few lines changed, etc), this is totally fine. Try to return the favor
     when someone else is asking for feedback on their code, and universe balances out.
@@ -272,7 +275,7 @@ about:
 Release Policy
 --------------
 
-The project leader is the release manager for each Raven Core release.
+The RavenQT-SIG selects a release manager for each Ravencoin release.
 
 Copyright
 ---------

README.md

@@ -28,6 +28,8 @@ The `master` branch is regularly built and tested, but is not guaranteed to be
 completely stable. [Tags](https://github.com/RavenProject/Ravencoin/tags) are created
 regularly to indicate new official, stable release versions of Raven Core.
 
+Active development is done in the `develop` branch. 
+
 The contribution workflow is described in [CONTRIBUTING.md](CONTRIBUTING.md).
 
 Developer IRC is inactive please join us on discord in #development. https://discord.gg/fndp4NBGct
@@ -40,9 +42,7 @@ requests than we can review and test on short notice. Please be patient and help
 other people's pull requests, and remember this is a security-critical project where any mistake might cost people
 lots of money.
 
-Testnet is now up and running and available to use during development. There is an issue when connecting to the testnet that requires the use of the -maxtipage parameter in order to connect to the test network initially. After the initial launch the -maxtipage parameter is not required.
-
-Use this command to initially start ravend on the testnet. <code>./ravend -testnet -maxtipage=259200</code>
+Testnet is up and running and available to use during development.
 
 ### Automated Testing
 

doc/README.md

@@ -36,12 +36,9 @@ sudo apt update
 sudo apt install libevent-dev libboost-all-dev libminiupnpc10 libzmq5 software-properties-common
 ```
 
-The wallet requires version 4.8 of the Berkeley DB. The easiest way to get it is from the bitcoin repository:
+The wallet requires version 4.8 of the Berkeley DB. The easiest way to get it is to build it with the script contrib/install_db4.sh
+
 
-```
-sudo add-apt-repository ppa:bitcoin/bitcoin
-sudo apt update
-sudo apt install libdb4.8-dev libdb4.8++-dev
 ```
 
 The GUI wallet requires the QR Code encoding library. Install with:

doc/benchmarking.md

@@ -1,7 +1,7 @@
 Benchmarking
 ============
 
-Raven Core has an internal benchmarking framework, with benchmarks
+Ravencoin has an internal benchmarking framework, with benchmarks
 for cryptographic algorithms such as SHA1, SHA256, SHA512 and RIPEMD160. As well as the rolling bloom filter.
 
 After compiling raven-core, the benchmarks can be run with:

doc/bips.md

@@ -1,4 +1,4 @@
-BIPs that are implemented by Raven Core (up-to-date up to **v0.13.0**):
+BIPs that are implemented by Ravencoin (up-to-date up to **v0.13.0**):
 
 * [`BIP 9`](https://github.com/bitcoin/bips/blob/master/bip-0009.mediawiki): The changes allowing multiple soft-forks to be deployed in parallel have been implemented since **v0.12.1**  ([PR #7575](https://github.com/bitcoin/bitcoin/pull/7575))
 * [`BIP 11`](https://github.com/bitcoin/bips/blob/master/bip-0011.mediawiki): Multisig outputs are standard since **v0.6.0** ([PR #669](https://github.com/bitcoin/bitcoin/pull/669)).

doc/developer-notes.md

@@ -489,13 +489,10 @@ Subtrees
 ----------
 
 Several parts of the repository are subtrees of software maintained elsewhere.
-
-Some of these are maintained by active developers of Raven Core, in which case changes should probably go
-directly upstream without being PRed directly against the project.  They will be merged back in the next
-subtree merge.
+They will be merged back in the next subtree merge.
 
 Others are external projects without a tight relationship with our project.  Changes to these should also
-be sent upstream but bugfixes may also be prudent to PR against Raven Core so that they can be integrated
+be sent upstream but bugfixes may also be prudent to PR against Ravencoin so that they can be integrated
 quickly.  Cosmetic changes should be purely taken upstream.
 
 There is a tool in contrib/devtools/git-subtree-check.sh to check a subtree directory for consistency with
@@ -709,7 +706,3 @@ A few guidelines for introducing and reviewing new RPC interfaces:
   - *Rationale*: If a RPC response is not a JSON object then it is harder to avoid API breakage if
     new data in the response is needed.
 
-
-IRC Required Commit
----------------------
-Required to register on IRC

doc/fuzzing.md

@@ -1,4 +1,4 @@
-Fuzz-testing Raven Core
+Fuzz-testing Ravencoin
 ==========================
 
 A special test harness `test_raven_fuzzy` is provided to provide an easy

doc/gitian-building.md

@@ -20,7 +20,7 @@ The size of some in-memory caches can be reduced. As caches trade off memory usa
 
   - Do not use this when using the client to broadcast transactions as any transaction sent will stick out like a sore thumb, affecting privacy. When used with the wallet it should be combined with `-walletbroadcast=0` and `-spendzeroconfchange=0`. Another mechanism for broadcasting outgoing transactions (if any) should be used.
 
-- Since `0.14.0`, unused memory allocated to the mempool (default: 300MB) is shared with the UTXO cache, so when trying to reduce memory usage you should limit the mempool, with the `-maxmempool` command line argument.
+- Since bitcoin `0.14.0`, unused memory allocated to the mempool (default: 300MB) is shared with the UTXO cache, so when trying to reduce memory usage you should limit the mempool, with the `-maxmempool` command line argument.
 
 ## Number of peers