Preserve superseded resolutions

Rather than directly amending a previously-passed resolution, the TC
has decided the change should be a new resolution.

For the stackforge resolution, this commit adds the text of the
updated resolution as a new resolution with some introductory
explanatory text noting what the update is and the reason for it.
It also reverts the text of the original resolution to that which
was originally passed and adds a new section at the bottom of the
original resolution which indicates it is amended by a subsequent
resolution and links to it.

The superseded resolutions are placed in a specific folder for
clarity. The same process was applied to the Mission statement
resolution.

Change-Id: I446d0797554311b199fce999a7469dbf4e3a2d30

doc/source/index.rst

@@ -29,6 +29,7 @@ Reference documents and Resolutions
 
    reference/index
    resolutions/index
+   resolutions/superseded/index
 
 .. seealso::
 

resolutions/20160119-stackforge-retirement.rst

@@ -0,0 +1,60 @@
+.. _20160119_stackforge_resolution:
+
+============================================
+ 2016-01-19 Stackforge Namespace Retirement
+============================================
+
+Introduction
+============
+
+When the :ref:`20150615_stackforge_resolution` was originally adopted,
+the TC felt that the term "Stackforge" was still useful as a sort of
+shorthand for "the area where unofficial projects can develop before
+they became official".  In keeping with that, we have continued to
+refer to the hosting space for unofficial projects as "Stackforge".
+This has certainly resulted in people thinking our documentation was
+out of date, and has also likely resulted in missed opportunities to
+communicate that projects within openstack/ but not approved by the TC
+are unofficial, rather than official OpenStack projects.
+
+This updated resolution reflects the TC's revised intention to retire
+not only the "stackforge" namespace but also the term itself in favor
+of "unofficial project".
+
+Updated Resolution
+==================
+
+The Stackforge project provides an environment for projects to share
+the OpenStack project's development resources and methodology, and
+otherwise participate in the OpenStack community.  It enables projects
+to deeply interact with OpenStack in development and testing, whether
+they seek to become "core" OpenStack projects or not.
+
+This is an extremely valuable service that benefits our entire
+community, including new as well as established projects.
+
+With recent changes in project governance, the OpenStack project has
+opened itself to including a much wider range of projects under its
+umbrella.  Because of this, projects are moving between Stackforge and
+OpenStack at a much higher frequency than previously.
+
+The names of projects hosted in the OpenStack project infrastructure
+have prefixes that have been used for distinguishing Stackforge
+("stackforge/") and OpenStack ("openstack/") projects.  Because these
+prefixes form part of the full name of the project's source code
+repository, organizational changes entail renaming the project.  This
+is complex for the Infrastructure team and very disruptive to
+developers, operators, and users.
+
+In order to simplify software development lifecycle transitions of
+Unofficial and Official OpenStack projects, all projects developed
+within the OpenStack project infrastructure will be permitted to use
+the "openstack/" namespace.  The use of the term "Stackforge" to
+describe unofficial projects should be considered deprecated.
+
+The "openstack/" namespace is intended to convey that projects
+contained within it are hosted on OpenStack infrastructure.  Only some
+of the projects within will be official OpenStack projects
+themselves. As such, there should not be any new requirements such as
+CLA signing. This resolution should not alter the workflow of any of
+the projects.

resolutions/20160217-mission-amendment.rst

@@ -1,10 +1,12 @@
+.. _20160217_mission_amendment:
+
 ========================================
  2016-02-17 OpenStack Mission amendment
 ========================================
 
   .. note::
 
-    This is an update to :doc:`20160106-mission-amendment` in response to
+    This is an update to :ref:`20160106_mission_amendment` in response to
     feedback from the OpenStack Foundation Board of Directors and the following
     `discussion on the foundation mailing list
     <http://lists.openstack.org/pipermail/foundation/2016-February/002263.html>`_.

resolutions/superseded/20150615-stackforge-retirement.rst

@@ -1,3 +1,5 @@
+.. _20150615_stackforge_resolution:
+
 ============================================
  2015-06-15 Stackforge Namespace Retirement
 ============================================
@@ -25,10 +27,9 @@ is complex for the Infrastructure team and very disruptive to
 developers, operators, and users.
 
 In order to simplify software development lifecycle transitions of
-Unofficial and Official OpenStack projects, all projects developed
-within the OpenStack project infrastructure will be permitted to use
-the "openstack/" namespace.  The use of the term "Stackforge" to
-describe unofficial projects should be considered deprecated.
+Stackforge and OpenStack projects, all projects developed within the
+OpenStack project infrastructure will be permitted to use the
+"openstack/" namespace.
 
 The "openstack/" namespace is intended to convey that projects
 contained within it are hosted on OpenStack infrastructure.  Only some
@@ -36,3 +37,8 @@ of the projects within will be official OpenStack projects
 themselves. As such, there should not be any new requirements such as
 CLA signing. This resolution should not alter the workflow of any of
 the projects.
+
+Updates
+=======
+
+This resolution is amended by :ref:`20160119_stackforge_resolution`.

resolutions/superseded/20160106-mission-amendment.rst

@@ -1,3 +1,5 @@
+.. _20160106_mission_amendment:
+
 ========================================
  2016-01-06 OpenStack Mission amendment
 ========================================
@@ -27,3 +29,7 @@ the adoption of the following wording::
   simple to implement and massively scalable while serving the cloud users'
   needs.
 
+Updates
+=======
+
+This resolution is amended by :ref:`20160217_mission_amendment`.

resolutions/superseded/index.rst

@@ -0,0 +1,12 @@
+========================
+ Superseded Resolutions
+========================
+
+This is a list of resolutions which were superseded by more recent
+resolutions.
+
+.. toctree::
+   :maxdepth: 1
+   :glob:
+
+   *