move the vision from reference to resolution

We want to make it clear that the vision document is a point-in-time
document, and not meant to be updated as a living document. We will
produce new visions in the future.

Change-Id: I34117506468a78c42968acc8dacb7bfc40a8e613
Signed-off-by: Doug Hellmann <doug@doughellmann.com>

reference/index.rst

@@ -10,7 +10,6 @@ Reference documents which need to be revised over time.
    opens
    principles
    charter
-   technical-committee-vision-2019
    projects/index
    new-projects-requirements
    new-language-requirements

resolutions/20170404-vision-2019.rst

@@ -1,7 +1,7 @@
 
-=====================================
- Technical Committee Vision for 2019
-=====================================
+===========================================================
+ Technical Committee Vision for 2019 (Drafted April, 2017)
+===========================================================
 
 This document was written in June of 2017 as if it were created in
 March 2019, looking back at what the OpenStack Technical Committee has been
@@ -10,6 +10,11 @@ yet realistic end goal. It doesn't intend to list out all the tasks needed to
 reach the end goal, nor does it intend to stop evolving the direction as the
 enviroment changes between now and 2019.
 
+.. note::
+
+   This is the vision of the TC from April 2017. Future TCs may
+   publish new visions for the future.
+
 To help with setting the context of this vision, please review these documents:
 
 * `Why and How Visioning Works <https://www.zingtrain.com/content/why-and-how-visioning-works>`_

resolutions/index.rst

@@ -7,6 +7,15 @@
 When a motion does not result in a change in a reference doc, it can
 be expressed as a resolution.
 
+2017
+====
+
+.. toctree::
+   :maxdepth: 1
+   :glob:
+
+   2017*
+
 2016
 ====