 Okay. Good morning, good afternoon everybody. I'm here to talk about how we can advance the future of CI CD together and under the umbrella of the CD Foundation. So just first up, I'm director of open source at CloudBees. I'm also on the governing board of the Continuous Delivery Foundation. I'm the co-instigator of the Great Brexit Pub Crawl. Was anyone here at that on Friday? You can find me on Twitter as Tracey Miranda. So I'm here to talk about continuous delivery, which we saw in a poll earlier. That's what many people see as the CD of CI CD. It's essentially an engineering practice where teams commit regular amounts of code but they always want to keep it in a state where it's ready to ship. So continuous delivery is something that as a concept has been around for 10 years or so, and we have a lot of research in this day and age about the best way to deliver software. So who's read the Accelerate book or come across that? Yeah, a few hands. But I highly recommend that book as the modern text for how you and your team should be delivering software in this day and age. That's accompanied by the state of DevOps reports, which come out every year, and they give information about ways you can measure your software throughput, but also really good suggestions about how you would improve that in your team. Yeah, one clue. It's more about the team environment than the individuals and their special powers. So I love that quote from Nicole Forsgren, one of the authors of the book who just talks about how the teams that are good at it just keep getting better and better. We have teams that can really struggle if they don't get the right things together. So continuous delivery has been around for a while. We have a book which maps it all out. But at the same time, we find that adoption is really, really low for this practice and we go, well, why is that? There's three big challenges that I think people are facing at the moment. The first is this huge shift in the industry which is the rise of microservices. So who's doing things with microservices today? Yeah, I'd say about half the room. So that presents some interesting challenges. You no longer have your monolith application. What does it mean when are you releasing different bits of the services that make up? What even is your application? How do you define it? Then you've got Cloud Native Technologies, things like Kubernetes, who's using Kubernetes at the moment? Yeah, a few more. That introduces a whole distributed paradigm which has different challenges to contend with. On top of that, you look at the tool landscape today, and it's pretty fragmented. You have all sorts of different CI and CD tools. They don't necessarily work together, and it's often left to you as the DevOps folks to work out how to integrate, I don't know, security scan with your bills, with your delivery mechanism. Then finally, of course, change is hard. So all human, we all have teams, we all like how we do certain things, and just having to evolve that as a group can be pretty challenging. So that was some of the motivation for why the Continuous Delivery Foundation was formed. It's less than a year old, so this is the first FOSDEM, it's really been alive at, and as an open-source foundation, it started as well around four founding projects, and I'll talk more about those in a minute. But it was pretty significant just because we were trying to bring together the whole space. So we call it Continuous Delivery Foundation, but it does cover CI, Continuous Deployment, Continuous Delivery, and DevOps, and we're looking at different ways we can tackle problems in this space. So essentially, we see ourselves as a neutral home for the next generation of Continuous Delivery Collaboration, and that's the key bit of it, like how are we going to come together to solve industry-wide problems. So one of the ways we've been thinking about what can we do as this foundation after we launched was to get a lot of the board members together, and you might recognize some of the project leads, Kosuke Kawabukuchi is in there, of Jenkins and Andy Glover of Spinnaker, and then we've also had Jess Humble, who wrote the book on Continuous Delivery, and he sat down with us to share his experience as well as think about, how can we go about solving these problems? The thing I love about this picture is that everybody's wearing shades because the future of CICD is so bright. So the outcome of that meeting was actually to come up with nine goals for the foundation, and so there's a lot there, but what I'm going to do is pick out about three or four of those and tell you where we've gotten to in our journey and how you can get involved if it's something interesting to you. For the full details of all the different goals and how we are trying to achieve them, you can check out the website at cd.foundation. So the first one is driving continuous delivery adoption, helping people in their journeys. When you come to the landscape, the first thing like the CNCF, which is the Cloud Native Compute Foundation, they have this massive landscape, it shows all the different tools and how they get qualified. We also decided a very first step is to start to try to categorize CICD tools, which turns out is really, really hard because things fit in multiple categories. But we do have a first version of the landscape, which is open source and people can make contributions. We're hoping to get all the different tools in there and to mark them in the different categories. So the main thing of what they do. So I'd invite folks to check that out. Definitely has mistakes. So you're welcome to submit pull requests, but it's a version 0.1, and we're hoping to build this up to give, just get people new into the space, start to have an idea of what the different categories are, what they mean, and what are the options in the space. We also, just in terms of spreading the word about continuous delivery, we have a set of meet-ups. So these were actually Jenkins area meet-ups. So Jenkins is one of the founding projects, and these meet-ups were contributed to the CD Foundation, and the CD Foundation is now driving those forward. Meet-up owners are invited to widen the scope. So if you want to talk about more than Jenkins, you can do that. We've got quite a few all around the world, and maybe some of you have already been there, maybe some of you run them. But either way, I encourage you to either join a local meet-up or look to start one yourself, so you can sort of work together with other people to sort of see how people are approaching things. Okay, then one of the other missions is to just focus on the projects that are part of the Foundation. So there's a lot of CI CD projects out in the world. We launched with four specific projects. So Jenkins, Spinnaker, Tecton, and Jenkins X. So these are founding projects. And the interesting thing I find about the different projects we have in this space is that they really represent different parts of adoption in the industry. So you take something like Jenkins, like, okay, who's heard of Jenkins? Yeah, I think some of you are just being lazy. So most people, I say Jenkins is pretty much late majority. If you're doing some form of CI CD, you've come across it, you've used it, and it's only ligates who perhaps aren't employing CI CD, who aren't using it. Spinnaker, probably early majority, lots of people using Spinnaker. Well, how many people in this room are using Spinnaker? Have heard of Spinnaker? Okay, maybe? Yeah, just a few people. And then over here on the right, Jenkins X and Tecton, for those of you who were in the talk earlier, we talked about Tecton, and there'll be some talks later about Jenkins X. Those are coming in much more on the kind of innovators and early adopters, folks who are just getting to grips with microservices and Kubernetes, and looking for tools that can deal with the different kind of tech paradigm. So, you know, tools in different languages, tools with different challenges. So as a foundation, we're sort of saying, okay, what does each tool need, and how can we help them grow and be useful to the end users who want to use them? And, you know, some of the things we do is just measuring, you know, how many contributions we have. That was a little infographic I did, just trying to compare how many people are contributing to the different projects, compared to, let's say, something like Kubernetes, which is really taken off. And just saying, like, you know, Jenkins for a basically a 15-year-old project is doing pretty well and quite healthy, and all the other projects are sort of growing steadily. So that's something we'll look at sort of year on year. But a key thing is we do want to just foster some tool interoperability. So how do we make sure all these tools stay working together? So we want to think about, you know, standardizing building blocks into shared APIs, building this whole ecosystem where things can be plug and play. So it's not like you have to go and figure out how they all work together for yourself. And then just generally, we see that will improve the state of delivery for the entire industry if people are not less struggling to themselves and working out what's gone wrong when they plug tools together. So we have some ideas for common APIs and establishing, let's say, common metadata. You know, how do you define a release? It should be standardized, whether it's from Spinnaker or whether it's from Jenkins X. So we're looking at ways we can do that. So very recently, we spun up a working group called the SIG Interoperability Group. And where's Fatty? There we are. So Fatty is one of our chairs who's doing an incredible job just getting people together. And I want to highlight this full request which is in progress. And it's one of the first things which is actually saying, look, there's all sorts of different tools out there. And even just with the vocabulary, you know, what do they refer to as a pipeline? What does it mean for that tool? So can we, first of all, define them and then maybe start to translate so that if you're talking about a pipeline in one tool, is that equivalent? Is the step the same thing? So before we can integrate, we need to just sort of say what is it, what are the different tools talking about? So again, this is all in GitHub. I encourage you if you have a project to go and add it to the list and to just contribute to that sort of first step in getting towards the shared vocabulary. Okay, and final bit in this kind of whirlwind tour is the goal of expanding into emerging tech areas. So machine learning is something that's emerging quite in quite a few areas. And we have a specific area. So machine learning ops is the intersection of DevOps and machine learning. So we've also got a special interest group that started up around that. I believe you've got Cara Dillamark is one of the very active members in there. And so one of the things I'd like to highlight from that group is that group is working on a very initial roadmap. So what does it mean for DevOps and machine learning? So they talk about in the roadmap if I pick out two highlights, what is ML Ops? One, it's the extension of the DevOps methodology to include machine learning. So making sure models and data and code are all first class citizens. And then things like what is it not? It's not about putting Jupyter notebooks into production environments, but helping people find better ways to do things. So highly encourage you to go check that out. And again, if that's of interest, the group is open, join the meetings, talk to Cara. And yes, it's pretty exciting. Okay, I think that's all I have time for today. So haven't even touched on some of the other things we're doing around diversity and security, both very important areas. But I hope you get the general idea that it's just people coming together, trying to drive things in the right direction for the good of the full industry and not just one specific tool or one specific vendor. And yeah, please check out our website and come try and join us. And we also have a Twitter account where you can find out what's happening with the foundation. Thank you very much. Any question? One question. Yeah, go ahead. I've seen an overlap with what the Kubernetes SIGs are doing. Are you collaborating with SIG apps on the app definition? Yes, so we do want to work, not just with CNCF, but all the different bodies. Oh, okay, so the question was, we're seeing a lot of maybe overlap with what CDF is doing and other communities like CNCF and the SIG app delivery. So my response is yes, we're looking to work with a lot of different open source communities out there. CNCF is one and actually in our interoperability SIG, which has just recently started, we did have a member of the SIG app delivery join. So we hope that we continue talking and just find ways to work together without necessarily all working on the same things in different ways.