Open Stack

Hi

I would like to announce my candidacy for the Orchestration (Heat) PTL.

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.

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.

Some of my activity artifacts:
https://review.openstack.org/#/q/owner:sbaker%2540redhat.com,n,z
https://review.openstack.org/#/q/reviewer:sbaker%2540redhat.com,n,z
http://russellbryant.net/openstack-stats/heat-reviewers-180.txt

Icehouse
--------

During the next cycle, I see these activities as among those the team
need to consider:
- Growing the core team to match the level of new contributions
- Focus on documentation including a comprehensive template writers guide
- Resource implementations for all the things, ideally contributed from
outside the core developers
- Finishing the HOT template format design and implementation
- Evaluating the suitability of TaskFlow[1] for Heat
- Native autoscaling, with associated autoscaling API.
- For projects and cloud providers that adopt Heat, ensuring their needs
are being met
- Ensuring all Heat features can be used without making any reference to
CloudFormation/AWS
- Make Heat templates multi-region and multi-cloud aware

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.

[1] https://wiki.openstack.org/wiki/TaskFlow
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130924/3e808d45/attachment.html>