interop/ProcessCycles.rst
Chris Hoge f5e3d09e48 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
2015-04-09 19:03:23 -07:00

2.7 KiB

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

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

Scale Cycle (Spring 2015)

Objectives

  • Capabilities for I & J
  • Process approved by TC & Board

Meetings

Future

Names to be decided when we get there. Topics that are intentionally pushed into the future:

  • OpenStack API Mark