<html>
<head>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi<br>
<br>
I would like to announce my candidacy for the Orchestration (Heat)
PTL.<br>
<br>
I have been a software engineer for 16 years and have been
developing on Heat for over 12 months. In this period Heat has grown
from a small project to being part of the OpenStack ecosystem with a
healthy growth in contributors and users. During this time my Heat
related development has led to productive relationships with
contributors from other projects including Horizon, Infrastructure,
Documentation, QA, TripleO and DevStack.<br>
<br>
The Heat core team has always performed well without the need for
prescriptive leadership. Consequently, I feel that this role's
primary function is to act as the point of contact with the greater
OpenStack community. There is also a need to facilitate the process
of reaching consensus, and to advocate for areas which are being
neglected. I'm already familiar with most of the tasks of a PTL
while filling in for others on several occasions and doing release
management for python-heatclient and heat-cfntools.<br>
<br>
Some of my activity artifacts:<br>
<a
href="https://review.openstack.org/#/q/owner:sbaker%2540redhat.com,n,z">https://review.openstack.org/#/q/owner:sbaker%2540redhat.com,n,z</a><br>
<a
href="https://review.openstack.org/#/q/reviewer:sbaker%2540redhat.com,n,z">https://review.openstack.org/#/q/reviewer:sbaker%2540redhat.com,n,z</a><br>
<a
href="http://russellbryant.net/openstack-stats/heat-reviewers-180.txt">http://russellbryant.net/openstack-stats/heat-reviewers-180.txt</a><br>
<br>
Icehouse<br>
--------<br>
<br>
During the next cycle, I see these activities as among those the
team need to consider:<br>
- Growing the core team to match the level of new contributions<br>
- Focus on documentation including a comprehensive template writers
guide<br>
- Resource implementations for all the things, ideally contributed
from outside the core developers<br>
- Finishing the HOT template format design and implementation<br>
- Evaluating the suitability of TaskFlow[1] for Heat<br>
- Native autoscaling, with associated autoscaling API.<br>
- For projects and cloud providers that adopt Heat, ensuring their
needs are being met<br>
- Ensuring all Heat features can be used without making any
reference to CloudFormation/AWS<br>
- Make Heat templates multi-region and multi-cloud aware<br>
<br>
Finally, despite the overwhelming correlation, and my temporary
desire for it to remain so, it is not considered mandatory for the
Heat PTL to be called Steve.<br>
<br>
[1]
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a href="https://wiki.openstack.org/wiki/TaskFlow">https://wiki.openstack.org/wiki/TaskFlow</a>
</body>
</html>