 Good morning, everyone. Welcome. We're here. My name's Christian Hernandez. As Fatigius mentioned, I'm a senior principal product manager at Red Hat. And Scott, would you like to introduce yourself? Yeah, Scott Rigby. I am fun-employed right now. Nice. Anyway, I'm independent. And I am very involved with the Open GetOps project. And as Fatigius mentioned, several other co-maintained several of the CMCA projects. And I'm involved in a few other working groups. Awesome, awesome. So we're here to talk about the state of Open GetOps, GetOps working group. And first, we kind of want to go off of who we are and what we do, right? We think we've spread the good words of GetOps a little bit for a while now. But since this is our first time with CDCon and GetOps Con, we have more folks from outside the GetOps world. So I figured we can just quickly talk about who we are and what we do. Yeah, that's right. And I probably should have mentioned I was formerly at Weaveworks. And that's where the GetOps term initially originated from Alexis Richardson, the CEO of Weaveworks. But that was quite a while ago. And since then, there's really community around this to the point where there's shared terminology now. There's shared, we're all kind of all on board for this across the industry. So yeah, so just to give you a sense of what the differences are between or the similarities and the relationships between the working group and the Open Project is that so CNCF working groups, I won't make any assumptions about the knowledge of this audience with CNCF and all of its inner workings. But basically working groups, by and large or under technical advisory groups, very similar to the Kubernetes special interest groups. And that's where the GetOps working group is under the app delivery tag. So our focus, basically app delivery is about how things are delivered. And it pairs very well with the connection with the CD Foundation. And the GetOps working group, our main focus is about really just the principles around your desired state for your operations. And so all of our principles relate to that. And you'll kind of see how they tie together in later slides. The working groups are meant to be short-lived really until their goals are achieved. We're still on the fence about how much longer we need a working group because the Open GetOps project has really been a place that holds the long-lasting documents like the principles and the glossary. And it's a place where, I guess, information about the certification that Fatih mentioned earlier will be and conformance and really anything around the public-facing side of GetOps. So at this point, you can be involved with the working group. And ultimately, what that means is you're really helping to participate in and contribute to and run the GetOps, Open GetOps project. So there's not a lot of difference right now. But yeah, we're going to, I guess, you'll go over how. So we'll just introduce how the GetOps principles really map. How they relate to each other. Yeah, so I think I'm going to go over the next slide. Shout out to William Caban, who isn't here, but he was involved with drafting these principles and actually mapping them to common practices. And so the GetOps principles and was vendor-neutral from industry-wide. We had a lot of folks who will go over that, who contributed later. But I'll still define each one. And then you can talk about how they map. Yeah, so the first principle is a declarative. A system that is managed by GetOps must have its desired state expressed declaratively. But this is true for things like configuration as code, infrastructure as code, DevSecOps, and also GetOps. And so things that aren't necessarily new, but we are actually putting a definition around what it means with respects to GetOps. For principle two is version and immutable, meaning desired state is stored in a way that is, it enforces immutability. Versioning and retains a complete version history. Again, this is the same for infrastructure as code and DevOps and all those sorts of things. But also GetOps. You're also, GetOps also uses this principle as well. And it's pulled automatically. And I like to define pulled. So software agents automatically pull the desired state. So pulling the desired state versus web hooks and stuff like that. And just to interject real quick, the one thing that's not really on this website that is in the versioned GetOps principles is that each of these four principles relate specifically to the desired state of your operations. And we probably should just very quickly mention what that is. That's basically the declarative side of operations. So platform applications, but also anything that's required for your system to work, including policies and security policies and policies about who's supposed to access networking, pretty much anything for, ideally, everything from soup to nuts. But so what's pulled? We're talking about the declarations, the desired state is pulled. Your end state, as opposed to the imperative steps to get there. Correct. So that is kind of like the DevOps, DevSecOps, GetOps. But number four, which is my favorite, that gets you fully into GetOps is software agents continuously observe actual system state and intend to apply that desired state to the system. And so all of these we hope to build on each other. And really, only when you're doing all four, I make the joke kind of like clap them, plant it, I don't know if anyone knows what that is. But when your powers combine, you're actually doing all GetOps. And so each principle takes you closer and closer to GetOps and only when you're doing all three, you're actually doing GetOps. And so moving quickly here, so we have a few announcements. Also, things are happening. So ArgoCon happened, so folks from the Argo community also take part of Open GetOps. And ArgoEU happened, third ArgoCon to take place second time in person. So it was co-located with KubeCon EU to make it a little easier. And so that was a lot of fun that happened there. That's not the only thing GetOps related that happened in Amsterdam. So Scott, talk a little bit about the community meeting. Oh yeah, this is good to know about, even though it's like, well, why are you saying, why are you mentioning this here? But it's good to know about because this is an ongoing set of discussions that anyone, any of you who are interested in the topics around GetOps, please participate in. Basically, we use GitHub discussions as the place to sync our live meetings and all the async work that's happening by people in various times. So we're really trying to promote the usage there and make sure that, yes, we have other channels of communication, Slack and mailing lists and in-person meetings. But that's where we really try to synthesize everything so that no one's left out. And so the community meeting that was at KubeCon, we really took that list of topics and held an open, or let's say, kind of an unconference style, birds of a feather conversation, or had birds of feather conversations. And they were really great. So it would be great to have some of that with you all in a less formal way, I think, over the next two days in the hallway or in between chats, between conferences. Yeah, and something else, and Fati already mentioned it, but we're also helping co-author the Certified GetOps Associate Certification with where we're not only doing the conference with the CD Foundation here, we're also helping shape the certification of interneutral certification that the Linux Foundation is going to be putting on about GetOps. So course outline is set. We're currently writing, discussing, doing all that fun stuff. So take a look at that when that comes out. We're really, really excited about that. So sweet. Let's talk about what's next. Yeah? Yeah, so as Christian was saying, basically, the conformance and certification to be super clear about this, conformance is primarily for projects and platforms, products, and things like that. Certifications are for people. So that gets mixed up sometimes in a lot of the conversations, so I thought I'd throw that out there. And for the certification, we're really talking about the human side of this. Like you take classes or you attend conferences and then you want to get your certification. So that's what's coming, not so much the conformance side. But that is on the horizon as well. And yeah, kind of on the foot of that is the fact checking. The GetOps police is here. No, I'm just kidding. But we really want to help the larger community in the industry about the use of GetOps. I always say we don't want GetOps to turn into cloud. Cloud came out and it was just everywhere. And who knows what cloud means now? But we don't want the same thing happen to GetOps, which is part of the reason why the working group exists. And a lot of articles and blogs were written even before the working group even existed. So we try to educate and kind of make GetOps accessible to everyone so that way it's like, hey, join the community, let's get these practices out there. And so that way, us as a tech industry can be speaking the same language. Yeah, and so on that note, please reach out to us, not just Christian and I, but all the people involved in the working group and the GetOps project. That's really part of our job is to help collaborate with people and say, oh yeah, now that there are these industry standard and versioned terms that's agreed upon across many different companies and industries and so on. If you want some, I don't know, even eyes on your writings about things or even just have any questions or even have ideas about what should change in within GetOps, yeah, please let us know. Awesome, and then again, PRs are welcome. That's kind of what the last bullet is. Since we're running out of time, I'll march on here. So get involved, the more the merrier, Scott, talking about project structure and how to get involved. I'll be quick about this one. So yeah, so the entry point for, I mean there's an open GetOps.dev website, but for folks who are looking to get in through Git, it's all at GitHub like most of the CNCF projects. Or like how's there, at least says this, the main source of truth. And the organization is Open-GetOps, so just remember that for now. Someone named squad at Open-GetOps one word and it's just been sitting there for years. We don't know who it is. Yeah, you know who it is, let us know. Yeah, we could redirect it, but in any case, there's nothing there. So you'll find it and the main entry point, like repo is the project repo. So like third down on that list, it just gives you information about like, what is this project? How do you get involved? Who's running it? Like what's the governance like? It's at, what are the licenses, that kind of thing. And the documents repo is really the main contribution that's out there right now. That's where the principles are being worked on. That's where the versioned, like the one of the principles are. Any issues and discussions around updating those or tweaking them in some way, that's where that happens. Also that's where the code base for the GetOps glossary is, which the principles link out to in vice versa. So yeah, like definitely check that out. And then if people wanna actually like say, hey, I wanna start contributing and maybe you're really good at front end work or whatever, check out the website repo because we can actually use some help there. It's looking pretty good, but it's always good to get more eyes. And then just the normal like GitHub health or default community files, like how to contribute and things like that. Cool. Yeah, cool. And just kind of let you know we're growing, right? And we're growing to the point where we have subgroups now. And also I just wanna say congratulations to our new maintainer, Nikki, Nikki's here. I, yes, hey Nikki, there you go. Thank you. Menno Ledaki? Did I say it right? Well mostly. Okay, thank you. So congratulations to your maintainer. She started the environmental sustainability for GetOps subgroup. So awesome, awesome work there that she's doing here. So there's some teams here, right? In the last few seconds that we got here. Again, the environmental sustainability team, which is active marketing media slash events, right? Kind of this is kind of where I kind of hang out do most of the stuff here. How we do what we do. So if you wanna get involved like, what kind of team would I like to be on? Check these out. There's a document in the main project repo about this. And then there's some proposed teams, right? Like security, media fact checking, that sort of stuff. And the inactive team, right? Well our first team was a principles committee which basically was a committee that came up with the GetOps principles that we discussed earlier. And then just kind of wanna give a shout out to all the authors, right? That contributed to the GetOps principles. And then, oh yeah, get involved with the discussions. And best place to get involved if you have your phone out, scan the QR code. You can find us in opengetops.dev. And you can join a meeting. And yeah, we, thank you. Enjoy the conference. Thanks so much.