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 member of the OpenStack Foundation Board of Directors, a Python Fellow and past member the OpenStack Technical Committee. Monty is the PTL of the 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 here since the very very beginning and have worked since we started as an End User, a Deployer, a Developer, a TC member and a Board member.
OpenStack's mission has never been more relevant or important. Freedom inside of a walled garden isn't enough.
The proprietary public clouds have already infected the mindset of the industry with otherwise rational people believing that second rate approaches, such as always shoving network traffic through NAT, are not only acceptable but actively desirable. It's like the entire industry is suffering from a collective Stockholm Syndrome where rather than fighting for good people have decided to embrace terrible and make decisions purely based on fashion trends.
Free and Open cloud infrastructure is essential for the world's next generation to be able to write and deliver software using the full power of the state of computing art.
I hope that my contributions will be seen in the fullness of time to have advanced our cause. I'm personally proud of having instituted our gating-oriented development process and having been a (potentially overly) loud voice in support of our cloud's End Users and the important of OpenStack clouds behaving consistently.
As we were founding OpenStack I was a member of a non-profit experiemental theatre collective in Seattle. It would probably surprise people just how many of OpenStack's technical processes can find some root in the needs of collaboratively generating new work as an ensemble.
In fact, most of my personal history has been in and around non-profits, mostly in the Arts. Luckily OpenStack hasn't need a bake sale to raise money for an East Coast tour yet, but should we find ourselves in that position I've got us covered.
I've served on the board for all but one year of its existence, having taken a year off in 2017. I think it's very helpful to have a sense of history when discussing new and exciting challenges. While the details are different, many of the conceptual issues we're about to face with the potential graduation of new Top Level projects are ones we've debated and grappled with for years ... and it seems might continue to grapple with for years to come.
I believe we've reached the point in the hype curve where it's essential that the Board provide an outward voice of support. It can be trendy to be negative towards OpenStack, ignoring the massive success and global reach we have achieved.
The Board consists of a wonderful array of people from different backgrounds, industries and geographies, and as such needs to behave as a bidirectional conduit. As Board members it's essential that we remind the world that OpenStack is running large swaths of the world. It's important that we remind the world the importance of Free Software at the center of our global infrastructure. And it's important that we facilitate the flow of information about people's successes and challenges with OpenStack inwards so that we can continue to deliver world class software for years to come.
Finally, I think it's important for the Board to Not Panic. Chasing the latest tech-press fashions is a losing proposition. Being confident in and who and what we are - and having the strength of character to not try to be something we are not - is an essential role for the Board in our otherwise tumultuous world.
As one of the founders of the Zuul project, I believe how we manage the impending graduation or lack thereof of our new Pilot Projects will define how the OpenStack Foundation operates for the next few years. The opportunities to continue serving our mission are great, but so are the possibilities of becoming mired in overhead or losing a coherent sense of who we are.
While we do that, we must ensure that we're continuing to grow and support our primary raison d'etre, the OpenStack project itself. I would like the see the board strongly encourage our technical communities to leverage the efficiencies provided by direct collaboration and eschew the short-sighted urge for going it alone that has become so prevalent in our modern ego-aggrandizement driven version of Open Source.
Monty has already been nominated by: