<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=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
        {font-family:Wingdings;
        panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
        {font-family:Wingdings;
        panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","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";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {mso-style-priority:99;
        mso-style-link:"Balloon Text Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:8.0pt;
        font-family:"Tahoma","sans-serif";}
span.apple-converted-space
        {mso-style-name:apple-converted-space;}
span.EmailStyle18
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.BalloonTextChar
        {mso-style-name:"Balloon Text Char";
        mso-style-priority:99;
        mso-style-link:"Balloon Text";
        font-family:"Tahoma","sans-serif";}
.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;}
/* List Definitions */
@list l0
        {mso-list-id:596256624;
        mso-list-template-ids:1922302306;}
@list l0:level1
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l0:level2
        {mso-level-number-format:bullet;
        mso-level-text:o;
        mso-level-tab-stop:1.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:"Courier New";
        mso-bidi-font-family:"Times New Roman";}
@list l0:level3
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:1.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l0:level4
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:2.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l0:level5
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:2.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l0:level6
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:3.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l0:level7
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:3.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l0:level8
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:4.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l0:level9
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:4.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l1
        {mso-list-id:760300059;
        mso-list-template-ids:-2103303382;}
@list l1:level1
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l1:level2
        {mso-level-number-format:bullet;
        mso-level-text:o;
        mso-level-tab-stop:1.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:"Courier New";
        mso-bidi-font-family:"Times New Roman";}
@list l1:level3
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:1.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l1:level4
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:2.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l1:level5
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:2.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l1:level6
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:3.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l1:level7
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:3.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l1:level8
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:4.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
@list l1:level9
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:4.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Wingdings;}
ol
        {margin-bottom:0in;}
ul
        {margin-bottom:0in;}
--></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="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">+1 on the points and rationale discussed at the end of your email (snipped).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";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>
<p class="MsoNormal"><a name="_____replyseparator"></a>So how will the contract language re: requirements change as defcore, the board, and community arrive at a consensus on “what’s next”?  Here’s what i expect:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<ul type="disc">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
It is my expectation that A) will stay as-is. <span style="font-size:11.0pt;color:#535353">
 "</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#535353">A primary purpose of your product must be to run a functioning operational instance of the OpenStack software.</span><span style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#535353">”</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#535353"> We
 could tweak it but I </span><span style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#535353">think</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#535353"> it</span><span style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#535353">’</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#535353">s
 pretty clear.</span><o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#535353">It is my expectation that c) will stay as-is "</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#535353">You must clearly state which OpenStack projects
 and versions are used to set customer expectations, in a way that is conspicuous to customers.</span><span style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#535353">”</span><o:p></o:p></li></ul>
<ul type="disc">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo2">
<span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#535353">And that everything </span><span style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#535353">under</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#535353"> b, </span><span style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#535353">which</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#535353"> deals
 with capabilities/code/apis today </span><span style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#535353">will</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#535353"> be re-written to </span><span style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#535353">reflect</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#535353"> the
 required </span><span style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#535353">capabilities</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#535353">, APIs, and code inclusion once those are approved (note that
 Icehouse is the first expected enforceable version, as the Havana stuff being </span><span style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#535353">discussed</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#535353"> </span><span style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#535353">today</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#535353"> is </span><span style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#535353">“</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#535353">advisory</span><span style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#535353">”</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#535353"> meaning
 it wouldn</span><span style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#535353">’</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#535353">t be a contract requirement). I am working on this language in conjunction
 with our </span><span style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#535353">trademark</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#535353"> attorney (with placeholders for the actual things that are in or
 out, pending a decision there) and will socialize it with the ecosystem and defcore.  We might </span><span style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#535353">actually want to take the specificity out of the agreement itself and point
 instead to a web page where the details are posted, so that we can get this moving faster and not over burden the agreement itself.</span><o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;text-align:justify;mso-list:l1 level1 lfo2">
<span style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#535353">My expectation is that d) will be re-written to more accurately reflect the expected testing requirements and mechanisms.  Frankly, if we just put the tests  and steps up on the
 page </span><span style="font-family:"Calibri","sans-serif";color:#535353"><a href="http://OpenStack.org/FITS"><span style="font-size:11.5pt">OpenStack.org/FITS</span></a></span><span style="font-size:11.5pt;font-family:"Calibri","sans-serif";color:#535353"> then
 I’m not sure how much change this language needs. That said, we should decide if this is still the standard for freshness and re-testing we want to have "Your product will be required to pass the current FITS test on an annual basis, which will generally require
 you to be running either of the latest two software releases. “</span><o:p></o:p></li></ul>
</div>
</div>
</div>
</div>
</body>
</html>