OpenStack DefCore Committee has established the principles and first artifacts required for vendors using the OpenStack trademark.  Over the next release cycle, we will be applying these to the Ice House and Juno releases.

Learn more?  Hear about it LIVE!  Rob will be doing two sessions about DefCore next week (will be recorded):

1. Tues Dec 16 at 9:45 am PST- OpenStack Podcast #14 with Jeff Dickey
2. Thurs Dec 18 at 9:00 am PST – Online Meetup about DefCore with Rafael Knuth (optional RSVP)

At the December 2014 OpenStack Board meeting, we completed laying the foundations for the DefCore process that we started April 2013 in Portland. These are a set of principles explaining how OpenStack will select capabilities and code required for vendors using the name OpenStack. We also published the application of these governance principles for the Havana release.

1. The OpenStack Board approved DefCore principles to explain
   the landscape of core including test driven capabilities and designated code (approved Nov 2013)
2. the twelve criteria used to select capabilities (approved April 2014)
3. the creation of component and framework layers for core (approved Oct 2014)
4. the ten principles used to select designated sections (approved Dec 2014)

To test these principles, we’ve applied them to Havana and expressed the results in JSON format: Havana Capabilities and Havana Designated Sections. We’ve attempted to keep the process transparent and community focused by keeping these files as text and using the standard OpenStack review process.

DefCore’s work is not done and we need your help!  What’s next?

1. Vote about bylaws changes to fully enable DefCore (change from projects defining core to capabilities)
2. Work out going forward process for updating capabilities and sections for each release (once authorized by the bylaws, must be approved by Board and TC)
3. Bring Havana work forward to Ice House and Juno.
4. Help drive Refstack process to collect data from the field