 Hi, everyone. So yeah, my name's Dave Nielsen. I'm the head of community at Harness. And you may have heard about Harness. We just launched GetOps as a service, based on Argo CD, of course. But I'm not here to talk about that. I'm here to talk about getting more open source Argo CD users. And in the drone community, which is I don't know if you've heard of drone CI, but in the drone community, we have lots of users out there who are actually using drone with Argo. And so in talking to them, I found out that they're experimenting, they're trying, probably just like a lot of you when you first got started. And not everyone has access to the resources to put together a complete stack. You may have part of the stack, but it's not very easy to try things out if you can't get the code and put it into deployment. So we noticed that people had put together some kind of stack, and we took a look at what they were doing. And we thought, well, what if we could just put this all together for folks so they could just try it out? So what we did is we took, oh, we thought, what if we put this all together and you could run it on your laptop? Because if you can run it on your laptop, then you eliminate things like having to have credentials and connect to all these different systems. So it makes it much, much easier for things like labs and workshops where people need to learn. So that's what we did. So we put together something called the drag stack. And of course, it's Argo CD. And then it's drone CI. And then we use GitE, but the intention is for you to be able to use this with any Git repo and also any Container Registry. And in our case right now, we're using Docker Registry, but we're talking about using Harbor instead or in addition. And then, of course, you might want to play around with other things. So why not add something like litmus chaos? So you can have chaos engineering. So yeah, this is the drone and then the R's for any registry and then Argo and then the G's for any Git. And we put this all together and we're running a workshop on it tomorrow. So what are the benefits that you get from something like this, though? So first of all, this stack is very simple. All of the apps are written in Go. So if you want to get involved in the project and you don't have to worry about all of these different languages and things to have to mess with, so it makes a nice stack. It's also, we put together one installation process. Jam and Kamesh were here somewhere and they worked for the past couple of months putting this all together. And we've enabled multiple deployment targets because right now, at least what I'm seeing, there's a lot of folks who are very interested in the developer experience, not just overall but even on the laptop. So how can we make the developer more productive and have an enjoyable experience on the laptop? And if you do all this, it makes it much easier. So first time users can get it to run their laptop right away. Also, there's some other nice things. For example, all of these projects, they all are declarative. They all store their configuration details in the Git repo, which is why I call this full stack GitOps. It's the whole thing. And it's extensible. I mean, anything in software is extensible. But we're purposely building it so you can add other parts of the stack, like, for example, chaos engineering. So maybe instead of CI, CD, it's CI, CD, CE, or something like that. I don't know. Anyway, so before I go to the call to action here, let me back up for a second. And I just want to talk about drone just for a brief moment because I'll bet you not that many of you have heard about it, actually. So how many of you have heard of drone, John CI? OK, about half. That's pretty good. For the rest of you, there's a couple things you might not know. So first of all, it has more GitHub stars than pretty much all of the other open source CI projects combined, including Jenkins. Now, why don't we know that? Maybe it's because drone is not part of the CNCF, right? So we don't pay attention to it. Also, drone was started back by a guy named Brad who was a, he saw Docker come about and he thought, you know what, continuous integration tests, those should be happening in containers. Instead of having to upgrade all of my tests at the same time because they're all using the same programming language platform, let's put them in containers and then you can use whatever version you want. In fact, you can use whatever language you want. And then you just put a YAML file together that strings the containers together. So here's the first one to do that. And it took off in the Docker community. And that's why it's so popular. It's really primarily because of that. Also, it's one developer working on this thing. It's very tight and very clean. Of course, he had other help from other folks, but he was really focused on solving people's problems, not in marketing. So he focused on issues, pull requests, answering questions in forums, and really working on the code. It's very tight. In fact, one of our folks has this drone running in a Lambda function. So you can actually call it, spin up a Lambda function, which then spins up other containers to build the containers that it needs. So it's pretty tight. It's worth looking at. So I want you to go check out drone.io. I think that's the domain. You should check it out. Anyway, OK. So what's the call to action? For this project, we have a workshop tomorrow. The online version of it is the virtual version is sold out. But I think we may have a couple more spots in person. It's in Mountain View at 1 o'clock. Or we've got the domain named dragstack.org. Right now, it just points to the Git repo. But we'll start adding wherever we put future workshops, mostly online. But we'll do some in person. We've got our harness community where you can go. And we have a Slack channel in there. Or I'm sorry, a discourse community and a Slack channel as well, and on Twitter. And you can also reach out to me. My name is Dave Nielsen. And with me somewhere in here are Jim Sheldon and Kamesh, who are here. So you can come talk to us. And also, I have cards here. We have a happy hour tomorrow after our workshop if you want to join us then. Thank you very much.