Moved section on joining Pharos community out of configguide.rst so that it does...

Change-Id: I7114f561cbeae81a2c8e0c67624e22ae0cc54a22
Signed-off-by: Trevor Cooper <trevor.cooper@intel.com>
(cherry picked from commit 6732859ab09ddb890ad4c67e2834059f57175bd6)

diff --git a/docs/configguide/configguide.rst b/docs/configguide/configguide.rst
index 5971590..3f1c035 100644 (file)
--- a/docs/configguide/configguide.rst
+++ b/docs/configguide/configguide.rst
@@ -9,19 +9,7 @@ Lab Setup Guide
 Provides an overview for setting up a Pharos lab. A full set of
 :ref:`pharos_master` documents are maintained in the *pharos* repo.
 
-Contributing to the Pharos Community
-------------------------------------
-
-The development, test and production activities rely on Pharos resources and support from the Pharos community. Lab
-owners and Pharos project committers/contributors will evolve the vision for Pharos as well as expand lab capabilities
-that are needed to help OPNFV be highly successful.
-
-* Jira is used to track Pharos activities including lab operations
-* PODs are connected to Jenkins and generally available 24/7 other than scheduled maintenance and troubleshooting
-* Lab resources are declared as either for *Development (bare-metal or virtual)*, *Production latest (bare-metal)* or *Production stable (bare-metal)*
-
-Declaring a Pharos Lab
-----------------------
+When setting up an OPNFV community lab ...
 
 * Provide the Pharos community with details of the intended setup, including ...
 

diff --git a/docs/configguide/pharosconfig.rst b/docs/configguide/pharosconfig.rst
index 1f8c166..6b0783d 100644 (file)
--- a/docs/configguide/pharosconfig.rst
+++ b/docs/configguide/pharosconfig.rst
@@ -8,7 +8,14 @@
 Pharos Configuration
 ********************
 
-Pharos configuration documents provide information on how to setup hardware and networks in a Pharos compliant lab
+OPNFV development, test and production activities rely on Pharos resources and support from the Pharos community. Lab
+owners and Pharos project committers/contributors will evolve the vision for Pharos as well as expand lab capabilities
+that are needed to help OPNFV be highly successful.
+
+Pharos configuration documents provide information on how to setup hardware and networks in a Pharos compliant lab. Jira
+is used to track Pharos activities including lab operations. PODs are connected to Jenkins and generally available 24/7
+other than scheduled maintenance and troubleshooting. Lab resources are declared as either for *Development (bare-metal
+or virtual)*, *Production latest (bare-metal)* or *Production stable (bare-metal)*
 
 .. toctree::