I’ve been leading an effort with Alan Clark to define “what is OpenStack core” for the Foundation Board. Now that I am sitting here at OSCON and celebrating OpenStack’s third birthday, I think it’s a great time to bring the general community into the discussion.
There is significant history behind this topic. According to Foundation governance, the Technical Committee (TC) defines which incubated projects are integrated and the Board of Directors (I am one) determines which of the integrated projects are labeled as core.
When it comes to the core label, the stakes are high.
Defining core is a convoluted topic. To make it digestible, I’m breaking it down into multiple blog posts over a series of weeks:
- Why do we care about core?
- Decomposing the problem (“the spider”)
- Insights from decomposition (healthy tensions in OpenStack)
- 12 Positions: A Common Framework (I recommend ready the list of 10 instead)
- Community Feedback at OSCON
- “What is Core” the visualization
- Where I think this is going, OpenStack’s Test Driven Core
- Core Positions Refined: the 10 positions behind the core visualization (above).
- Videos (most >90 mins). The online meetups are easier to follow.
- Thinking about how to Implement OpenStack Core Definition