<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>Technical Committee,</div>
<div><br>
</div>
<div>Please accept my proposal of a new type of project called a deployment [1]. If people don’t like the type name, we can change it. The basic idea is there are a class of projects unrepresented by type:service and type:library which are deployment projects
including but not limited to Fuel, Kolla, OSA, and TripleO. The main motivation behind this addition are:</div>
<ol>
<li>Make it known to all which projects are deployment projects in the governance repository.</li><li>Provide that information via the governance website under release management tags.</li><li>Permit deployment projects to take part in the assert tags relating to upgrades [2].</li></ol>
<div><br>
</div>
<div>Currently fuel is listed as a type:service in the governance repository which is only partially accurate. It may provide a ReST API, but during the Kolla big tent application process, we were told we couldn't use type:service as it only applied to daemon
services and not deployment projects.</div>
<div><br>
</div>
<div>Regards</div>
<div>-steve</div>
<br>
<div>[1] <a href="https://review.openstack.org/295528">https://review.openstack.org/295528</a></div>
<div>[2] <a href="https://review.openstack.org/295529">https://review.openstack.org/295529</a></div>
</body>
</html>