 All right. Thank you to all of you. Thank you to our sponsors Red Hat and AWS. So my job was to tell you how to get involved and we need your help. All these problems that we're talking about today aren't necessarily solved easily. There's some quotes that have come out of today already, right? Like, choose your tech debt. You know, choose it wisely. You're not choosing a tool. You're choosing your technical debt. And then the ubiquitous Conway's law always applies. So how do you get involved in helping us? Well, first, thank you to all the volunteers that made this possible today. That's a lot of people. Christian, Aubrey from Red Hat, Scott from WeaveWorks, a bunch of people there, a few people from AWS. Yeah, it's a lot of volunteers. It's a lot of speakers too when you put them all on one page. So thank you to all the speakers. This would not have been as awesome of a day without them. So how do we get involved? Showing up is actually 80% of the work, Scott. I've heard that. I've heard that, yes. So what is in front of you? Well, it's the CNCF that IO slash calendar. And if you search for GitOps, you will find our working group meetings, which you can then add to your calendar. It's awesome. What do we talk about in those meetings, Scott? Well, we talk about... We have an agenda. I mean, one thing we do is we... I don't want to jump the gun. You're fine. Go ahead. There's nothing. Okay. But there are different groups of people working on different work products that are part of the GitOps working group and for the Open GitOps project. And one of the things that we do at that meeting is those people report back, I guess you could say, or try to just integrate so that everybody has an idea of what's going on. For example, there are people working on white papers on certain topics, or research papers or things like that on certain topics. There are folks working on events, such as this event today and the other one in North America that happens every... Speaking of North America, it's in Detroit where I'm from. I'm very happy to welcome all of y'all to my city. It is truly different than what you've heard in the news. It really is. I promise you that. I would not live there if it wasn't cool. And we talk about topics. So in between folks start... But there are some people who can't make these meetings, and I think you're probably going to show some more of that. But just when we are in these meetings, the folks that can't make it, we also integrate with those people. So folks that can't make it in person, not just us, but various people within the GitOps working group connect with on Slack, help people get their agenda items onto our meetings doc, like most project meetings, or most working group meetings have a meetings doc. And that's what you could do. So if you can't join these meetings, Chris will show you some other ways to get involved. But in the meetings, you will also be represented. Yeah. Again, this is our repo, essentially. The documents are the kind of the outputs of our work. And the project repo is where we have our discussions that you saw earlier this morning, all those links. Those discussions are still all open, right? Like secrets management is still a big deal. And we still need to figure that out on like a multi cluster, multi tenancy level. Scaling secrets by itself is hard. So that's worth it. Worthy of a discussion, worthy of building some recommendations around the discussion, and then worthy of creating a blueprint or white paper or did we say green paper at one point? I think we just started using standard terms because people started getting confused. It sounded cool, though. I still like it. Yeah. And there's lots of already open PRs, too. Yeah. So there's plenty of places for you to just dive into open dash getups on GitHub and start getting involved. If you have a question, just a general question, go to that discussions page and ask it. There's a special thing just for questions. If you have an issue, like with terms missing from the glossary, for example, feel free to open an issue and create a PR and it'll get added, trust me. And then Slack, I created a shorter link because that URL no one's going to remember. Please join us on Slack. That's a great way to get your stuff into our meetings, into our field of view. Screenshot didn't turn out, oh, well. Okay. So there's some. No, it's Slack. Yeah. It's Slack. Get involved here. If you need a nudge, getting started, or just want to say hello, it's fine. All right. Like if you want to just keep an eye on things and lurk for a little bit, that's fine, too. Oh, one thing I should probably say, though, while you're on the Slack topic, is that you may notice if you're in CNCF and you type in getups, you'll see a couple of channels that say getups and them. Yes. Yeah. So we, I realize now, Dan and Chris, that we didn't actually mention this when we first started today, whereas we did last getups con because it was big news. It doesn't feel like big news anymore, but it is still worth noting that open getups is a sandbox project. I know at some point it was noted, you know, that's where documents live. But basically, that is a CNCF sandbox project. It is not the same as the getups working group. Just like most projects aren't the same as working groups. Working groups are meant to be short term. They last as long as they last. They're either underneath technical advisory groups, which the getup working group is. It's underneath the app delivery tag. And other working groups are just directly under CNCF. Excuse me. So in any case, where was I going with that? Oh, yeah. So the getups working group, it doesn't seem to be going need to go away right this moment or anything like that. I mean, it will last as long as it's needed. But once the open getups project is really running solidly on its own and it doesn't feel like it needs a separate group, that group may not be necessary anymore because you'll actually be able to group together with folks in the open getups project. That's already getting started. So the GitHub teams that I mentioned that where people are joining to do certain types of tasks together explore certain ideas together. You know, I mentioned earlier during the opening the the getups impact on environmental sustainability. Hey, if that's one of the topics that interests you, awesome, please connect with us and other folks who are a part of that group. And if you have an ability to commit to that, then we can add you to that team. Another cool thing about being added to a GitHub team is that you can choose to show that badge on your GitHub profile. So you can do that too. And we try to also make it clear that volunteers can have. You're not just being asked to do silent work. You're always thanked. Yes. Yes. So in terms of Slack, I got a little off the topic there, but in terms of Slack, we have both channels and you can use both, but we've been migrating as much as possible to open getups. If there are things that are specific just to the working group that aren't really relevant to the getups, we might still do it on the working group, but hopefully that helps you there. There. Awesome. Cool. Thank you for that, Scott. All right. And spread the word, right? Like, tell your friends, like, do, tell your friends how to do Dev and Ops through a pull request, right? Like, that's the start of it, that start of that conversation internally. Tell us what you're up to, right? Like, we want to know the companies and the people that are using getups. So it, you know, obviously, there's a lot of people doing getups. It'd be great to know who they are so we could learn from them and hopefully learn from their mistakes so that we can pass those on, you know, through guidance or documentation. Right. That's a good point. And if you need to be anonymous with your employer about some getups horrors that you've had, that can be respected, you know? We don't think we have an NDA process, but you can also just tell us without telling us who you are, you know? Right. Yeah. Also, there is an adopter, to what Chris said, there's now an adopters page within the Open Getups project repo, I think. Anyway, it's one of the repos. There is a page where you can list yourself as an adopter of getups and there's a template showing you how to do it. So please do that. Give like a one sentence, hey, this is how I'm using getups. And even like, oh, here's a link to our blog post showing you more in depth on how we're using getups or even how we're in the middle of using getups or whatever you want to say. There's no real bar there except for follow, except for you are actually implementing getups or trying to. You're trying. Yeah. Yeah. And you're following the code of conduct, but otherwise, no one is excluded. Right. And then, you know, I made this short and sweet. Like, thank you all for coming. Thank you, Scott. Thank you, Dan. Thank you, Christian, wherever you are. I don't know where you went, but really happy to have you all here today. Hope you had a great day. I hope you have a greater KubeCon. And we look forward to seeing you in Detroit. Yes. Thanks. Thank you, everyone.