<div class="ace-line" id="magicdomid37"><span class="author-a-oz73zm69mz68zz73zgz65zz71zz72zoz66zcz88z">I thought I would get some input on a draft statement before submitting one for the TC to vote on.<br><br>We're very focused on using OpenStack components in the delivery as much as possible - growing the capabilities of OpenStack rather than working around things; so I've captured that in the mission statement. While we're focused on trunk deploys today, I think that is more tactical than mission-level : we'd be totally happy to work with releases (as well) should interested people want to step up and help maintain stable branches of the tripleo heat templates etc.<br>
<br>So - here is the draft:<br><br>Official Title: OpenStack Deployment</span></div><div class="ace-line" id="magicdomid93"><span class="author-a-oz73zm69mz68zz73zgz65zz71zz72zoz66zcz88z">PTL: Robert Collins <<a href="mailto:robertc@robertcollins.net">robertc@robertcollins.net</a>></span></div>
<div class="ace-line" id="magicdomid25"><span class="author-a-oz73zm69mz68zz73zgz65zz71zz72zoz66zcz88z">Mission Statement:</span></div><div class="ace-line" id="magicdomid129"><span class="author-a-oz73zm69mz68zz73zgz65zz71zz72zoz66zcz88z">  Develop and maintain the tooling and infrastructure needed to</span></div>
<div class="ace-line" id="magicdomid236"><span class="author-a-oz73zm69mz68zz73zgz65zz71zz72zoz66zcz88z">  deploy OpenStack in production, using OpenStack itself wherever</span></div><div class="ace-line" id="magicdomid250">
<span class="author-a-oz73zm69mz68zz73zgz65zz71zz72zoz66zcz88z">  possible.</span></div><br clear="all"><br>-- <br>Robert Collins <<a href="mailto:rbtcollins@hp.com" target="_blank">rbtcollins@hp.com</a>><br>Distinguished Technologist<br>
HP Cloud Services