 Hello, everyone. Hello. Good day. Thanks for posting the meeting notes. Those are in the zoom chat. I've received some messages folks are out today. May have a, I don't know if there's a holiday, we may have a smaller number. We did cancel last week. Let's see. So, if you have any agenda items, please Adam. Elephant developer and testing forums coming up. Let's start tomorrow. Open Ryan. The virtual summit is tough on TV. That's later this month. Let's see open source summit. The open source summit. North America seemed to have a pretty good. Number of. Networking telecom related talks, including of course the one summit, which happened at the same time. Oliver, do you know if, if one summit is happening. During open source summit Europe. Similar to the North America. Can anyone hear me. I knew. Oh, great. Thank you. Oliver either. Maybe not Mike's muted. All right. We'll have to look at that. If there's a one summit. I presume they see a piece may be closed if it's happening. So, and new track. Just as a reminder for. If there's a one. We'll start at this. At KubeCon North American Chicago. There's a new telco and edge track. CFPs are going to close on June 18th. So anyone. Like to submit for. Telco or networking. Talk should do that. We're still looking for sponsors. We're still looking for sponsors. We're still looking for sponsors. We're still looking for sponsors. I think that's it. So last time we were here, we had a little bit of a review on the big five. And then talked about. This best practice. Containers with one process type. And started a. A Google doc. Draft for this practice. I think that's probably the next thing. And to dig back into. The draft. And I believe there's another draft that came in. With some folks out. I think it'll be. We'll get back in this week. I'll post those drafts in here. And then anyone would like to. Jump in and help. You can do it. Just reach out. Myself Victor. I think that's it. Someone else that's been trying to move us forward. All right. We have one more. Hey, Elica. Hi. Hi. We're just about to end. There wasn't really anything much today. Off. And out last week. And the. I think that the next thing that we were going to really dig back into is. The documents for some of the. Best practices that were created. From the last in May. So we'll be looking at that. This was just posted here though. So we have a. This one pull request. I think this might be a, yeah, this was a. A GitHub issue. Putting, putting all that. So this is pretty sure for. Just moving the. Document content under the docs folder. While we're on this, I'm just curious, is it possible? Or would it make sense to. Like prior to the next meeting, for example, I know that, you know, in the meeting minute. Document, we, you know, we can always add agenda items, but. You know, if we had like, you know, after that, sort of as we close these meetings, if maybe just have a. Sort of what's on the agenda for next week, like planned. You know, that doesn't mean it can't vary, but it might help for. People who want to prepare in advance. So for example, you just pointed out some things we may probably will be talking about the next time around. Sure. And we usually do ask. And it's if someone says something, but we could put it on there. Ahead of time, just. It'll sometimes end up action items, but not added. But we could try to do that. Yeah. Is there anything other than what I mentioned, as far as the. No, I think the one you just. I think the, there was one of the issues that you were showing there. Second. Well, I mean, the poll request to move them. Yeah, it wasn't that one, but I think there was, you said. There was a best practice proposal that we have been discussing. And the container should have one process category of type. So for example, if we, if we think we will have some more discussion on that, and we have that in the agenda item that might also allow people to. Deprep and or bring, you know, people with viewpoints to that discussion. That's what I was thinking, you know, basically then people know it's going to happen. And then at least the plan is to have a chat about it. It's in the issues. If you're, if you're wondering, you know, you know, which one I mean, right? Uh-huh. This one. Yep. Well. Yeah, I think the next thing on that was just the. To put a proposal forward. So there's been some discussions and that. Issue and some discussion. Um, on other. Not non-senate partner related places. And it would. Be easier if we actually had a full. Here's the full proposal. Rather than an idea. I think the issue is kind of more just an idea. So. Finish. What was this? Add content to. Here it is. So this needs to be. Turned into a full draft. So here's the start of it. Whatever this is going to be. Called. There was some. Seemed to be some. Confusion around. The wording when it said one process type. I think it meant one process. You can only have a single process and at several other. Misunderstandings, I guess this. I would, I'd call it rather than. What is the actual intent? And then the focus ended up being on misunderstandings rather than. Let's actually talk about the intent of this. And it seemed like if we had. You know, I think it actually has the full summary and motivation and all this written out. At that point, we can focus on. What are we actually trying to recommend as a best practice? So this is the draft on that started. Week before last. So this is what I was referring to all of her. Need to work on and. Make sense. Work on that this week. And then we'll go to the next slide. And then we'll go to the next slide. And then we'll go to the next slide. And then people can comment either directly on the Google doc, which is. I've linked now. Or. In the poor question itself. Makes sense. We've been talking with. A larger group of service providers. From. Some folks that met. I've. Some hoping to get more direct feedback from the service providers on the. Best practice. Areas that they care about. I know that onboarding of CNS. However. The phrasing and stuff would be the onboarding deployment. Practices around that. Automation of network. Configuration, programmable networks, those sort of things were. Repeated topics. By different folks. So it seems like. Some best practices in those areas would be. Good. To put forward. But Oliver, if y'all are hearing something, I'd like to make sure that we're catching on. No, then. Ylda co, what do you care about? What do you want to see? In what context? What do we do from the working group. C and CF community. I don't know. Collaboration across groups. What, what do you want to see? What. What should we be working on in your mind? I'm always pro collaboration. That never happens enough in my opinion. So that one is on top of my list. And there's some commonality where we could collaborate or. Some pain that you're saying that. You keep hearing, but nobody's. Trying to resolve. Together. Even coming together to discuss and put forward their pain points. Trying to think if there's anything that that's more CNF specific. When it comes to the, we do have an edge working group. Or well, edge and distributed infrastructure focused working group. I think that's more accurate under the opening for a foundation umbrella. And we've been discussing AI recently. I don't know if that's a topic that came up for CNFs as well. Or, or it's too early or not applicable in this space yet. But that's one of the conversations that, that keeps coming back. We had a presentation about DevOps. And generative AI today. I think it was pretty interesting. So if that is something that came up in this working group as well, that could be something to look into throughout the whole stack. Or the full stack. That could be interesting. Yeah, I think. The working this working group is going to need to expand. It's. Focus, I guess, but expand what it's publicly. And saying it's working on and willing to work on. Beyond what we had stated before. Just based on what I'm hearing from. I would say service providers would be the drivers on what are the need for everybody. If you're creating a product, it's probably. Going towards the service providers. If you're an integrator, you're probably taking. Different products and the whole putting the stack together for the service provider. So what I'm hearing it seems like it needs to expand. So I think. When we say CNS. That's been. What is a word that we can use that gives people some focus, but it's probably. Move. We've moved past it being as helpful. Where some people go, well, I'm not building a CNS. So I don't need to talk to you, but if you go, well, hold on, you're helping deploy a CNS for. You're monitoring CNS. Or whatever it may be. The full stack. What you're saying. I think full stack as far as DevOps and. How do you manage all of it? Is important to look at. And it's been there the whole time. It's just. When. There was a point in the past when you said, well, you care about all of it. What is the full stack? Then sometimes it would get off and focus on one. Very small part of the stack and say, you can't do this. So we don't need to talk at all. And I think that ended up being one of the main reasons to go, okay, we'll just focus on. Applications. That are running at some certain level and ignore the others, but that was, that's kind of always been temporary. And I think it's kind of time to expand. There's been a request for it for a long time. So how do, how do we do these other things? If there's like some links to that you could recommend either talks or. Projects or whatever, if you can drop a man and. Maybe we go and dig into some of the areas and see. What where we could look at for some collaboration would be good. I'll throw some links into the into the document. Thank you. Oliver, do you have anything else? I added these two things for action items, which can be moved that into the agenda for. The next one is for the next fall, like you're suggesting. Yeah, I bet that was all that makes sense. All right. All right, well, then we'll end it here unless anyone has anything else. Thanks everyone. Thank you. I'll see you next week. Thanks. Have a good day.