Jump to: navigation, search

Governance/InteropWG

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?

  • Read the (pending) white paper and (pending) watch the video about DefCore.
  • Join the [DefCore] list
  • Join #refstack on Freenode IRC
  • Follow PlanetOpenStack DefCore Tag (instructions pending)
  • Follow the 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
  • 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.
    • no proxies

Process Cycles

Spider

Previous

Elephant

Current

Future

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