 Next up, to hear about Zool is Monty Taylor. Come on out, Monty. Good one, sir. All right, I'm really deficient. I have no faulty cages in my talk, so I apologize about that. I am here to talk to you about, oh, there it goes. Yeah, that's exciting. I'm here to talk to you a little bit about Zool and what we've been doing over the last six months. Before I do that, I'm going to give you a little background on what Zool is for those of you who may not be aware of who we are. So Zool is a project gating system. We wrote it for the OpenSack project, as you're probably aware, since Mark talked about it earlier. It's a really big project. We get a lot of commits. We have a lot of contributors. And so we had to build some tools to deal with that. We built those based on some underlying principles about how we thought about developing software. First and foremost, we believe that free software needs free tools. So as we're building free software, as we're building the open source system of OpenSack, we believe that all of the tools that run that need to themselves be free. So to that end, Zool itself is open source, and will always remain that way. We believe very strongly in the OpenSack community that if something isn't tested, we should assume that it's broken. So Zool helps us ensure that every change that goes into OpenSack goes through testing before it lands. Finally, in the Zool world, we believe that clouds are useful for automation and that we should allow the humans to spend their time being creative. We have clouds to do repetitive tasks, so we should use them. We should maximize their use, freeing up the humans to do thinking things, to do creative things, to do design things, to do review things, rather than to waste their time doing repetitive tasks. So we built Zool to help the OpenSack project do this. It has some really special features in it. Specifically, it understands the idea that we have a collection of projects that work together to deliver a final result. And we need to be able to test those with each other, to be able to deliver features, and to be able to test that new features work across a stack of things before having to land and release those in independent projects. It's a very cool and unique feature of Zool. So in Vancouver, we announced Zool v3. We wrote Zool for OpenSack and for the needs of OpenSack, but other people were starting to use it, and it hadn't really been written with their needs in mind. So with Zool v3, we focused on actually making it something that was widely available and where the uses of people outside of the OpenSack community were taken into account as primary use cases. We released that in Vancouver, and as a result of that, we've had a whole bunch more people join us in, and it's been a lot of fun. Since then, we've done a lot of work. We've picked up a whole bunch of new friends, new community members, got a whole bunch of interesting people. We don't even know who all is using it now, which is great. It used to be the case that we knew each of the people who were using Zool, and now we don't. These are just a few. Several of these people will be talking this week at the summit about what they're doing. Since Vancouver, we added some features. I'm going to talk about a couple of them real specifically. The first one, we've had a pluggable pipeline managers in Zool since the very beginning, since six and a half years ago. But it actually is the last plugin that we wrote a new plugin type for. In this cycle, we wrote one called the Supercedent Pipeline Manager. This is really useful in post-commit processing, so things like documentation publication, artifact publication, where if four or five commits land while you're still processing the event for the first one, you don't really need to build the docs four or five more times before publishing them. So the Supercedent Pipeline Manager allows us to only do that type of task once for each of the collection of triggers. We made a feature called JobPause. There's use cases where you need to do things like have the top of the stack create, say a Docker registry or a YAM repository, put some artifacts into it, and then have subsequent jobs consume those. JobPause allows you to structure jobs doing that in whatever way your job needs to do. We rewrote our web dashboard in React. This allows it to eat much less of my laptop's battery when I'm on a plane, and also gave us a much better mobile interface. So you can go on your phone. You can actually add it as an application on your home screen and then get to the various Zool dashboard features. Finally, and most recently, we've added support for Kubernetes build resources. This allows us to not only deliver individual containers as places to run jobs, but in fact entire Kubernetes namespaces. So if you have a job that wants to test itself against Kubernetes, you can request in your job, I need a Kubernetes. We'll hand you one, and then you can do whatever you want to with that, and then we make it go away at the end of your job. And we're very excited about the possibilities that that presents. We have a whole bunch more things lined up that will be coming that it will hopefully tell you about in Denver. And this week, we have several sessions today. Oh, gosh, I'm going to be in all of those, I think. So this is my schedule for the rest of the afternoon. So you should come check these things out, a bunch of people talking about things that we're doing. And we're super excited to tell you about that. And with that, I'd like to introduce our fantastic Zool maintainer from BMW, Tobias Inkel.