 Okay, thanks y'all. All right, here we go. So bridging the gap, CDF and GitOps communities in collaboration. Pinky, you are the best. Thank you so much. Okay, so who am I? Here I am. I'm Laura LaRusso. As Pinky said, I'm the Outreach Marketing Committee Chair of the CDF and I'm a CNCF ambassador. Feel free to link with me on LinkedIn. That's a little QR code. Take it right there. Also Twitter, X, whatever you wanna call it. I haven't left yet. That's my handle. And this is a picture of me and my daughter from the summer. She really likes Snapchat. We just use the filters because the rest of that is too much. So story time. How did I end up here? So last year at this time, if you told me that I would be a keynote for GitOpsCon EU virtual, I would have said, what? Excuse me, are you losing your mind? Because right around this time last year, we started planning for CDCon and I was the program chair of CDCon and that's when I met Pinky, which was great. And we were just kind of talking and they said, oh, we're pairing CDCon with GitOpsCon and I didn't know what that meant. So I asked the former executive director of the CDF FATI, I said, what does this mean? I'm sorry, I'm lost. And he was very frank and said, many people are in consideration of GitOps. They see it as the evolution of CI CD and it helps incorporate the best practices of this. And so many end users are either evaluating or moving to GitOps. So it's a perfect marriage between CDCon, which is focused on continuous delivery and GitOpsCon. And I said, oh, so we're just like a little piece of the overall puzzle and he said, yes. And so I hope y'all agree with that sort of statement. And so in that, we got to work with the GitOpsCon committee which was Christian and Scott and Dan and they did a great job and it was so much fun working with them. So when Christian asked me if I would talk with y'all today, I jumped at the opportunity because it's always fun to play. And so why are we here today? Why are we at GitOpsCon Europe? Why are we watching somebody flail as they start their presentation because they can't find a Zoom button? Well, I think it's very simple. What makes GitOpsCon the place to be is community. This is why we're here. This is why we wanna be together. And so what is community? It is a feeling of fellowship with others as a result of sharing common attitudes, interests and goals. And I just wanna make sure you guys can all see my right screen, right? I just had a momentary freak out. Okay, so back to community. So what is open community? So it takes it a step further, right? Cause we all are working in open source. So an open community, it ensures that the community is cohesive, inclusive. There's a level playing ground. We balance the three forces of developers, users and ecosystems and I have to tell you this idea of building common goals, strong connections coming up with one path forward is something that when I saw it in action for the first time at my first open source developer meeting where they were building out a project, I thought I was gonna lose my mind. Like, first of all, seeing magic happen is amazing. I think developers make magic, but seeing you all come to a consensus, having everybody at a table be super passionate about what they're talking about and have different viewpoints and different opinions and going through the motions of getting everyone at the table heard and listened to. And then as a consensus deciding how to move forward, I mean, think about it. That doesn't even happen in my house and I just have an eight year old, right? There is no sense of consensus. So I think the idea of community, of open community is amazing and you all practice it every day. So I'm gonna take us on a little journey, right? And so we are now a company because this is why we're here today. We're talking about GitOps and CDF. So we are Trendy Corporation. I hope you like my very generic logo that I found online. What are we? We are a small company. We're starting to scale up in 2024, but we wanna make sure that we're thinking about all the things we need to think about so we can do this appropriately and in the right way. We work in Git, we are all about distributed teams. So no RTO issues, you know what I mean? And our desired outcome is to work smarter, but not harder. So this is our problem. So how can the community help us modernize our developer workflow? How can the community help us move forward? Well, we gotta do some investigation, right? We gotta find a proven framework. And where does that, how do we do this? How do we evaluate what we're looking at? Well, easy. We see like what other companies, we find a framework, we find what other companies are using this framework, who's developing and maintaining this methodology, like who's saying that this is a best practice? And does it allow for us to keep using our current developer toolset? Or are we gonna have to completely scrap everything that we're doing and move forward? Well, I think as you would all agree, the choice is simple and that's GitOps, right? Because we wanna go by their four principles. The declarative, the versioned and immutable that pulled automatically, continuously reconciled. You know, it's a framework using the best practices of DevOps and taking it to a Git infrastructure. So it's the best of everything. You've got your version control, you've got your compliance built in, your CI CD built in, and it's all about automation. So we're like, yes, this is what we need to do. And who maintains GitOps? Now, this is what's great, right? It's a project of the cloud native computing foundation. So you've got the GitOps working group and then you've got open GitOps. So basically, again, you have all these brilliant minds working together to make sure that they're constantly refining and reviewing the principles, the architecture and making sure that end users have a good path forward. That's proven and tested. But now we have another problem. How can the community help us optimize continuous delivery component of our GitOps workflow? Because we realize things are getting stuck. So what do we do? We find a proven framework. How are we gonna do this? Who can help us? And so if Kelsey Hittiteower says that, and this is back in 2018, that GitOps is version CI CD on top of declarative infrastructure, stop scripting and start shipping. So we need to work with people that are all about the shipping. So who's gonna help us do that? Continuous delivery foundation. So the continuous delivery foundation was actually born out of the CNCF. The group of founders realized that continuous delivery was such a strong subset of problems that it deserved its own sort of home. And then they created the CDF to live for it. So here are some of the projects. There are eight projects at the CDF. There's Jenkins, Spinnaker, screwdriver, Ortelius, Jenkins X, Tecton, Shipwright and CD events. So all of these events have to do with continuous delivery in some way, shape or form. And as these projects are evolving, they're adding in security and other layers, integrations with other projects truly help build out a robust tool set for users. So what can we use to help us? Well, there's a project called CD events. And CD events makes it simple to connect workflows from one different systems. It increases the pace at which you can migrate and fully automate your continuous delivery process for your organization. And as you see here, they already work with Argo, Flux and Harbor. So these are projects we're currently using and they're gonna help us have a standardized event so that anytime something happens, we have an easy way to observe the event happening, have a common language, and we can be able to quickly remediate any issue. So if an event happens over here in our pipeline, we realize now that it's triggering something over there that we didn't see, that's the magic of CD events. So we don't have to change our tooling, we're just adding on a call that gives us the information that we need that we didn't otherwise see. And shows how everything is related and interoperability is the way to the future and it's gonna make us all work faster. Again, when we're doing our research, so we found out what CD events is, but now here's another paper and it's called Using GitOps and GitHub Events, CD Events and DevSecOps Release Orchestration Pipeline. So Manuel Schuler just did this talk at DevSecCon and he's putting it into practice. He's giving us all this information and all this research that he did. He's showing us a demo, he's showing us his frameworks. Now we can start getting really confident that, okay, we can do GitOps and add in CD events and we're gonna be better shaped in for the future. And lastly, here's the new article that just came out, I think yesterday, CD events and action leveraged into the spec for pipeline notifications for approvals. So now I'm telling you that not only do you not have to change your pipeline, you just have to add on this call to figure out what's going on, how things are working, interoperability and now I'm gonna get notifications where I work, which is in Slack. So when you have all of these things combined, you do the research, you see others, what others have done, you see that the projects that you're currently using are already integrated with this. There's like no other answer, like this is where I need to be. And thank you to the community for figuring out there was a problem and solving it so that I can then move forward. So collaboration is key. That's the one thing that we need to think about is we need to work together and that means we're gonna work smarter. So open GitOps, GitOps working group underneath the CNCF and the CD Foundation with projects like CD events or Jenkins, you know, all of these things can work together to create a nice harmony and have us work smarter and not harder. So what does cross collaboration projects bring? Well, first, you know, I think it encourages more diversity of thought, right? Cause each community can view the same problem space to a different lens, right? So where, you know, CDF, there was Jenkins as a pipeline or then CNCF took it a step further and created Argo because they wanted to focus on cloud native infrastructure. So you have different communities working on the same problem in different ways and you can take from each of those what's gonna best suit you. What else can it do? You can get more robust solutions that represent your organization and organizations at scale. You know, because when you look at the list of members of these projects, right? You've got your Fidelity's, you've got your Apple's, you've got your Dell's, your IBM's, you've got all of these huge end user companies that are working like Netflix to solve a problem. And in that, you're gonna see how they did it at their scale and be able to pair it down to where you're at. And lastly, you know, open and open lines of communication like really helps you get things done faster. So even though somebody is working in the Argo project when they decided to adopt CD events, perhaps they started sitting in on the CD events working group meetings. You know, maybe they're a part of an interoperability sig and then they realized, okay, CD events is addressing that. So I want to be a part of that as well. So the more you can have cross flow communication between different communities, the better the overall ecosphere is gonna be because no one is going to be operating out of a silo. People are going to be able to have this free flow of communication and knowledge. And again, when we talk about open source, everybody gets a seat at the table. Everybody gets to get their voice heard. So CD events was actually born out of the interoperability sig and they decided that they could move things forward and create an actual POC and that's awesome. So when you open and maintain lines of communication cross projects, cross foundations, what you're really just gonna get is better solutions and work done faster. You're going to be able to lean on each other in different ways, different avenues. And I also think it sparks innovation, right? Because you're hearing what other people are doing and how they're doing it. And maybe you think, ah, I could do it like that or I could do it a little bit different and get a better result. So that's super cool. So diversity of thought. So I just took these like amazing screenshots of the working group for getups as well as the CD events group. Now these are in different Slack channels because we can't have enough Slack channels. The cloud native computing foundation has the getups working group and the CDF has the CD events working group. But as you can see, the getups working group has 983 members and the CD events working group has 197 members. I would love to do a download to see like if there's any cross pollination because I'm sure there is. But this is what I mean when I say diversity of thought. So you have over a thousand people here working on similar problems and addressing it in their own way. So this is huge, right? And again, when we follow those open source principles everybody gets a seat at the table, everybody gets to get their voice heard. You can just watch, you can see, you can download documentation and then maybe you wanna do an issues request or maybe you wanna like start mentioning things in Slack and maybe you have this and maybe you have that. But the whole point is you're with a thousand people that are in a similar place than you and they wanna help you because everybody wants to get to the end and to the better solution. Now, robust solutions. Now I just did a random Google search and came up with this little scenario. So it's an end-to-end getups automation with Argo CD Jenkins on Kubernetes, right? So look, we're at a cross-pollinating where we thought we were or not. So Jenkins, of course, the CDF project, Argo, CNCF project, everything working to create better tooling and better workflows in the getups pipeline. So why are we working together? Because you get the best out of each community, right? So they're hyper focused on solving the specific problem and you get to see what their solutions are and you get to do the research and determine like, okay, is this solution right for me? Here are their workflows, here are their examples. Everything's out in the open, it's amazing. So again, you can take two different foundations, two different projects and see how they work together to create a great workflow for this organization. And in that article, there are demos, there are code-based examples, there's all kinds of things for your resource. So again, I can't stress enough, this is why we wanna work together and this is why open source is so amazing. You can get this high level view of what they did in this one little image right here and then you can really get into the weeds, into the down and dirty, into their code base because it's open and they're sharing it with you. It's amazing. I apologize for this terrible photo. I took it at the LF member summit a couple months ago but I was super excited because Andrea Portole who's one of the lead maintainers of CDEvents was just, it's just a quick shot of like who's collaborating and who's adopting. So as you see Argo and Flux and Harbor are adopting CDEvents but then as you also see there are other foundations helping to adopt CDEvents. You've got the open SSF, they're going to use CDEvents as a framework for security. You've got the VSM consortium, they're concerned with interoperability. You've got a cloud native computing foundation which of course houses, Argo and Flux. So from the beginning this project which I think is at version dot three now has done it in my idea the right way from the beginning. They really realize that what they're trying to solve is interoperability issue. You needed to have a common set of language, common set of pools. And so they started really reaching out to all of these projects and all of these communities to see if they were interested in working with them so that everything can kind of get kicked off the right way from the beginning. And so the reference architecture is getting built. All of these things are getting built with tools that end users currently use. So again, the framework, the reference architecture that's going into this, the amount of communication that's happening in collaboration. I mean, it's phenomenal. And like I said, they're not even in version one yet. So imagine what's going to happen as everybody continues to work together over the next few months, few years and really starts to show the value of what CDEvents can do, what interoperability really means to your pipeline and how you can work so much faster knowing that something triggered over here is going to trigger something over here because your system is so huge, you had no idea. And now you're going to be able to tell. So, where do we begin? Where are the gaps? How do we bridge them? How can we standardize the process of cross communication and collaboration? Well, I think it all starts, looking at the current communities that you're involved with, looking at the current tooling set that you're using. I'm sure like you get emails saying like your tool sets up to this different version, you know, version 8.6 or whatever. And maybe you just don't have time to upgrade, but maybe look and see what they're doing. Maybe they're saying we've now decided to, you know, adopt CDEvents and we want to show you why this is important or, you know, maybe go to the GitHub Slack channel and just start poking around, start asking questions, see what people are working on, right? Like, is there one of the principles that's really important to you that you want to see what is happening in that space? Ask around. And if so, maybe you're in the CDF Slack and you're like, I feel like this principle of continuous delivery and automation is something that maybe somebody else is working on, ask a question. I think, you know, sometimes we get meeting to death, so it's really hard, but the cool thing of again, about open source communities is that everything is transparent and out in the open. So there's always meeting notes or agendas or, you know, things that you can look at on your own time, like recordings, which is super cool. I would say, don't limit yourself to just doing your normal day-to-day if this is something that you're passionate about and you have these ideas that are like in the back of your head, but you don't know where to get started, just get started in the Slack channel. Because maybe they're like, oh, you know who I know? I know someone so that works in Jenkins and he's a part of Plugins. And what you're saying sounds like a plugin that you need added on. So why don't you go talk to them? It's amazing. I think for all the jobs that I've had, when I got to focus on open source, I think my mind, and it's still blown about how much the community cares and how much the community wants people to advance and enhance their everyday-to-day like working. So, you know, I think the first step is probably just to do a little bit of research. You know, look at the tools that you're using, see where they came from, you know, and then start poking around. Maybe start asking questions. Maybe there's a blog post that you want to write. Well, guess what? CNCF, CDF, all the foundations love posting blogs. I'm sure the projects would love to host an example that you did. So every voice matters. And I think, again, in the spirit of open source, it's always good to give back and not just take. So part of that could just be, like I said, just asking question, raising a hand and adding your voice to the conversation. And with that, I want to say thank you and here's my information. And like a lot of us out there today, I am also looking for my next opportunity. So if you know of anything or if I can help you in any way and extend my network to you, please let me know. I would love to be able to help open a door for you. And, you know, the same in return. So I will now stop sharing. Okay. So I'm a little early. So. Yeah, that was my bad. I just be eager. No, I love it. And it's just so funny. My mom's like yelling at me. She's like, is this your recycling? I'm like, lady. While you're, oh, we didn't hear it. We didn't hear it. We were just talking about that before too, before the sessions. We were talking about like random interruptions. Everything's changed. Yeah. I have a couple of questions for you. The first one is, is Argo CD not part of the CD Foundation? No, Argo CD is part of CNCF and it's graduated from the CNCF. And like I said, I know that the CDF is born in this continuous delivery space and that's their job is to like make things worse fast and secure, but CNCF has 170 something projects. And when CDF was started, Argo went to CNCF. So when you're thinking about, if you're a project and you're wondering like how you should propose it or what foundation you should propose it to, have a list, have a criteria, it's a marathon, it's not a sprint. And the same thing is true to graduate. It's a marathon and not a sprint. So you can talk more about that. Like it's- Oh, yes. But it's great, right? Getting close to graduation around the same time. Yeah, it was, I wasn't like the one that had all the stress on my shoulders, but I watched the people that did. It was my teammates. And yeah, it was a big process, like the security audits and just trying to get it pushed and like get it past all of the like different things that were asked of it. Yeah. But very much worth it. I totally agree with you. It changes a project's, I think trust and like the outreach pool as yeah. A hundred percent. And I think like, again, like the, I think the key to open source is to do the research. And it puts a little bit on you in the beginning, but that's okay because again, if you're a project and you want to donate it and you're not sure where you have to figure out, there's so many projects out there that are focused on so many different things. And you need to scope the criteria. Again, for entry, for exit, you need to like look at so many different things and the credibility factor of being a project at the CNCF or being a project at the CNCF, CDF, CNCF, OpenSSF, all of the SSFs, all of the Fs is huge. And I think it again, it allows to what you said, the reputation building and the trust, the trust for the community because they know that your friends, Pinky went through it and you got to like sit back and watch, but you worked on it and you continued to work on it. But no, I wasn't like, I remember it was like Daniel too and it was just, it's a lot, but it's like really, really worth it. Like you said, it changes. I was actually asked this question at KubeCon recently in Chicago of like, why donate a project to the CNCF? And we were discussing like the value ads and it really changes the lifecycle of a project and the outcome. And like, it gets more visibility, but it also gets this like wonderful backing and community outreach. And it's really cool. I agree. It's cool to be a part of the community like this. 100%. And when you think about it, why are you gonna get to sit down with all of these end users that are really trying to make things better? Like the, like, and that's what I mean too about my network. And I'm serious. If you guys are need a connection and you see that I'm connected to somebody, please let me know because without open source, I wouldn't have all of these connections. Like I wouldn't have been able to have this seat at the table to meet all of these people that I was just like, oh, this is just DDC. He's really cool. Oh, wait, he works for Apple. Wow, oh, he does this. Oh, wow, like, oh, Mark does this, you know? And I think it's just, it's an awesome environment. I feel the exact same way. I feel like before I became like involved in CNCF, it's like my network has just increased so much now. And I know people like all over the world that I wouldn't have known and it's so wild. I get to meet all these cool people all the time and it's my job and it's really just awesome. It's very, very cool to be a part of this community. I agree. On that note, actually, how did you yourself get started, like being involved in the open source communities? So this is kind of funny and I talked a little bit about it at CDCon. I was all-in-told. So when I started at my previous company, I started as a community manager and just like internal kind of stuff. And then we realized we were part of a bunch of foundations and I was asked to sit in on some meetings and I said, okay. And then I realized, oh, wow, there's a lot of things happening in all of these meetings. There's a lot of cool stuff that not only relates back to the company that I'm working for, but just like kind of my passion and my kind of interest, you know, like, and there's all these opportunities, like I'm a marketing person and oh my gosh, there's so many different ways that I can help, you know, these projects or the organizations help market themselves. So last June, my position shifted to open source program manager and I got to devote more of my time to just like getting my hands dirty. And then I was nominated and accepted a leadership position as the outreach marketing chair of the CDF. And then I like on a whim nominated myself for marketing chair of the CNCF and I got it. And I was like, wow, this is amazing because going from a organization with nine projects at the time to another organization that's so huge. And I like, I wrote that project mantle. Like I was like, we have got to get all of these projects as much information as they can, like as many templates to market, as many things as they can do to help them while they're making magic. So just kind of snowballs. And exactly, I have now this huge network of people that I am so excited to see virtually or in person. And it's been great. So again, sometimes you just got to be told to do something to make it happen and you'd be surprised at what comes out at the end. Yeah, that's really true. I mean, I think mine was kind of similar. Like I went from, I used to work at the State Farm and then I went to work at Weaveworks and it was like a totally different experience. Like being involved in the CNCF, it's really different and it's really, really cool. And I really do wish like everyone could experience it because it's like the nicest community of people that are so welcoming. And it's, yeah, it's just really exciting to be a part of. There is a question here too about if CD events is based on cloud event standard. So that I don't know, but I will say that in the presentation there are a bunch of links. And if you just go to the CD events website they have all of the documentation that will help you get started. And if you join the CDF Slack channel and join their working group, like you'll see everything you need. Like I said, there's links. This is what again makes open source amazing, right? Is that everything is transparent. So nobody's trying to like hide anything from you. So you can see their agenda, you can see their meeting minutes, you can see recordings of their meetings and really get yourself started. So sorry I don't have the exact answer for that. I just know that they're rocking and rolling over there and the adoption rate is awesome. And every time I hear somebody talk about CD events I get super excited because I could never say the word interoperability. And now I just got it and it's so important. I also had to practice it before I was like interoperability. It's a tough work. It's a lot. Like why didn't they work so hard, you know? This question is kind of similar where it's like, I don't know if you'll know this like for sure. I don't know where cargo light lands, but it's kind of a comment slash question. We had a presentation of cargo yesterday. It's a very interesting project to respond to problems of environments, stages, promotions. Cargo is a part of which foundation. I'm not, I'd have to look into it too. I haven't checked to see what cargo, which one it falls under yet. So that might be, go check the horrible maps. Maybe that's a good one for the Slack channel to just kind of ask around and see who can be your resource. Cause sadly I am not your resource on this one. But again, you're in an open source community with lots of people that can help. And sorry, I don't know. Yeah, no, you're fine. What's the relationship between cloud events and CD events? It's kind of like a... You're getting in the weeds, man. I know. I'm going to say that's beyond our scope. But I did want to ask like, I know you did touch on this earlier, but like, so what's your recommendation for someone to like how to get started and help and contribute to the projects and get involved in like CNCF things? So I think like the easiest way is, well, first you need to kind of determine from your own boundaries, do you want to do this at work or do you want to do this as a passion project at home? And I highly recommend and suggest and figure that out first. Because if you're going to go the at home route, well, there's so many things, right? You can look at the tools that you work on your passion projects at home. You can see like, if they're looking for contributors, maintainers, maybe they need somebody to help write documentation and you're really good at that. Maybe you're like me and you're like, well, I can just help market. Like maybe there's like outreach and networking I can help do and like there's other companies. Maybe I run a meetup or something and like I can have a speaker come in. So, okay, that's passion side. Work side, I think it's always good to look at the current tools that you're using. Look at the open source tools that you're using and then do some research. Are they looking for maintainers, contributors? What can you do? Is there something cool that you created at work that you want to help give back? And then ask your manager, hey, we're working on Flux and I would like to be able to donate five hours of my work week to helping them move Flux forward. We're working on this project, Steve. You know, Steve, it's not getting any further but if I could actually sit with them and talk to them, maybe we could help shape how this is moving forward and we can do this. Steve, Jill, Bob, whoever. I think those are- Yes, Steve, let them do what they gotta do. Come on, Steve, just do it, man. But I think you need to have justification as to why you want to do something and again, start with your internal, where do I want this to fall? Because slowly but surely, if it's a passion project, you can realize it starts creeping in and then, you know, like your night times get shorter and you're like super excited and you have all these things you want to do and then it's like all of a sudden at 7 a.m., your kid's gotta get out the door and then you gotta sit down and start work. So I think that's something that you can also, you know, relate back as value. Maybe you do a tech talk at lunch, a brown bag because you want to share what you're learning. But that's the key to development, right? Like you guys are always learning. Like you guys make the magic and in order to do that, you have to kind of stay abreast as to what's going on and joining a project at whatever level or becoming a more active member in the CNCF or CDF, taking the trainings, the certifications, like these are the people that are building the tool set and the knowledge base that is gonna get your project and your company from point A to point B. So if you can sell that in that way to your manager, I mean, Steve's just gonna have to say yes. I've not given my number and we'll make it happen. You're so right too. Cause like it's not just about like coding either. There's so much more than that. You could do documentation. Let's say you don't know the code base. You can still like actually help out the project that you're using. And I think that's a really cool place to start. I agree with you. If you're already using the open source tools, help out the community. That's awesome. And like, yeah, you're so right too. End user talks. That helps out the project so much more than people realize. So yeah, that's very cool. Okay. Is there anything else you wanted to like chat about? No, this was awesome. This was a great opportunity. I hope everybody online has a great time. I was popping in yesterday. The talks are awesome. The fact that everything is being recorded, you don't feel like you're missing anything. Again, I appreciate you letting me be here. And it's so good to see you after, seems like I guess it's been like almost like half a year. This year just went so fast. It's December. I have elves on shelves. And I said elves because my kid is obsessed. So we have five. Five. I can't believe it's December. I just like can't. It feels like we were just in Vancouver too. So it's like. Yeah. And honestly, y'all, now is a good time. Like if you want to get involved in an open source project, take the next couple of weeks when we know everything's kind of like winding down unless you're in sales and figure it out, right? So pitch it to your boss as something that you want to work on in 2024. Add that to your set of deliverables. Add that to your next performance review, right? Add that as an objective of something that you want to accomplish. Like this year is almost gone. And so it's a good time sort of reflect on like what you maybe want to do next year. So I think joining Pinky with Flux or anybody else could be a good way to go. And I think open source summit Seattle's CFPs are open too. So if anyone wants to take a look at that. I know it always feels like there's another thing to submit to you can never get to break. But yeah, I think those are open as well. So if anyone wants to submit to that as well, that'd be really awesome. If there's an open source tool that you're a fan of that'd be really cool. But also I just want to say a few things before I run out of time. So we're going to be transitioning to breakout sessions in a bit. And so if you look to the left of your screen you should see a vertical menu where you can select breakout sessions. So once we're done here, you'll want to click on that to see the next sessions and join them. And it's going to like ask you to verify that you want to leave and that's fine. But thanks so much for joining us and we'll see you back here at 330. Thank you so much, Lori. It's always a pleasure. And hopefully I get to see you in Paris. Hopefully you'll be there. You guys crossed. Yeah. Have a great one. This was awesome. Happy holidays, y'all.