Jump to: navigation, search


< Governance
Revision as of 00:12, 27 November 2013 by Markmc (talk | contribs) (How to Engage?: - fix link to list)

This Committee was formed during the OpenStack Ice House Summit in Hong Kong by Board Resolution on 11/4.

Our mission is to define "OpenStack Core" as chartered by the by-laws and guided by Governance/CoreDefinition

This page is work in process....

How to Engage?

> There is a lot of pending items here...

  • Read the (pending) white paper and (pending) watch the video about DefCore.
  • Join the [defcore-committee] list
  • Join #refstack on Freenode IRC
  • Follow PlanetOpenStack DefCore Tag (instructions pending)
  • Follow the code at https://github.com/openstack-ops/refstack (instructions pending)
  • Register your user and then upload your test results to RefStack.org (instructions pending)

Governance Process

  • Meetings will be interactive using Google Hangouts (we will already stream for non-committee members)
  • Members are expected to to their homework. We will _not_ be rehashing due to time limits.
  • Meetings will work from resolutions that are proposed in advance with +/- voting (cochairs are +/-2)
    • as per Board of Directors policy, we welcome broad engagement but cannot allow proxies on resolutions
    • resolution +/- could be asserted before the meeting (but may have to be overruled based on discussion)

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 (previous, Fall 2013)


  1. Find a consensus approach to moving forward on DefCore
  2. Define process by which Core will be defined

Elephant (current, Spring 2014)


  1. If needed, change the bylaws to reflect the Spider Core Principles
  2. Establish the "must-pass" tests, processes and tools
    1. Define tests that will be used to determine core based on Spider cycle work
  3. Lower the water in the discussion to expose broader issues
    1. Clearly identity "elephants" that we are not ready to resolve in this cycle


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

  • OpenStack Compatible Mark
  • ... Committee Chairs will add to this ...

Meetings/Agenda Schedule

Meeting 11/20 prep

  1. Agenda / Notes / Minutes [[1][Committee Structure Planning]]

Meeting 12/3 8:30 - 10:30 PDT Agenda (tentative)

  1. Approve Timeline for Implementation for Havana & Icehouse
  2. Bylaws change - Discuss Bylaws change proposal
  3. Kick off the test selection criteria sub-committee
  4. RefStack.org review / demo
  5. Question: do we need to have multiple levels?
    1. if so, Need to decide on naming for levels of compliance. E.g.: "core/concensus" and "commons" and "edge"
  6. Define a process by which
    1. programs are nominated for use with the mark
    2. by which tests certified for use with the mark
    3. test list is vetted and approved by the board

Meeting 12/17 3pm PDT Agenda (tentative)

  1. Committee resolves bylaws changes to advance to Board
    1. Board will have to meet after (or electronically) to setup community vote on change
  2. OIN impacts from Core/Commons definition