 Hi, everyone. Thanks for joining us for GitHub's Con Europe today. Pinky, Ravi, and I will be giving you an update on the GitHub's working group, as Scott mentioned. But first, let's introduce ourselves. Pinky? Hey, I'm Priyanka Ravi. I also go by Pinky. And I am a developer experience engineer at WeWorks. And I'm also a member of the GitHub's working group and a member of the Flux project. Nice. Hi, friends. I'm Stacey. I'm a program manager, open source community at Dynatrace, primarily working on CNCF projects, Captain and Open Feature. Formerly, I was at WeWorks with Pinky and crew and had the pleasure of working with the Flux team over there. I'm also a member of the GitHub's working group, marketing events, and media teams, which we'll cover in a bit on the later presentation. So I've been contributing, a contributing member of the Open GitHub's project and the GitHub's working group since kind of the early days. So now that we've introduced ourselves, let's introduce the GitHub's working group and the Open GitHub's project a little bit. So the GitHub's working group lives within the Cloud Native Computing Foundation's technical advisory group for application delivery, also known as the CNC and CNCF tag app delivery. For those who may be unfamiliar with the working groups and tags, the tags work within the CNCF and we'll dive into that a little bit right now. So CNCF tags oversee and coordinate interests of specific areas for end users and or projects. So with tag app delivery, focusing on projects and initiatives related to delivering Cloud Native applications, including building, packaging, deploying, managing, and operating them. So our focus within the GitHub's working group is to clearly define a vendor-neutral, principle-led meaning of GitOps. And I will let Pinky kind of dive into the Open GitHub's project a little bit on the next slide, but it is also kind of guided by the working group. Yeah, so Open GitOps is a CNCF sandbox project to define a vendor-neutral, principle-led meaning of GitOps. So this will establish a foundation for interoperability between tools, conformance, and certification through lasting programs, documents, and code. OpenGitOps.dev is the website to find out more about the Open GitOps project and also get involved in the GitOps working group as well. So I want to go over the GitOps principles really quick. Nicholas actually did a GitOps 101 talk just a few minutes ago and he dives into great detail on each of these as well as how they map to modern practices, but I'm going to review them just in case you missed that talk, but definitely go back and watch it if you can. It was really great and detailed. So the first principle is that a system managed by GitOps must have its desired state expressed declaratively. So everything is written in code. It's more reusable this way. There's an audit journal, things like that. The second principle, and just to quickly mention, that principle maps to things such as configuration as code, infrastructure as code, DevOps, and DevSecOps practices as well as GitOps. And then the second principle is that a desired state is stored in a way that enforces immutability, versioning, and retains a complete version history. So there's no sneaking in that change at all. And this relates more to infrastructure as code, DevOps, and DevSecOps as well as GitOps. So we've dropped off, configuration is coded there. And then the third one is that software agents automatically pull the desired state declarations from the source. And this is more DevOps and DevSecOps and GitOps as well. And then the one that's more purely GitOps and stands out for GitOps is that software agents continuously observe actual system state and attempt to apply the desired state. And these principles are a set of best practices that have been defined through discussions with many different vendors and user experiences by the GitOps working group. And as I mentioned earlier, you can go to OpenGitOps.dev to learn more about that and also check out more about the principles there as well. And don't feel like you have to have all of them done in order to get started using GitOps. Everyone's journey with GitOps looks different and you can always get started with it and then add in hardening and tweak your setup to meet these guidelines as you go. So Pinky, I did wanna just interject here quickly because I noticed in Nicholas's talk on the last session before the break, somebody had asked, what is the difference really between three and four? I don't really understand the big difference between three and four. So would you mind just kind of diving into differences between those a little bit more? Yeah, so three and four, I always usually lump them together when I talk, but they're actually different in the sense that three is saying that changes are pulled instead of pushed, but also four is then going a step further from just pulling the changes in to continuously checking, hey, has anything for some reason gotten out of sync? And we use the term drip detection in that regard and say that if things for some reason have been accidentally changed, this operator will actually make the changes back to what's declaratively stated in the repository, for example. And so that's the difference, yeah. Thanks for bringing that up. Thanks, yeah. All right, so now we'd like to talk about some exciting announcements we have. The first one being that the certified getups associate certification goes beta in Q1 of next year, very excited about this. The invitation list is full, but you can add your name to the wait list by going, clicking on the link on this slide that's stated here. And we really want to give a huge thanks to everyone who's making the certified getups associate program happen. They've been working tirelessly since August and we really appreciate all the hard work. If we did forget to put your name on this slide, we're very sorry, but we're really, really grateful to anyone that's helped out with this process. Yeah, thank you all so much. This is so exciting. And for events, we have some news from ArgoCon which was co-located at CubeCon in Chicago back in November. So this was a full day, three tracks and peak attendance was around 601 with an average of about 475 people in attendance during any session. The top three sessions that are listed here, you can go and check those out. And then I've also included a link on this slide for the entire playlist for you. So you can go back and watch all of these sessions from their original recordings. ArgoCon in North America is going to be, I'm sorry, ArgoCon, CubeCon EU will be at CubeCon EU in Paris in 2024. So if you haven't already registered for that, you can go and check that out at the link as well. And stay tuned for our getupscon North America announcement, hopefully we'll be able to release all the details of that very soon, but we're just trying to pin down those final details for you. So how can you get involved with the open getups and getups working group? So you can find the open getups project on github at github.com slash open dash getups. But the main entry point for anyone new is the project repo. But please have a look at docs where you'll find the principles and glossary events if you want to attend our community project meetings and the website, even though this is looking pretty good, we can always use some extra help. If any of those things interest you, please go to open getups project in github and check those out. Yeah, so the project is run by its members and we're growing. Folks are organizing topic teams, subgroups within the getups working group, such as the getups environmental sustainability team, the marketing media and events team. And there are a few proposed teams for things like security and media fact-checking and there are also positive archive teams as well. So if you're interested in any of these, please get involved in any of them. You can also find discussions in the open getups project repo as well. So if you're looking for answers to questions, you can check there first. And otherwise, here are a bunch of links where you can find us. If you would like to scan the QR code, this will actually take you to the open getups website and to the get involved page that we have dedicated to this. But you can star and watch the open getups documents. That's a really easy entry point if you wanna get involved. The tag app delivery and getups working group, links are in here as well on GitHub so you can check those out. And join us for a meeting on the first and third Wednesday at 1900 GMT. I think Eastern time, it's around two or three in the afternoon, I can't remember exactly. I always get my time zones messed up. And yeah, join on the discussions, open an issue, join the CNCF tag app delivery mailing list which we where we live under and you'll get updates regarding the working group and the open getups project there as well. And if you have something that you're passionate about in and around getups, feel free to come and share with us. Yeah, so for more ways to get involved, again, open getups.dev slash get-involved or scan this QR code. Yeah, and we really, really love people joining the meetings. And so you can really come and just chat with us about whatever there's always time in there for people to come and share their ideas or just show us cool things and whatever you wanna do, yeah. Yeah, for sure, thanks so much. And yeah, I think that's kind of it for the update for the working group and the open get-ups project. So at this time, I'd like to invite Scott back on, see if we have any questions or if there's anything that he has for us that we maybe missed in our presentation. Maybe he wants to chat a little bit. Hey, Scott. Yeah, hi, thank you for that. Thank you, and Stacey, I love that. Yeah, so I think that there's a couple of things that we could cover, but one thing I just wanted to note is that I added a little extra flourish to that question about the difference between three and four in the platform. And for anyone watching this who's not looking at the platform right now, the main thing I like to tell people, I mean, like what Pinky said was absolutely 100% correct. But I also just like to tell people, like some of the reasons why too. There's a bunch of reasons, but one of the main ones from my point of view is that like how you get from principle three to four when Pinky was mentioning how in principle four, you're checking the difference between your desired state and the actual state. Well, that has to, three has to be able to happen. Your system has to be able to access your declarative desired state at any time. That's why we actually say poll specifically because it needs to be able to know what your current plan is for your running system in order for number four to continue to try to see what the difference is and reconcile those two by updating your running system. So if for an event-based system, a push-based system only, your system would only have your changes after you, after you make a commit or something like that. And those also can fail. So yeah, there are really clear reasons why we say that and I hope that that helps to make sense. Yeah, that's great. Thanks, Scott. Yeah. So I guess is there anything maybe that you could shed some light on, Scott, about kind of the future of the Get Ops working group and maybe the Open Get Ops project, kind of what you, what might be something that we can look forward to or anything like that for the future? Absolutely, absolutely. Well, so I know you've already covered the structure of the group, the teams and that there are discussions that are going on. In GitHub discussions. I'm tempted to share my screen, but I guess I don't really. You know what? I'll go ahead and try it. Okay. There we go. Can you all see my screen? Yeah. Oh, yeah, yeah. Okay, awesome. If there's an issue too, I didn't really give the people a heads up. So hopefully this works. If not, it's my bad. But let's see. Let me know if anyone else can't see this, but excuse me, sorry. Wow. I think they can see it, Scott. My gosh. Okay, so the most important thing is within the project repo under Open Dash Get Ops in GitHub, you've got a folder called Teams. There's a lot of other information here about the Get Ops principles and so on and how to get all the, you know, everything else you need, but Teams specifically, there's a file that explains what it's about and why, you know, why we have teams in the first place. And mainly the answer is that we have different work projects. For example, there was a team of people who put together the principles. There's a team of people who work on the events, such as the one that you're all at today. There are teams of people who are monitoring or at least trying to monitor different media that's going out, that's describing what Get Ops is about. Some of them are from before there were official Get Ops principles, the official meaning by the CNCF. And some, you know, may be unaware of that fact and might not be totally accurate. So here's a list of the teams. There's some information about basically what the process is for joining a team and recommending or suggesting new teams, but and in short, make a GitHub issue or just talk with us at any point it will help you. And so the current teams are what I had mentioned before, the media team, et cetera. The proposed team that I'm talking about is actually we've got to move that to an active team. So that's actually becoming active again, finally. That's the media fact-checking team. It's under the marketing team and it's mainly like what I was just saying is just trying to be friendly and helpful to everyone in the wider community about really the principle-led definition of Get Ops and all of the things that Stacy and Hanky just covered. So I'm mentioning this now because a bunch of folks have asked how they can get involved and not just like, the answers are, we've already covered them, but like in detail, really it's all about collaboration. And there is a group of folks who, excuse me, as you can see who are working on the environmental sustainability teams, really what that's about is Get Ops impact, known impacts and potential impacts on ecological sustainability. For better and hopefully not for worse, I think it depends on how you configure it and how you set yourself up. But there's a whole lot of people there and some of this is working on a white paper and it's a tie across between our working group under the app delivery tag and the environmental sustainability tag for technical advisory group. So anyway, this just helps give you a sense of what you can do and the discussions really need to be picked back up upon, but they have a number of topics where you can really, for example, there's a topic about the Certified Get Ops Associate exam that the Linux Foundation is putting out. There's a topic about Get Ops that scale patterns, et cetera. So there's a lot of things that are important and valuable here and just check it out. I'll just give you one example to look at is the fact-checking team I just mentioned, there's a help one to tag. This just really goes through what the motivation behind it is, mostly what I just said, and specifically propose dance, like not to somehow say that we're telling people they're wrong and I mean, they need to fix it, but more just that we're trying to participate with folks. And there's a lot of chat here, feel free to join these. There is another issue that I think is relevant to today that I'm just gonna point out. I want to, oh, excuse me. Yeah, there was a Get Ops machine learning subgroup and AI ML subgroup in October last year. This was being discussed for a lot longer, but it also happened before this like more recent explosion of interest in AI that seems to be capturing public imagination. A lot of people said they were interested, but no one showed up for the meeting. So this is not like pointing any fingers, this is just saying that it's in order for these groups to work, there has to be some regular participation. And a lot of the other teams do have that. This one just did not, so it was closed down and that's why it's listed in this inactive team. And that's to say it, not saying that it couldn't resurface again, right, Scott? So this is a topic that interests you and you want to get involved, come back, reach out, open the discussion, contribute to this discussion and we can definitely pick that back up again. Exactly, and I miss both the positive team. Sorry, thank you. I was just gonna say, William's really interested in this one. So he would definitely help, like if someone was interested in working it with them, I'm sure he would. Yeah, I'll paste it into the chat, the issue, and I'll also do that in the open get ops channel. But yeah, let's take a look and see, does anyone have any questions? Okay, I see nothing in Q and A, that's cool. So we can just continue to chat. Oh, there is one other thing I'm gonna highlight about the teams. So if anyone here is interested in helping, but doesn't feel like they necessarily have, oh, I don't know, skills yet to be an expert in any topic, that's completely okay. This whole thing is about meeting people where they're at, meeting organizations where they're at as well. That's part of the idea of get ops is that it's not, there is a maturity model being put together, but it really, and some companies have done that, for example, WeepWorks has a maturity model for get ops. And I think some of the other companies have also made their own, but while there might not be an official one, the stance is shared between everyone, that it's all about, it's not about demerits for not being somewhere, it's about where are you now? What does your business need and how can we help you continue to move through the different actions that are based on these principles? So with that in mind, if anyone here loves marketing or is good at doing social stuff like posting on Twitter or helping to, with any design things, like we have essentially it's all volunteer. So we have a team to do that, that was also listed on that page. And we would love your participation. Yeah, and actually on that, we got a question saying how much knowledge or what level of expertise do you need to contribute? I think you basically just covered that. Where you welcome anyone of any kind, like any level of expertise you have, there's things you can contribute from like documentation, things like that. But I'm happy to add to that too. Like Scott said, I'm not a get-up practitioner per se for myself, but I've been in marketing in the past, I'm a community manager, so I help out with those kinds of things. If that's your shtick, then come and join us in that way as well. You don't have to be an expert on the principles, you don't have to be, if you're good at, like Scott said, if you're good at Twitter, socials, being in the community, getting the word out, anything like that. We're again, we're all here out of the love of the space and being a collaborative team. So awesome, thanks, Scott. If you're like a little shy, just join maybe join our meetings, you can like lurk for a bit. Like that's how I got started. And I kind of just joined the meetings, it was really quiet. Yeah, be a fly on the wall for sure. That's totally fine. You don't have to speak at meetings, you don't have to contribute in the beginning, but if you wanna just show up and kind of be there and see how things go, that's fine too. We have fun in our meetings as well, so it's nice. Yeah. So I also wanted to mention that basically, I could go on and on about this and I sort of just been picking just a few topics, but there are some interesting topics that I think are kind of like, if anyone is in the audience just kind of like, ultimately waiting to just pull up popcorn and wait until like any kind of drama happens. You can help with that too. We're writing some posts about comparing different tools. Several of us have done that in the past. I know Christian and I both collaborated on some content for an article that was published about comparing flux and argon at that time. We've done other versions of that. Right now, there's a number of us working on a comparison between Flagger and Argo Rollouts. And that's specifically something that Boyant has been participating in and helping with because people asked about LinkerD, for example, what shines for Professor Delivery. So we're working on that now. There are many topics like that that really all you have to do is ask. Mostly we try to put them in the discussion list on GitHub discussions on the GitHub, excuse me, on OpenGitOps project, but sometimes that might lag a little bit behind. But yeah, that's where you can come in just to bring your own comments. And also you can start topics too. You can also just do emoji ops and just come in and give your smiley faces or your thumbs down or literally whatever you wanna do, your rocket emojis and to show your support that way if you feel too shy to leave comments or you just want to troll. Yeah, and I think we are going to have breakout sessions in about in just a little over a minute. So I just wanted to thank you, Pinky, and thank you, Stacey, for this keynote. It's really helpful. Absolutely. Thanks for having us. Yeah. Have a great rest of the conference, everybody. Thank you so much. And a reminder to anyone who might have joined late, click the breakouts horizontal tab on the left in your portal that'll get you to the list of breakouts where you can pick and you can go between them if you want to, basically like as if you were in a live conference just walking from one room to another and we'll see you there. Bye. Thanks.