From f5e3d09e48bf8eeab759a23b073fa9ed13c4b640 Mon Sep 17 00:00:00 2001
From: Chris Hoge <chris.hoge@puppetlabs.com>
Date: Thu, 9 Apr 2015 19:03:23 -0700
Subject: [PATCH] Move Governance/CoreDefinition into gerrit

At the April 8, 2015 DefCore Scale.11 meeting, the DefCore committee
decided to migrate some existing wiki artifacts into
gerrit.  This patch represents one such migration.  This patch
reproduces content previously housed at the following URL in RST
so that it can be placed more easily in source control:

https://wiki.openstack.org/wiki/Governance/DefCoreCommittee#Process_Cycles

Change-Id: I4eeb9ff3698191ffff0cd6651ff72e233a1a007a
---
 ProcessCycles.rst | 116 ++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 116 insertions(+)
 create mode 100644 ProcessCycles.rst

diff --git a/ProcessCycles.rst b/ProcessCycles.rst
new file mode 100644
index 00000000..4a607c1a
--- /dev/null
+++ b/ProcessCycles.rst
@@ -0,0 +1,116 @@
+Process Cycles
+==============
+
+Defining OpenStack Core is a long term process and we are doing the work
+in progressive cycles. For reference, we have named the cycles. This
+helps describe concrete deliverables for a cycle while allowing
+discussion of the broader long term issues. For example, we may say that
+"item X is important to DefCore but out of scope for Elephant." We have
+found that this approach to breaking down the problem is necessary to
+maintain community consensus because we are taking smaller bites of the
+larger challenge (aka eating the elephant).
+
+Spider (Fall 2013)
+------------------
+
+Objectives
+~~~~~~~~~~
+
+  * Find a consensus approach to moving forward on DefCore
+
+  * Define process by which Core will be defined
+
+Elephant (Spring 2014)
+----------------------
+
+Objectives
+~~~~~~~~~~
+
+  * If needed, change the bylaws to reflect the Spider Core Principles
+
+  * Establish the "must-pass" tests, processes and tools
+
+  * Define tests that will be used to determine core based on Spider
+    cycle work
+
+  * Lower the water in the discussion to expose broader issues
+
+  * Clearly identity "elephants" that we are not ready to resolve in this cycle
+
+Meetings
+~~~~~~~~
+
+  * https://etherpad.openstack.org/p/DefCoreElephant.2
+
+  * https://etherpad.openstack.org/p/DefCoreElephant.3
+
+  * https://etherpad.openstack.org/p/DefCoreElephant.4
+
+  * https://etherpad.openstack.org/p/DefCoreElephant.5
+
+Lighthouse (Fall 2014)
+----------------------
+
+Objectives
+~~~~~~~~~~
+
+  * Complete Capabilities Score for Havana (Advisory), Icehouse and
+    Juno
+
+  * Recommend by-laws changes for winter voting
+
+  * Launch refstack site for data collection and sharing
+
+Meetings
+~~~~~~~~
+
+  * https://etherpad.openstack.org/p/DefCoreLighthouse.1
+
+  * https://etherpad.openstack.org/p/DefCoreLighthouse.2
+
+  * https://etherpad.openstack.org/p/DefCoreLighthouse.3
+
+  * https://etherpad.openstack.org/p/DefCoreLighthouse.Bylaws1
+
+  * https://etherpad.openstack.org/p/DefCoreLighthouse.F2F
+
+  * https://etherpad.openstack.org/p/DefCoreBylawsIPE
+
+Scale Cycle (Spring 2015)
+-------------------------
+
+Objectives
+~~~~~~~~~~
+
+  * Capabilities for I & J
+
+  * Process approved by TC & Board
+
+Meetings
+~~~~~~~~
+
+  * https://etherpad.openstack.org/p/DefCoreScale.1
+
+  * https://etherpad.openstack.org/p/DefCoreScale.2
+
+  * https://etherpad.openstack.org/p/DefCoreScale.3
+
+  * https://etherpad.openstack.org/p/DefCoreScale.4
+
+  * https://etherpad.openstack.org/p/DefCoreScale.F2F
+
+  * https://etherpad.openstack.org/p/DefCoreScale.5
+
+  * https://etherpad.openstack.org/p/DefCoreScale.6
+
+  * https://etherpad.openstack.org/p/DefCoreScale.7
+
+  * https://etherpad.openstack.org/p/DefCoreScale.8
+
+Future
+------
+
+Names to be decided when we get there. Topics that
+are intentionally pushed into the future:
+
+  * OpenStack API Mark