Metering, Oslo, and other cross-project activities.
Doug Hellmann is currently employed by HP to work on OpenStack. He has been programming in Python since version 1.4, and has worked on a variety of Unix and non-Unix platforms for projects in fields such as mapping, medical news publishing, banking, and data center automation. Doug is a member of the Python Software Foundation, and served as its Communications Director from 2010-2012. After a year as a regular columnist for Python Magazine, he served as Editor-in-Chief from 2008-2009. Between 2007 and 2011, Doug published the popular "Python Module of the Week" series on his blog, and that material served as the basis for his book "The Python Standard Library By Example". He lives in Athens, Georgia.
Doug started contributing to OpenStack in 2012, just before the Folsom summit. He is a core reviewer and one of the founding members of the Ceilometer project, and a core reviewer for the requirements and unified command line interface projects. He is on the stable release maintenance team, part of the team working on the Python 3 transition, and has contributed to several of the infrastructure projects. He has served as the PTL for the Oslo project for the Icehouse and Juno releases.
I'm involved in the following OpenStack projects: Nova,Keystone,Quantum,Ceilometer,Oslo,Openstack-ci
My commitment to OpenStack's success is a reflection of the fact that this community is the most collaborative group I have been involved with since I started working on open source projects in the early 1990s. I want OpenStack to be successful to show that investing in a community is the right approach for building large scale software projects.
My most obvious contribution is being part of the team that created Ceilometer. In addition to the design and coding work there was a lot to be done to formalize the process of bringing new projects into OpenStack.
I am also proud to have played a small role at the beginning of the travel aid program, which made it possible for several ATCs to attend summits when they might not have been able otherwise.
I am a member of the Python Software Foundation, and served as Communications Director for two years. Although I was not on the PSF board, I did interact with the board regularly as part of my duties as Communications Director so I could report the board's decisions to the rest of the members and broader Python community.
The community has some important decisions to make about the direction and rate of our growth, and how to ensure that all community members can find a way to be successful at the same time. The board's role in this is to balance the needs of the contributors with the needs of the project as a whole when setting policies.
There are two primary issues to be resolved in the next year. The work started this year on adjusting our board election procedures needs to be completed to ensure the long-term health of the project. The other priority should be establishing guidelines for vendors, deployers, and hosting providers using the OpenStack trademark (commonly known as the "defining core" question).
Doug has already been nominated by: