I run the OpenStack Development Infrastructure
I currently work full-time on OpenStack for HP. I lead a team that works on running the Developer Infrastructure systems for the project, as well as teams working on OpenStack Deployment (TripleO) and OpenStack Bare Metal (Ironic). I am past PTL of the OpenStack Infra Program and set up the original project gating infrastructure. I currently sit on the Technical Committee. Previously, I was a core developer on Drizzle and was a Senior Consultant for MySQL, Inc. I've been a Python hacker by choice since 2000, and am currently a member of the Python Software Foundation.
I have a degree in Theatre Directing and went to grad school at CalArts in lighting design. The intersection of fields has led me to start more than one business around developing technology for and related to live performance. I continue to work in the theatre, and regularly light shows in New York, Seattle and Austin.
I'm involved in the following OpenStack projects: Openstack-ci
I have been with the project since the days when we were arguing over names. When we started things up, I set up the initial gating infrastructure and have either managed or been part of the management of the CI and developer infrastructure since then.
OpenStack's success is important to me because we're getting to this dangerous place where there are tons of services that are not open. The Internet changed everything, and ever since the emergence of the Web as the dominant form of communication, we've been slowly backsliding into the walled gardens we were before. If the only Clouds that are out there belong to the Googles and Amazons of the world, then they will be able to dictate what we build and when and how we deliver it. The web hasn't had a gatekeeper yet - and I don't think it's time that we gain one.
We MUST have an Open Source Cloud. OpenStack is best positioned to do that.
I've been on the OpenStack Foundation board since the formation of the Foundation, so I can tell you I'm as prepared as anyone to sit on it again.
I'm also a member of several arts related organizations. Notably, I'm a member of Seattle's Satori Group, which is a generative ensemble theatre collective. It turns out that all of the work that we do in OpenStack to ensure that people can effectively collaborate with each other in a way that's effective yet empowering to all participants is a topic that comes up a lot in enseble-based theatrical collectives. In many ways some of how we do things in OpenStack might even be influenced by that world ...
Being the voice of the business interests in collaboration with our technical meritocracy.
We have a meritocracy largely to ensure that participants from all of our businesses can come together and work on the common goal of an Open Source cloud. In order for the technical work to be successful, we have to keep the business bickering out of the tech. (or, like Jay famously said, we have to keep the dirty XML out of his JSON)
However, clouds aren't hobbyist software - and if we're not making things that serve the needs of our business community, then what are we doing? That's where the board comes in. 250 companies do not sit down with 2000 developers and get anything done. But, a board of directors can listen to the business community, synthesize it and be a body that can interface with the Technical Committee to produce a working conversation.
On the other hand of that conversation, in addition to providing a business voice to the TC, the Board also must take that information, formulate it into strategy and vision and manifest that in a trademark policy that makes the word OpenStack restritive enough to be meaningful, and flexible enough to allow competition in the marketplace.
If we can get those two things done, I think we're golden.
Articulating a clear narrative about what OpenStack is and where we want to go.
Monty has already been nominated by: