redirect and update source docs

doc/developer-notes.md

@@ -181,3 +181,5 @@ Tested ACK - Reviewed the code changes and have verified the functionality or bu
 ACK -  A loose ACK can be confusing. It's best to avoid them unless it's a documentation/comment only change in which case there is nothing to test/verify; therefore the tested/untested distinction is not there.
 
 NACK - Disagree with the code changes/concept. Should be accompanied by an explanation.
+
+See the [Development Guidelines](https://zcash.readthedocs.io/en/latest/rtd_pages/development_guidelines.html) documentation for preferred workflows, information on continuous integration and release versioning.

doc/dnsseed-policy.md

@@ -1,54 +1,6 @@
 Expectations for DNS Seed operators
 ====================================
 
-Zcash attempts to minimize the level of trust in DNS seeds,
-but DNS seeds still pose a small amount of risk for the network.
-As such, DNS seeds must be run by entities which have some minimum
-level of trust within the Zcash community.
+This document has been relocated to https://zcash.readthedocs.io/en/latest/rtd_pages/dnsseed_policy.html
 
-Other implementations of Zcash software may also use the same
-seeds and may be more exposed. In light of this exposure, this
-document establishes some basic expectations for operating DNS seeds.
-
-0. A DNS seed operating organization or person is expected to follow good
-host security practices, maintain control of applicable infrastructure,
-and not sell or transfer control of the DNS seed. Any hosting services
-contracted by the operator are equally expected to uphold these expectations.
-
-1. The DNS seed results must consist exclusively of fairly selected and
-functioning Zcash nodes from the public network to the best of the
-operator's understanding and capability.
-
-2. For the avoidance of doubt, the results may be randomized but must not
-single out any group of hosts to receive different results unless due to an
-urgent technical necessity and disclosed.
-
-3. The results may not be served with a DNS TTL of less than one minute.
-
-4. Any logging of DNS queries should be only that which is necessary
-for the operation of the service or urgent health of the Zcash
-network and must not be retained longer than necessary nor disclosed
-to any third party.
-
-5. Information gathered as a result of the operators node-spidering
-(not from DNS queries) may be freely published or retained, but only
-if this data was not made more complete by biasing node connectivity
-(a violation of expectation (1)).
-
-6. Operators are encouraged, but not required, to publicly document the
-details of their operating practices.
-
-7. A reachable email contact address must be published for inquiries
-related to the DNS seed operation.
-
-If these expectations cannot be satisfied the operator should discontinue
-providing services and contact the active Zcash development team as well as
-creating an issue in the [Zcash repository](https://github.com/zcash/zcash).
-
-Behavior outside of these expectations may be reasonable in some
-situations but should be discussed in public in advance.
-
-See also
-----------
-- [zcash-seeder](https://github.com/zcash/zcash-seeder) is a reference
-  implementation of a DNS seed.
+The source for this document is available at https://gitlab.com/zcash-docs/zcash-docs/blob/master/source/rtd_pages/dnsseed_policy.rst

doc/files.md

@@ -1,14 +1,5 @@
-* zcash.conf: contains configuration settings for zcashd
-* zcashd.pid: stores the process id of zcashd while running
-* blocks/blk000??.dat: block data (custom, 128 MiB per file)
-* blocks/rev000??.dat; block undo data (custom)
-* blocks/index/*; block index (LevelDB)
-* chainstate/*; block chain state database (LevelDB)
-* database/*: BDB database environment
-* db.log: wallet database log file
-* debug.log: contains debug information and general logging generated by zcashd
-* fee_estimates.dat: stores statistics used to estimate minimum transaction fees and priorities required for confirmation
-* peers.dat: peer IP address database (custom format)
-* wallet.dat: personal wallet (BDB) with keys and transactions
-* .cookie: session RPC authentication cookie (written at start when cookie authentication is used, deleted on shutdown): since 0.12.0
-* onion_private_key: cached Tor hidden service private key for `-listenonion`: since 0.12.0
+# Data Directory Files
+
+This document has been relocated to https://zcash.readthedocs.io/en/latest/rtd_pages/files.html
+
+The source for this document is available at https://gitlab.com/zcash-docs/zcash-docs/blob/master/source/rtd_pages/files.rst