The OpenStack DefCore committee has been very active during this cycle turning the core definition principles into an actual list of “must-pass” capabilities (working page). This in turn gives the community something tangible enough to review and evaluate.
TL;DR! We appreciate those in the community who have been patient enough to help define and learn the process we’re using the make selections; however, we also recognize that most people want to jump to the results.
This week, we started a “DefCore roadshow” with the goal of learning how to make this huge body of capabilities, process and impact easier to digest (draft write-up for review & Troy Toman’s notes). So far we’ve had two great sessions on this topic. We took notes and recorded at both meetups (San Francisco & Austin).
My takeaways of these initial meetups are:
- Jump to the Capabilities right away, the process history is not needed up front
- You need more graphics – specifically, one for the selection criteria (what do you think of my 1st attempt?)
- Work from some examples of scored capabilities
- Include some specific use-cases with a user, 2 types of private cloud and a public cloud to help show the impact
Overall, people like what they are hearing. It makes sense and decisions are justified.
We need more feedback! Please help us figure out how to explain this for the broader community.