<div dir="ltr"><div>I like it, too. I thought we needed something like that, but couldn't think of a way to make it sound good. I was thinking more the legalese and Mark found the right mix.<br><br></div>--rocky<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Dec 7, 2016 at 5:54 PM, Egle Sigler <span dir="ltr"><<a href="mailto:ushnishtha@hotmail.com" target="_blank">ushnishtha@hotmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="auto">
<div></div>
<div>I like that as well!</div><div><div class="h5">
<div><br>
On Dec 7, 2016, at 3:01 PM, Catherine Cuong Diep <<a href="mailto:cdiep@us.ibm.com" target="_blank">cdiep@us.ibm.com</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<p><tt>++ on using “OpenStack Powered (TM) Guidelines”. The name clearly articulates the goal and the originator of the guidelines.</tt><br>
<br>
Catherine Diep<br>
<font size="2" color="#800080">----- Forwarded by Catherine Cuong Diep/San Jose/IBM</font><font size="2" color="#800080"> on 12/07/2016 12:07 PM</font><font size="2" color="#800080"> -----</font><br>
<br>
<font size="2" color="#5F5F5F">From: </font><font size="2">Mark Voelker <<a href="mailto:mvoelker@vmware.com" target="_blank">mvoelker@vmware.com</a>></font><br>
<font size="2" color="#5F5F5F">To: </font><font size="2">Egle Sigler <<a href="mailto:ushnishtha@hotmail.com" target="_blank">ushnishtha@hotmail.com</a>></font><br>
<font size="2" color="#5F5F5F">Cc: </font><font size="2">"<a href="mailto:defcore-committee@lists.openstack.org" target="_blank">defcore-committee@lists.<wbr>openstack.org</a>" <<a href="mailto:defcore-committee@lists.openstack.org" target="_blank">defcore-committee@lists.<wbr>openstack.org</a>></font><br>
<font size="2" color="#5F5F5F">Date: </font><font size="2">12/07/2016 06:45 AM</font><br>
<font size="2" color="#5F5F5F">Subject: </font><font size="2">Re: [OpenStack-DefCore] Interop - Guideline Rename Workstream</font><br>
</p>
<hr style="color:#8091a5" width="100%" size="2" noshade align="left">
<br>
<br>
<br>
<tt><br>
<br>
<br>
> On Dec 6, 2016, at 6:02 PM, Egle Sigler <<a href="mailto:ushnishtha@hotmail.com" target="_blank">ushnishtha@hotmail.com</a>> wrote:<br>
> <br>
> Hello Luz,<br>
> <br>
> Thank you for working on this! I think "OpenStack Interoperability Guidelines”<br>
<br>
Likewise. I also like the idea of providing a UI hint (a label, bold text, something) to make these a bit more distinct in the interface.<br>
<br>
<br>
> or just "Interoperability Guidelines" would work, but I am also interested to hear what others think.<br>
<br>
Another thought: the Guidelines the Interop WG produces ultimately determine a product’s eligibility for the OpenStack Powered (TM) programs. We could refer to them as “OpenStack Powered (TM) Guidelines” which would help folks be clear on the relationship
between the two. <br>
<br>
At Your Service,<br>
<br>
Mark T. Voelker<br>
<br>
> <br>
> Thank you,<br>
> Egle<br>
> <br>
> <br>
> From: Cazares, Luz <<a href="mailto:luz.cazares@intel.com" target="_blank">luz.cazares@intel.com</a>><br>
> Sent: Friday, December 2, 2016 12:43 PM<br>
> To: <a href="mailto:defcore-committee@lists.openstack.org" target="_blank">defcore-committee@lists.<wbr>openstack.org</a><br>
> Subject: [OpenStack-DefCore] Interop - Guideline Rename Workstream<br>
> <br>
> Hello Everyone,<br>
> <br>
> As part of our rename work stream, we need a standard way to refer to the guidelines provided by this group.<br>
> <br>
> As we discussed in our last meeting [1]. “DefCore Guidelines” was a very specific name pointing to the guidelines from this group... so we need something at this level with the new name (not open to interpretation).<br>
> Some ideas:<br>
> · OpenStack Interop Guidelines<br>
> · Interoperability Guidelines<br>
> · Interop WG Guidelines<br>
> · Add label “Oficial” to differentiate our guideline from any other custom interop guideline.<br>
> <br>
> Please let me know your comments, concerns or any question (if any).<br>
> <br>
> [1] </tt><tt><a href="http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-11-30-16.00.log.txt" target="_blank">http://eavesdrop.openstack.<wbr>org/meetings/defcore/2016/<wbr>defcore.2016-11-30-16.00.log.<wbr>txt</a></tt><tt><br>
> <br>
> Thanks, Regards<br>
> Luz Cazares<br>
> ______________________________<wbr>_________________<br>
> Defcore-committee mailing list<br>
> <a href="mailto:Defcore-committee@lists.openstack.org" target="_blank">Defcore-committee@lists.<wbr>openstack.org</a><br>
> </tt><tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>defcore-committee</a></tt><tt><br>
<br>
______________________________<wbr>_________________<br>
Defcore-committee mailing list<br>
<a href="mailto:Defcore-committee@lists.openstack.org" target="_blank">Defcore-committee@lists.<wbr>openstack.org</a><br>
</tt><tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>defcore-committee</a></tt><tt><br>
</tt><br>
<br>
</div>
</blockquote>
</div></div></div>
<br>______________________________<wbr>_________________<br>
Defcore-committee mailing list<br>
<a href="mailto:Defcore-committee@lists.openstack.org">Defcore-committee@lists.<wbr>openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>defcore-committee</a><br>
<br></blockquote></div><br></div>