<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 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 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.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
font-family:"Calibri","sans-serif";}
@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">Tom,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I agree! <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Josh and I did a presentation with examples in ATL (<a href="http://www.confreaks.com/videos/3695-openstacksummitatl2014-core-via-crowd-sourcing-defcores-tempest-in-a-docker-container-tcup">http://www.confreaks.com/videos/3695-openstacksummitatl2014-core-via-crowd-sourcing-defcores-tempest-in-a-docker-container-tcup</a>
) and I gave an updated version at OSCON (<a href="http://www.slideshare.net/rhirschfeld/oscon-2014-def-core-review">http://www.slideshare.net/rhirschfeld/oscon-2014-def-core-review</a>)
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">These are also discussed on my blog at <a href="http://www.slideshare.net/rhirschfeld/oscon-2014-def-core-review">
http://www.slideshare.net/rhirschfeld/oscon-2014-def-core-review</a> <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Please let me know if those examples help explain the use of the mark better.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks<o:p></o:p></p>
<p>> -----Original Message-----<br>
> From: Tom Fifield [mailto:tom@openstack.org]<br>
> Sent: Thursday, August 14, 2014 6:14 PM<br>
> To: defcore-committee@lists.openstack.org<br>
> Subject: Re: [OpenStack-DefCore] Please review, results from <br>
> Designated Sections review w/ recommendations. +1s needed<br>
> <br>
> Hi Rob,<br>
> <br>
> Can you provide a few example uses of the commercial marks based on below?<br>
> <br>
> eg "I can call my cloud "OpenStack Powered" without regard to the use <br>
> of Keystone."<br>
> <br>
> <br>
> I'm also interested in any practical implementation concerns you think <br>
> can arise based on the below suggestions.<br>
> <br>
> For example, in the case of an "OpenStack Powered" cloud that offers <br>
> an object store that is not swift, would they be recommended/required <br>
> to denote that actually that particular bit was not "Openstack Powered"?<br>
> <br>
> I could see that being confusing for users, and my guess is there <br>
> might be some similar cases that should be managed :)<br>
> <br>
> <br>
> Regards,<br>
> <br>
> <br>
> Tom<br>
> <br>
> On 15/08/14 04:54, Rob_Hirschfeld@Dell.com wrote:<br>
> > DefCore,<br>
> ><br>
> ><br>
> ><br>
> > We had a small turn out and very good discussions that were able to <br>
> > produce clear guidance for Designated Sections (see below). We also <br>
> > reviewed the Havana capabilities from the board meeting and the 10 <br>
> > designated sections principles approved by email. Finally, we setup <br>
> > a calendar for community review leading up to the September Board <br>
> > meeting<br>
> ><br>
> ><br>
> ><br>
> > Here are the recommendations:<br>
> ><br>
> > · Havana Nova is by default designated except scheduler, filter,<br>
> > drivers, API extensions and networking.<br>
> ><br>
> > · Havana Swift has no designated code due to lack of consensus<br>
> > (see principles)<br>
> ><br>
> > · Havana Keystone is not designated.<br>
> ><br>
> > · Havana Glance designated sections are the API implementation<br>
> > code and domain model.<br>
> ><br>
> > · Havana Cinder designated sections are the API implementation code<br>
> ><br>
> > · Havana Neutron has no designated sections.<br>
> ><br>
> > · Havana Heat is not a core capability, no position at this time.<br>
> ><br>
> > · Havana Horizon is not a core capability, no position at this time.<br>
> ><br>
> > · other projects do not are not core capabilities and are not<br>
> > reviewed at this time.<br>
> ><br>
> ><br>
> ><br>
> > Please contribute to a discussion or +1<br>
> ><br>
> ><br>
> ><br>
> > Rob<br>
> ><br>
> > *______________________________*<br>
> ><br>
> > *Rob Hirschfeld*<br>
> ><br>
> > Sr. Distinguished Cloud Solution Architect<br>
> ><br>
> > *Dell*| Cloud Edge, Data Center Solutions**<br>
> ><br>
> > *cell*+1 512 909-7219 *blog* robhirschfeld.com, *twitter* @zehicle<br>
> ><br>
> > Please note, I am based in the CENTRAL (-6) time zone<br>
> <br>
> <br>
> _______________________________________________<br>
> Defcore-committee mailing list<br>
> Defcore-committee@lists.openstack.org<br>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee<o:p></o:p></p>
</div>
</body>
</html>