<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Trebuchet MS";
panose-1:2 11 6 3 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Comments in line: one typo, one suggestion at the end. I tried to separate the comments such that non-html mailers will at least see a good deal of spacing between original and comments.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">--Rocky<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Rob_Hirschfeld@Dell.com [mailto:Rob_Hirschfeld@Dell.com]
<br>
<b>Sent:</b> Monday, April 07, 2014 10:32 AM<br>
<b>To:</b> Defcore-committee@lists.openstack.org<br>
<b>Subject:</b> [OpenStack-DefCore] Working Session(s) & Doc Review Needed<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Defcore Committee,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We’ve got a small amount of work remaining to complete the capabilities matrix – we’ll need experts on object and volume to complete. I’d like to see if we can get together early next week for a working session.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">ALSO, please review the community communication doc about the Capabilities for publication
<i>next week</i>:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><a href="https://docs.google.com/document/d/1rxDkjcgPlYKuEmcV_Nigp1bSoMRrV7iyJMQ8fzwTr9M/edit?usp=sharing">https://docs.google.com/document/d/1rxDkjcgPlYKuEmcV_Nigp1bSoMRrV7iyJMQ8fzwTr9M/edit?usp=sharing</a> (I’m copying the text to this
email too, but please direct comments to the online version)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Trebuchet MS","sans-serif";color:#444444">Rob<o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Trebuchet MS","sans-serif";color:#444444"><o:p> </o:p></span></b></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.5pt;font-family:"Arial","sans-serif";color:blue">> note: this material will be used to introduce the Capabilities Scorecard to the community for review. We need to give enough background
but make the </span><span style="font-size:11.5pt;font-family:"Arial","sans-serif";color:black">scorecard
</span><span style="font-size:11.5pt;font-family:"Arial","sans-serif";color:blue">the center of the information</span><span style="font-size:11.5pt;font-family:"Arial","sans-serif";color:black">.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:21.0pt;font-family:"Trebuchet MS","sans-serif";color:black">Introducing the DefCore Capabilities Scorecard & Core Identification Matrix
</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><b><i><span style="font-size:11.5pt;font-family:"Arial","sans-serif";color:black">Insert reference to other docs here, including Mark Collier’s post:
</span></i></b><a href="https://www.openstack.org/blog/author/sparkycollier/"><b><i><span style="font-size:11.5pt;font-family:"Arial","sans-serif";color:#1155CC">https://www.openstack.org/blog/author/sparkycollier/</span></i></b></a><b><i><span style="font-size:11.5pt;font-family:"Arial","sans-serif";color:black">
</span></i></b><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.5pt;font-family:"Arial","sans-serif";color:black">The
</span><a href="https://www.openstack.org/blog/author/sparkycollier/%20"><span style="font-size:11.5pt;font-family:"Arial","sans-serif";color:#1155CC">OpenStack Core definition process</span></a><span style="font-size:11.5pt;font-family:"Arial","sans-serif";color:black">
(aka DefCore) is moving steadily along and we’re looking for feedback from community as we move into the next phase. Until now, we’ve been mostly working out principles, criteria and processes that we will use to answer “what is core” in OpenStack. Now we
are applying those processes and actually picking which tests will be used to identify Core.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.5pt;font-family:"Arial","sans-serif";color:black">TL;DR: We are now RUNNING WITH SCISSORS because we’ve reached the point there you
</span><span style="font-size:11.5pt;font-family:"Arial","sans-serif";color:#1F497D"><o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:red"> ^where<o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.5pt;font-family:"Arial","sans-serif";color:black">can see what’s going to be considered Core (and what’s not). We now have tangible draft lists for community review.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.5pt;font-family:"Arial","sans-serif";color:black">While you will want to jump directly to the results, it is important to understand how we got here because that’s how DefCore will resolve
the inevitable conflicts. The very nature of defining core means that we have to say “not in” to a lot of capabilities. Since community consensus seems to favor a “small core” in principle, that means many capabilities that people consider important are
not included.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.5pt;font-family:"Arial","sans-serif";color:black">The Core Identification Matrix attempts to find the right balance between quantitative detail and too much information. Each row represents
an “OpenStack Capability” that is reflected by one or more individual tests. We scored each capability on a 100 point scale using 13 different criteria. These criteria were selected to respect different viewpoints and needs of the community ranging from
popularity, technical longevity and quality of documentation. </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.5pt;font-family:"Arial","sans-serif";color:black">While we’ve made the process more analytical, there’s still room for judgement. Eventually, we expect to weight some criteria more heavily
than others. We will also be adjusting the score cut-off. Our goal is not to create a perfect evaluation tool - it should inform the board and facilitate discussion. In practice, we’ve found this approach to bring needed objectivity to the selection process.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.5pt;font-family:"Arial","sans-serif";color:black">So, where does this take us? The first matrix is, by design, old news. We focused on getting a score for Hanava to give us a stable and
known quantity; however, much of that effort will translate forward. Using Havana as the base, we are hoping to score Ice House ninety days after the Juno summit and score Juno at K Summit in Paris. </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.5pt;font-family:"Arial","sans-serif";color:black">These are ambitious goals and there are challenges ahead of us.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.5pt;font-family:"Arial","sans-serif";color:black">Specifically, we know there are gaps in OpenStack test coverage. Important capabilities do not have tests and will not be included. Further,
starting with a small core means that OpenStack will be enforcing an interoperability target that is relatively permissive and minimal. It’s vital to remember that we are looking for evolutionary progress that accelerates our developer, user, operator and
ecosystem communities. </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.5pt;font-family:"Arial","sans-serif";color:black">How can you get involved? We are looking for community feedback on this 1st pass - we do not think we have the scores 100% right.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:12.0pt;color:red">I’d also like to see under How can you get involved?
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:12.0pt;color:red"> 1) feedback:
</span><span style="font-size:12.0pt;color:red">We are looking for community feedback on this 1st pass - we do not think we have the scores 100% right. We will accept feedback in many areas: what’s in/what’s out, weighting, missing/different weighting, etc</span><span style="font-size:12.0pt;color:black">.
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:12.0pt;color:red">2) tests: If you think we missed some area that should be core, check out the tests. If there are none or few, write some tests so that the functionality can be validated.
Functionality can’t be considered as core until it can be validated.</span><span style="font-size:12.0pt;color:red"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.5pt;font-family:"Arial","sans-serif";color:black">We will eventually use RefStack to collect voting/feedback on capabilities directly from OpenStack community members.</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>