 Hello, everyone. We will give you a few minutes to wait for us to join. Okay. It is five minutes after the hour. This time I'm going to leave this, this, this meeting. So if you haven't done, please put your name in the attendance list. So I tried to copy the link of these many notes in the chat. So everything is there. And also you have any particular topic to discuss. Feel free to put that topic in the agenda. So I guess the Lucina with that announcement, the awful papers is going to be closing in seven days. That's right. So probably if you have any particular idea suggestion, feel free to submit your proposal. It's a great event which is going to happen before the coupon. And also, by the way, can you hear me? Oh, yes, we can hear you. Hi, sorry, I was triple muted. That's fine. I mean, yeah, that's the first announcement that we have it for for the end that so regarding the incoming events. The first one that we have it is the open source Latin America. This is going to be virtual. So I was checking the release of events. The release of the topics are related to this particular event. So I captured my attention up to for this particular event. The first one is going to be a keynote. And the other one is is going to be delivered by Ronnie, regarding the garden networking. So I don't remember exactly the cost of this event, but I guess is probably could be deserved to attend it. So maybe there is another one, another topics that you could be interested in attending. So just try to summarize what I consider interesting for from the networking perspective. Regarding the open source summit Europe. I tried to also collect all the interesting sessions regarding that workings. So probably I just keep some of them. Again, I'm not sure I heard this particular event. I'm not sure if this is going to be a hybrid event or it's just going to be in person. So, but yeah, I've this could be some of the topics that you could capture your attention or like maybe it could be interesting attending. There is a lot of other sessions related with the sbom and EPF and other topics, which may be could be also related with networks in a non implicit way, I guess. So, yes. Anything else regarding the upcoming events. Anything that you want to add Lucina or like One request for cloud native telco day. The current event is a half day event at cube con North America in Detroit. And it's currently scheduled to be an in person only event sponsorships are still available until August 12. Because if any one company is interested in sponsoring this event, then it would open up the opportunity for virtual attendance. Otherwise, it would be an in person only event. So, two, two action items, I suppose, for us or come into telco day, which would be the CFP's do end of the next Monday, the eighth, and then sponsorships do by the 12th to open up that virtual. Do you know if you need volunteers power for reviewing the papers or not at this moment. Who's on the program committee this year. Okay. I'll check in. I have that same question. Thank you. Yeah, thank you. Yeah, that will also possibly to also participate in this particular event. All right. I have two particular topics to discuss in this meeting. The first one is related with the PR that the Tom mentioned the previous session. So I don't know you having had time to take a look and verify or like review it. If you haven't had time, please request to take a look and read that everything is covered. And it's explained clearly what could be the best way to document a best practice. In my case, the only thing that I suggest was to restructure this particular thing because I consider like there are a few things that are part of the initial bullet. So something that we can discuss online offline. But also if you see something that is not clear for you or like you want to add more information or steps in the process, I encourage you to provide feedback. Can you use the display the rich stiff or whatever the little button that all. Yeah, and then do that for each one of us are looking. Yeah. I was out a lot last week. So I'm just reviewing this it looks good it looks like a lot of the stuff that we had been talking through has been captured. Specifically, there's updates all over but I'm specifically talking about CNF best practice process MD. Covering a lot of it. That was good. So, did, was there any feedback last week. No, well, the only feedback but I put it I just put it in the morning was just regarding this particular point. So, my suggestion was, if you see like all these three points or bullets are referring similar to this. So I just kind of like, they are like two bullets. And this is seems to be an example like, so probably it's not a bullet per se. All right, maybe it could even be it could also be a sub. Yeah, or note or something like that and what else. How is this. This isn't Tom's. All right. Can we do a suggest that it on those things right now. I think that I did in the morning. You've already done a suggest that it. Yeah, yeah. All right. It is probably here. Yeah. Yeah, it's here. All right. It's like all of them. I mean, he also captured this. To do or like the next things to do. So I don't know if you'll just remove it from here like just keep it as a comment. Oh, let me switch back ideas. Well, I mean, if it's a comment, I guess it's fine. Yeah, yeah, it's not. Or we can maybe use to do work. Like, I don't know if it is enabled for this rapper like capturing all the to do. So as a issues or like a PR as an issues. Issues. Probably more likely that I get remembered. We created an issue. Did you know it? Well, let me check if it is passing the checks. Yeah, the last time was having some issues with the spell check. Yeah. Yeah, he has also Mark link. Mark down the errors and maybe. Yeah, that's that's the only two things that he has issues. Oh, no natural language error. API issue that it looked like wasn't it. It is. Oh, it's up. What annoying. And rep who has to be repost 30. Okay. Yeah. That one probably should be adjusted. I think it's okay to say repo. Not a big deal. Maybe the only ones are like more. Yeah. Yeah. Yeah. We have to contact Tom to modify those things, right? Or should we just fix them by him? I mean, we can do a suggested it. So that they can be accepted, but those aren't a big deal. I would like the sub bullets on that. That you pointed out, I think are a bigger deal than these, but. It looks like it's a good iteration for the process. Get that out there and then get some feedback, maybe a. Questions like. A lot of it came from things where someone says, what do we do about this? So then we can answer that. Added into the process. Yeah. They're not familiar. Okay. Perfect. So it's only PR, but we have open, I guess is you have received anything else the moment. Or we. Well, the other one is from Jeff. So it's still. Yeah, we'll have some comments, but I don't know. I feel like that one was unnecessarily blocked for too long and needs to move forward. It's not a best practice. It's use cases and user stories. As long as it provides some context that's helpful. Then we need to move it forward. Okay. Anyways, we'll see if we can maybe get Jeff on this. I don't think there was much left. Clarification after clarification on little details, but again, user stories and use cases. It's not as. I think urgent to have all that perfect. Yeah, that's true. I mean, the other. Regarding the issues that it is reflecting is just cosmetic things like regarding. Martin and. Turn out her stoppers. So in this case, should we request more feedback or. Yeah, just if you can, do you have access to make them. Re start over. I need to get, I'll increase your access on that. So you can request that people redo their reviews. You should be able to refresh and do it. So. Yeah, sounds good. I don't know why his keep showing like that. The last one was from yen. Similar rates. There were some requests for clarifications. Just need to accept those and move it forward. Should I just also request to. Take a look again. Yeah. Maybe tag in the bottom comment. Review and accept. All right. Well, those are regarding the PR that we have open. There's only these three. We have some issues. Okay. But this is how just break one. The PRs. She will just keep this open. I mean, some of them are. More than one year older. So. Maybe it should be time to. Close them or like. Do something. I guess at least review so that. The oldest one, I think is one where we plan to and should move forward on. Creating that as a best practice sooner than later. It's one that was already agreed to by a lot of people when it was not. And we have content for it. The resilience table, which is that one. I feel like. Lucina may have created a PR for this already. Or somebody. Can you click on the link for the table of contents? Let's go look. No. This needs to be added. Still hadn't been at. Okay. It's not there. All right. It needs to be open. Okay. So. Multi multi interface. Yeah, we have. This discussion. Yeah. The other day I was reading. In a slack channel. Someone was mentioning. There were someone working in the. In the cap to add in. Distinct natively and the CNI. So I haven't had time to verify that in that. Affirmation, I mean, I'm not sure if that is true, like. I don't know. I don't know. It's. Cuban at this. Proplex is like, it was just like a misunderstanding. So. Which you. This is still like hot topic, right? Like. Maybe we, we should just keep it open. We can get more information and reactivate this particular. Discussion topic. Yeah. So. When this new changes and Kubernetes moves to production. What the effect is. There's some thoughts that. The current CNIs are going to be less. Some of the features and what they're doing is going to be. Less. Useful or not, not needed. What's happening? Are you in. In the loop on the new changes that are coming? No, I don't know, but I would like to be involved. Definitely because I have invested a lot of time in this particular topic. So I would like to know if. Someone else is doing. Anything specific in this. Yeah. Maybe just assign to myself. And try to either this particular. Yeah. Daniel said that there. Bel canada's been. Keeping track of that. So. You could. Investigate some yourself and maybe reach out to Daniel and see if he'd be willing to come talk as well. Okay. Is this his. People that handle. Yeah. Okay. He's also in. Slack and the CNF working group. Channel and stuff. So. Okay. Not. So. Right now. Our. Tree or like seal five. I think it's officially still fire. So. I guess it's still a good idea because. Maybe we should just reconsider like. And also, well, regarding this similar topic. We have. These interspersed is. So we should keep it as it is or like. Try to reach anyone and see if. If they have changed the company or like. They still interest on this or like. Or at least. Add the new names. We have new people. They call like maybe. We should be. Listed in this particular. File. So maybe. Could be a good time to. To see if what we can do with this particular list. Yeah. I mean, I. I think eventually that's going to be. Become harder and harder to keep up with, but, you know, it does seem. Good to know, like one of the, one of the things is. Who is where when you have people move around and. Are they. Representing what company and stuff whenever they're interacting. Is important for some of the stuff, especially like voting, but. Yeah, for example, Ronnie is now in the foundation. For sure. Right. Some others have been changed. This year. I think they may be. GitHub. User names when you. Highlight over them. Do they go to their. Yeah. You know, so one thing that we could do is. Open an issue and do like a. Status check. Don't know what to call it. But some type of status check and we tag everyone in this entire interested parties. And then just say, you know, please. Provide an update if it's changed. And if nothing's changed, then you can leave it alone. And since we have their user names, then we can highlight and drop them right in, you know, turn them into ads and. Everyone will get tagged that's in the. File and it's relevant to them since they're there. And for those who we don't have. They're. Um. Get to username. Yeah. Maybe create another ticket to try to. Review and find. GitHub user names for the people that aren't there. Yeah, that could be an effort and then. You know, if you can't find them. All right. Okay. So, so. So regarding the. Issue. So. Should we. Reactive it like consider like something. Or. Just ignore it. We talked about it quite a bit and said that three same reasonable. So a PR to update that. Okay. So. Any old and dear like. I think it just didn't happen. Also, I think myself like, I mean, it seems to be something simple. Right. Like. Do we have like a file or like it's just. Yeah, let's do that really quick. Let's go get the files. So sure if you want to assign yourself and then. The other part would be, let's go open the couple of files. So the. Contributor. The document, I think was one of them. And then maybe the governance document. We're specifically talking about. Non best practices, like the user stories and use cases. But you could put review. In that ticket and then put a link to the different documents. It's going to be further down your voting procedure. Some of this is about. Voting for. The co-chair. So this is, it's. Further down in the document for the. There we go. Yeah. So it's delegating. To the contributor guide for some of the changes. And then saying. Changes to the governance and charter. So. I think we need a higher amount of approval. Although the decision process hadn't been finished. All right. You got, I mean. Which partly. So click on the contributing guideline. And the, yep. There you go. It is. There you go. So that's probably the only place we can look. You know, other areas, but I think that's it. So that one would be three approvals. Okay. Acceptance steps. All of these also has to change, right? Now has to be three. Yeah. What was a. Issue. Discloses. You didn't create like any. PR or something. I'm sorry. I was, I was thinking that. That actually we create like a PR, but it seems like just. It just, it was just marriage, right? Oh yeah. I think you would have had to, when you did the commit, you have to choose to. You have right access right now. So you'll have to choose when you're doing a commit. You'd have to do the drop down that says create a new branch. And then after that, you'll create. The PR. It's all right. You did a commit your reference that ticket. I think that's probably enough. Okay. Hopefully I did it correctly. Yeah, it looked good. And we've had a lot of discussion about that one. And this is close. Yeah, now it's close. Okay. All right. All right. The only last two things that I just put it in the agenda was regarding the. The environment environment sustainability working group. The comment that you. Well, basically. The last, the last meeting. We bring that topic to discussion. We provided the link to take a look. Oh yeah. I found two places in the. In the green software engineer as a suggestions to regarding to the networking. So, especially for, for microservice architecture. The most obviously one was to optimize the network traffic. And the other thing was understanding the, the, the latency limits. So, but this is when you are designing microservices and things that you have to consider in order to. Improve your green. Your food print in the servers. So. Just put those references. If anyone is interesting to. To read it or. Try to start discussion there. All right. That's it. So. Anything else, anything that I haven't. Should to know, like. What are best practices that have the side effect of being. Also environmentally. Positive. Our mission right now is about best practices and kind of tying in with. Efficiency and other things. On use of in. Kubernetes framework and resources. I think that there's. Going to be roll over. I mean, one of the. Main points that's been put forward is. Better. More efficient use of the hardware resources. In Kubernetes, like. A long-term climb. So it seems like. There's going to be best practices that. Then end up relate. In that and other places. That ended up having an impact that would be. Relevant. To that. Working group. And what they're looking at. Without having to just focus on the environmental stuff where you can come up with things that may not be. Aligned with the cloud native best practices. I don't think we have to do a full switch to look at that. We can say what are the cloud native best practices that have a positive environmental. Impact. Yeah. Awesome to have those ones. Also cover them. All right. Any, any, anything else, any other topic? Any. Not for me. Nothing else from my side. Well, if that is the case, maybe. We can discuss all the topics the next week. And thanks also for. Attending the meeting. Thanks, Victor. Thanks everyone. Thank you. Great. Still. Thank you. Bye-bye.