<html>
<head>

</head>
<body>
<div style="color: black;">
<div style="color: black;">
<p style="margin: 0 0 1em 0; color: black;">The ironic thing is the use of
"trademark program" pre-dates the use of program in OpenStack, and it
hasn't seemed to create a large problem to this point.</p>
<p style="margin: 0 0 1em 0; color: black;">Jonathan</p>
</div>
<div style="color: black;">
<p
style="color: black; font-size: 10pt; font-family: Arial, sans-serif; margin: 10pt 0;">On
October 16, 2014 11:05:28 PM Michael Still <mikal@stillhq.com> wrote:</p>
<blockquote type="cite" class="gmail_quote"
style="margin: 0 0 0 0.75ex; border-left: 1px solid #808080; padding-left: 0.75ex;"><div
dir="ltr">Given the term "program" is already in use in OpenStack
to describe something different, I think you need to find a different word
here.<div><br></div><div>Michael</div></div><div
class="gmail_extra"><br><div class="gmail_quote">On Fri, Oct 17, 2014 at
6:50 AM, <a href="mailto:rob@zehicle.com">rob@zehicle.com</a> <span
dir="ltr"><<a href="mailto:rob@zehicle.com"
target="_blank">rob@zehicle.com</a>></span> wrote:<br><blockquote
class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><u></u>
    
 
  
 
 <div>
 
  <div> 
   <p>DefCore,</p> 
   <p>Feedback is welcome!  I'm preparing the board report for the
meeting Monday (yikes, Monday!) and need to create the background info and
proposals for the meeting.</p> 
   <p>Here's the description I have for the change.  I'll send the
proposals out for review tomorrow.</p> 
   <p>--------------------------</p> 
   <p>During the post-meeting review, <a
href="https://docs.google.com/document/d/1WHVGwIxLSB0Dh9xVntxO5faM4pJjTe0yM0JwpsLUebA/edit?usp=sharing"
target="_blank">Mark Collier drafted a Foundation supported
recommendation</a> that basically creates an additional core
tier <em>without changing the fundamental capabilities & designated
code</em> concepts.  This proposal has been reviewed by the DefCore
committee (but not formally approved in a meeting).</p> 
   <p>The original DefCore proposed capabilities set becomes the
"platform" level while capability subsets are called
"programs."  We are considering two initial programs, Compute
& Object, and both are included in the platform (see illustration
below).  The approach leaves the door open for new core programs to exist
both under and outside of the platform umbrella.</p> 
   <p><a
href="https://robhirschfeld.files.wordpress.com/2014/10/defcore-platform-and-programs-v1-1.png"
target="_blank"><img height="437" alt="DefCore Platform and Programs v1.1"
width="584"
src="https://robhirschfeld.files.wordpress.com/2014/10/defcore-platform-and-programs-v1-1.png"
border="0"></a></p> 
   <p>In the proposal, OpenStack vendors who meet either program or
platform requirements can qualify for the "OpenStack Powered"
logo; however, vendors using the only a program (instead of the full
platform) will have more restrictive marks and limitations about how they
can use the term OpenStack.</p> 
   <p>This approach addresses the "is Swift required?" question. 
For platform, Swift capabilities will be required; however, vendors will be
able to implement the Compute program without Swift and implement the
Object program without Nova/Glance/Cinder.</p> 
   <p>It's important to note that there is only one yard stick for
programs or the platform: the capabilities groups and designed code defined
by the DefCore process.  From that perspective, OpenStack is one consistent
thing.  This change allows vendors to choose sub-components if that serves
their business objectives.</p> 
   <p> </p> 
  </div> 
  <div>
   <span style="font-size:9pt">Rob</span>
  </div> 
  <div>
   ____________________________
   <br>Rob Hirschfeld, 512-773-7522
   <br>
   <br>I am in CENTRAL (-6) time
   <br><a href="http://robhirschfeld.com"
target="_blank">http://robhirschfeld.com</a>
   <br>twitter: @zehicle, github: cloudedge & ravolt
  </div>
 
</div><br>_______________________________________________<br>
Defcore-committee mailing list<br>
<a
href="mailto:Defcore-committee@lists.openstack.org">Defcore-committee@lists.openstack.org</a><br>
<a
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee"
target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Rackspace
Australia
</div>

_______________________________________________<br>
Defcore-committee mailing list<br>
Defcore-committee@lists.openstack.org<br>
<a class="aqm-autolink aqm-autowrap"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee">http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee</a><br>
<br>
</blockquote>
</div>
</div>
</body>
</html>