<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Simon,<div><br></div><div>While I love the tenor of your approach, I think we need at least three more:</div><div><br></div><div>1. Distributions (which I consider to be Red Hat, Canonical, and SUSE only) are currently shipping 100% of the integrated release, and they’ve expressed interest in a mark that represents that. So your proposed “OpenStack Software” mark would more likely fit *products* (Piston OpenStack, CloudScaling OCS, Nebula One, etc).</div><div><br></div><div>2. The proposed OpenStack Compute and OpenStack Storage would also need to apply to software and hardware products (as opposed to services) such as IBM’s whatever-that-thing-is-called. </div><div><br></div><div>I think it’s increasingly confusing to refer to swift-related things as “Storage”, since that excludes Cinder- or Manila-related things.<br><div apple-content-edited="true">
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div><div>An alternative approach would be to have just three marks:</div><div><br></div><div> - OpenStack Distribution (100% of the integrated release)</div><div> - Certified OpenStack (what’s currently covered by DefCore, being core capabilities and designated sections)</div><div> - Powered by OpenStack Components (includes one or more of the core capabilities with the relevant designated sections for each capability)</div><div><br></div><div>The third mark would be a replacement for “OpenStack Compute”, “OpenStack Storage”, etc, and would prevent mark sprawl.</div><div><br></div><div>--</div><div><br></div><div>Joshua McKenty</div><div>Chief Technology Officer</div><div>Piston Cloud Computing, Inc.</div><div>+1 (650) 242-5683</div><div>+1 (650) 283-6846</div><div><a href="http://www.pistoncloud.com">http://www.pistoncloud.com</a></div><div><br></div><div>"Oh, Westley, we'll never survive!"<br>"Nonsense. You're only saying that because no one ever has."</div></div></div>
</div>
<br><div><div>On Sep 22, 2014, at 10:43 PM, Simon Anderson <<a href="mailto:simon@dreamhost.com">simon@dreamhost.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Rob, I may have heard a different output from the Board call - which was that the Foundation staff would work on some multi-TM proposals and share them with the DefCore committee/Board. So Jonathan, Mark and Lauren may already be working on them.<div><br></div><div>Personally, I think having more than one trademark usage doesn't undermine the great work of DefCore so far. My thoughts on a simple multi-TM structure that might serve the market are:</div><div><ul><li>OpenStack Software (TM) for distributions, that would include all designated sections and core capabilities;</li><li>OpenStack Compute (TM) for services running all designated sections and core capabilities *except for* OpenStack Storage designated sections/core capabilities;</li><li>OpenStack Storage (TM) for services running the object storage designated sections and core capabilities (essentially SWIFT).</li></ul><div><br></div></div></div><div class="gmail_extra"><br clear="all"><div><div dir="ltr"><div><br>Best,</div><div>Simon<br></div></div></div>
<br><div class="gmail_quote"><div><div class="h5">On Mon, Sep 22, 2014 at 2:09 PM, <span dir="ltr"><<a href="mailto:Rob_Hirschfeld@dell.com" target="_blank">Rob_Hirschfeld@dell.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
<div lang="EN-US" link="blue" vlink="purple">
<div><p class="MsoNormal">All,<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Last Thursday, the board did not act on any of our recommendations. The Board is reconsidering one of the guiding principles from Hong Kong – DefCore is trying to define a minimum base definition for OpenStack. Instead, they’ve asked
us for multiple Trademark proposals.<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">ACTION ITEM: I’d be interested in hearing suggestions from the committee that we can use as the basis for a etherpad.
<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Towards that end, I think we should schedule a meeting on Thursday 10/2. I’m open to having a working session before that to brainstorm options (possibly with Mark or Jonathan).<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">I’d ask you to consider two items in preparation:<u></u><u></u></p><p><u></u><span>1)<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>Sean Dague’s Layers Model: <a href="https://dague.net/2014/08/26/openstack-as-layers/" target="_blank">
https://dague.net/2014/08/26/openstack-as-layers/</a> <u></u><u></u></p><p><u></u><span>2)<span style="font:7.0pt "Times New Roman"">
</span></span><u></u>Consideration of OpenStack as a product or “big tent” which seems to be part of the OpenStackSV output: Monty
<a href="http://inaugust.com/post/108" target="_blank">http://inaugust.com/post/108</a> and Randy
<a href="http://siliconangle.com/blog/2014/09/17/the-achilles-heel-of-openstack-is-lack-of-product-leadership-openstacksv/" target="_blank">
http://siliconangle.com/blog/2014/09/17/the-achilles-heel-of-openstack-is-lack-of-product-leadership-openstacksv/</a>
<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Trebuchet MS","sans-serif";color:#444444">Rob<u></u><u></u></span></p><p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Trebuchet MS","sans-serif";color:#444444">______________________________<u></u><u></u></span></b></p><p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Trebuchet MS","sans-serif";color:#444444">Rob Hirschfeld<u></u><u></u></span></b></p><p class="MsoNormal"><b><span style="font-size:8.0pt;font-family:"Trebuchet MS","sans-serif";color:#444444">cell</span></b><span style="font-size:8.0pt;font-family:"Trebuchet MS","sans-serif";color:#aaaaaa">
</span><span style="font-size:8.0pt;font-family:"Trebuchet MS","sans-serif";color:#444444"><a href="tel:%2B1%20512%20909-7219" value="+15129097219" target="_blank">+1 512 909-7219</a>
<b>blog</b> <a href="http://robhirschfeld.com/" target="_blank">robhirschfeld.com</a>, <b>twitter</b> @zehicle<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Trebuchet MS","sans-serif";color:#444444">Please note, I am based in the CENTRAL (-6) time zone
<u></u><u></u></span></p><p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
<br></div></div>_______________________________________________<br>
Defcore-committee mailing list<br>
<a href="mailto:Defcore-committee@lists.openstack.org" target="_blank">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></div>
</blockquote></div><br></div></div>
_______________________________________________<br>Defcore-committee mailing list<br><a href="mailto:Defcore-committee@lists.openstack.org">Defcore-committee@lists.openstack.org</a><br>http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee<br></blockquote></div><br></div></body></html>