<html><body><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 <mvoelker@vmware.com></font><br><font size="2" color="#5F5F5F">To: </font><font size="2">Egle Sigler <ushnishtha@hotmail.com></font><br><font size="2" color="#5F5F5F">Cc: </font><font size="2">"defcore-committee@lists.openstack.org" <defcore-committee@lists.openstack.org></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><hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br><br><br><tt><br><br><br>> On Dec 6, 2016, at 6:02 PM, Egle Sigler <ushnishtha@hotmail.com> 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 <luz.cazares@intel.com><br>> Sent: Friday, December 2, 2016 12:43 PM<br>> To: defcore-committee@lists.openstack.org<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">http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-11-30-16.00.log.txt</a></tt><tt><br>> <br>> Thanks, Regards<br>> Luz Cazares<br>> _______________________________________________<br>> Defcore-committee mailing list<br>> Defcore-committee@lists.openstack.org<br>> </tt><tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee">http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee</a></tt><tt><br><br>_______________________________________________<br>Defcore-committee mailing list<br>Defcore-committee@lists.openstack.org<br></tt><tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee">http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee</a></tt><tt><br></tt><br><BR>
</body></html>