I run the OpenStack Development Infrastructure
Monty currently leads the team that works on the Zuul project for CI/CD in Red Hat's CTO Office. He's the founder, core member and past PTL of the OpenStack Infra team which runs CI and developer tooling for OpenStack. He's a past member of both the OpenStack Technical Committee and the OpenStack Foundation Board of Directors. Monty is the PTL of the shade/python-openstacksdk project and is the maintainer of the Ansible modules for consuming OpenStack. Before his OpenStack days he was a core developer on Drizzle and was a Senior Consultant for MySQL, Inc.
Monty has a degree in Theatre Directing and went to grad school at CalArts in lighting design. The intersection of fields has led him to start more than one business around developing technology for and related to live performance. Recently Monty served as an Adjunct Professor at NYU's Tisch School of the Arts teaching a class on programming related to lighting design. If you let him, he'll talk to you WAY too much about Scuba Diving.
I've been involved with OpenStack since Jay Pipes and Eric Day left the Drizzle team to work on the next version of Rackspace Cloud Servers and then asked what I thought about using a software project from NASA instead of writing one from scratch. (That's my founder story ... I know Lauren loves it when we tell them)
OpenStack's success is essential to the health of our industry. As much as it seems like Open Source won and everything is Open Source now, what seemed to many to be tinfoil-hat fears about the Tivo-ization of software have also come to pass with gusto. People who otherwise care about Open Source are inexplicably perfectly ok using closed source services.
We are working on an Open Source Cloud Operating system, and we expect deployers to run interoperable copies of the upstream source code. This is a shining beacon at a time where Open Source is increasingly a thing to exploit, a catchphrase to use for marketing reasons, or a badge to hang on a VC valuation.
For my entire time with OpenStack I have been an advocate for the Four Opens, for ensuring that we are actually Open Source and not merely Open Core. I have worked to ensure that use of non-Free software is not required to either develop or run OpenStack.
We Are OpenStack, and the work I have done to date has been in service of that remaining true.
Together we serve as a proof positive that one does not need to enslave oneself to the whims of a closed product to build either software or a community around it. Together we show the world that Open Source, Open Process and Open Infrastructure are not only valid, but vital, vibrant and vivacious. Together we are a global force, and by working together we bring out the best in each other.
I will continue to be a voice for freedom. Freedom matters. The "Open" in OpenStack isn't just convenient marketing or a momentarily advantagous way to work ... it's why I'm working on this, and it's why I think what we're doing is important.
Other than my years on the OpenStack Foundation Board of Directors, I have an extensive background in the non-profit Theatre world. That may seem irrelevant, but I promise, a room full of developers, a room full of board members, and a room full of actors are all remarkably similar.
Ensuring the strength of the OpenStack brand. For a brand to have real strength, people must be able to understand what it means and what is communicated by something being branded OpenStack when something else isn't.
We're at a crossroads (as we so often are) on this topic. The word OpenStack has come to mean a pleothera of things. It is the name of the Foundatoin, of the primary piece of software we ship, the community of developers and operators, and the developer infrastructure we use to build things. While there is a great amount of overlap, there is also a great amount of distinction. Each of those provide real value, but the overlap brings with it lack of clarity and confusion.
Navigating the waters of who we are, what we do and what the word OpenStack means is the most fundamental and important work in front of the Board.
Handling the proposed expansion of top level technical projects in such a way that we bring exciting new humans in to our midst while not abandoning the things that make us who we are.
Monty has already been nominated by: