<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Oct 28, 2016, at 3:15 PM, Gema Gomez <<a href="mailto:gema.gomez-solano@linaro.org" class="">gema.gomez-solano@linaro.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hi all,<br class=""><br class="">at the contributors meetup for QA we have been discussing about whether<br class="">to keep the heat tests that are meant to be for interoperability in<br class="">tempest tree or not. An interesting discussion arised from that.<br class=""><br class="">We are having a discussion (with gmann and oomichi) about whether heat<br class="">could be considered core project or not (if it was core, there would be<br class="">no problem). They have shared this post with us as the definition they<br class="">are using of "core project" they are using:<br class=""><a href="https://dague.net/2014/08/26/openstack-as-layers/" class="">https://dague.net/2014/08/26/openstack-as-layers/</a><br class=""><br class="">Can someone clarify whether this definition is still valid or whether we<br class="">don't use it anymore? Is there any more up to date definition? Any<br class="">comment or clarification welcome.<br class=""></div></div></blockquote><div><br class=""></div>The Defcore/Interop Working Group scores capabilities against a set of</div><div>criteria, and if the score is high enough the capability is considered</div><div>for inclusion into the DefCore/Interop guidelines. [1]</div><div><br class=""></div><div>After an advisory period, a capability can become required, at which</div><div>point a product that obtains the “OpenStack Powered” trademark</div><div>against that guideline is required to provide that capability.</div><div><br class=""></div><div>Any project that provides a required DefCore capability could be</div><div>considered “core” in that regard, but the coreness of that project</div><div>and capability may or may not match up with current opinions on</div><div>what a core OpenStack project is.</div><div><br class=""></div><div>As far as I know, there is no official TC definition of what a core project is.</div><div><br class=""></div><div>-Chris</div><div><br class=""></div><div>[1] <a href="http://git.openstack.org/cgit/openstack/defcore/tree/doc/source/process/CoreCriteria.rst" class="">http://git.openstack.org/cgit/openstack/defcore/tree/doc/source/process/CoreCriteria.rst</a></div><div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><br class="">Cheers,<br class="">Gema<br class=""><br class="">-- <br class="">Gema Gomez-Solano<br class="">Tech Lead, SDI<br class="">Linaro Ltd<br class="">IRC: gema@#linaro on <a href="http://irc.freenode.net" class="">irc.freenode.net</a><br class=""><br class="">_______________________________________________<br class="">Defcore-committee mailing list<br class=""><a href="mailto:Defcore-committee@lists.openstack.org" class="">Defcore-committee@lists.openstack.org</a><br class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee<br class=""></div></div></blockquote></div><br class=""></body></html>