<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">I want to make sure that all on the DefCore committee is aware of Technical Governance changes that may impact how DefCore accomplishes its job.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The TC and developer community have been discussing “small core, big tent” for a while (about 9 months) and have released documents that direct how it intends to move forward with the changes. Here are links to some of those documents,
either approved or still in flight. The items on the governance pages are approved and currently implemented or being implemented. There is still a lot of uncertainty as to how the TC will manage/direct all the cascading changes required.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Organizational changes:<o:p></o:p></p>
<p class="MsoNormal"><a href="http://governance.openstack.org/resolutions/20141202-project-structure-reform-spec.html">http://governance.openstack.org/resolutions/20141202-project-structure-reform-spec.html</a>
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">New project tag “Integrated-Release”:<o:p></o:p></p>
<p class="MsoNormal"><a href="http://governance.openstack.org/reference/tags/integrated-release.html">http://governance.openstack.org/reference/tags/integrated-release.html</a>
<o:p></o:p></p>
<p class="MsoNormal">Note on the above, the last section lists the “integrated” projects for Kilo.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">These specify the new process for a project to “join” OpenStack. They no longer will be moved to the OpenStack repositories, but can remain in stackforge. All contributors to stackforge projects will<o:p></o:p></p>
<p class="MsoNormal"><a href="https://wiki.openstack.org/wiki/Governance/NewProjectTeams">https://wiki.openstack.org/wiki/Governance/NewProjectTeams</a>
<o:p></o:p></p>
<p class="MsoNormal">And requirements needed to be met:<o:p></o:p></p>
<p class="MsoNormal"><a href="http://governance.openstack.org/reference/new-projects-requirements.html">http://governance.openstack.org/reference/new-projects-requirements.html</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">supporting discussions:<o:p></o:p></p>
<p class="MsoNormal"><a href="https://etherpad.openstack.org/p/project-restructure-hangouts">https://etherpad.openstack.org/p/project-restructure-hangouts</a>
<o:p></o:p></p>
<p class="MsoNormal">Note: There are discussions here about the expanding ATC base, the summit pass rules changes, etc.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Along with the new project process, there is also a new testing guidelines document that will be applied to all projects wanting to become part of OpenStack:<o:p></o:p></p>
<p class="MsoNormal"><a href="http://governance.openstack.org/reference/project-testing-interface.html">http://governance.openstack.org/reference/project-testing-interface.html</a>
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">QA is currently proposing changing the gates to only gate continuously on the “core projects”. They are trying to work out how to incorporate the non-core projects.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">QA changes:<o:p></o:p></p>
<p class="MsoNormal"><a href="https://review.openstack.org/#/c/152683/">https://review.openstack.org/#/c/152683/</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The other projects/programs identified as “horizontal” or spanning most or all other projects have not merged any specs on their process changes.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">--Rocky<o:p></o:p></p>
</div>
</body>
</html>