On 10/07/2013 08:24 PM, Doug Hellmann wrote:
I am announcing my candidacy for a position on the OpenStack Technical
I have been programming in Python professionally for 15 years, in a
variety of application areas, and am currently the development lead
for DreamHost's OpenStack-based public cloud project, DreamCompute. I
am a member of the Python Software Foundation, have been on the PyCon
Program Committee, and was Editor in Chief of Python Magazine. In June
of 2011, I published "The Python Standard Library by Example".
I started contributing to OpenStack in 2012, just before the Folsom
summit. I am 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. I am on the stable release
maintenance team for Grizzly, am part of the team working on the
Python 3 transition, and have contributed to several of the
infrastructure projects. I will be the PTL for the Oslo project
starting with the Icehouse release.
These development activities, combined with our deployment work at
DreamHost, have given me a unique cross-project perspective into
OpenStack, and reinforced for me the importance of consistency across
our components. One of the roles of the technical committee is to
encourage projects to find commonalities and adopt consistent
approaches or tools to make the project run more smoothly for all
contributors and users. Using consistent libraries, coding style, and
implementation patterns helps integrate new developers with our
community more quickly and encourages existing developers to
participate in more than one project. Using consistent tools helps our
infrastructure team create and maintain the automated systems that
have made OpenStack's impressive development velocity possible.
Consistent configuration tools also help packagers and deployers
consume what we are producing, making adoption easier. Consistent APIs
and UIs make it easier for end users to choose OpenStack clouds,
either public or private, over other options.
In addition to my code contributions, I am especially proud of the
work over the last year that went into bringing Ceilometer through
incubation to become an integrated project. Because we were one of the
earliest projects to go through formal incubation, much of the process
was still being developed as we were navigating it. I learned a lot
while contributing to that discussion. There are still some open
questions about how mature a project must be to enter incubation, and
what level of integration is needed before graduation. I look forward
to addressing those questions as we continue to grow as a community.
I share the view of many of the other candidates that OpenStack should
not limit itself to today's definition of IaaS. The history of
computing is a progression of different levels of abstraction, and
what we consider "platform" today may become "infrastructure" tomorrow.
I have found the OpenStack community to be the most welcoming group I
have interacted with in more than 20 years of contributing to open
source. I'm excited to be a part of OpenStack, and look forward to
continuing to contribute in whatever way I am able.
My commit history:
My review history:
My Ohloh account: https://www.ohloh.net/accounts/doughellmann
My blog: http://doughellmann.com/
OpenStack-dev mailing list
OpenStack-dev mailing list