 Hello Lucina and all the very good morning. Hi Victor, how are you? Good, good. Yeah, ready for the start of the week? Yeah, exactly. Hello everyone. Hello. All right, I think that it's time to start. So I just started like the link of the, the meetings. So just ensure to put your name and you have any particular item to discuss. Also make sure to put it in the agenda. So probably the first item in the, in the agenda is about the cloud native to Coley. So, um, Yeah, probably the major announcement is like the CFP was extended to February 12. So if you have any particular topic or anything they want to expose or share with others, you still have time to propose it. It's a great way to share it with others and also learn from that. So anything else that I just miss it or we've seen anything that you want to add. There are nine different tracks or telco day to encourage a wide variety of topics and speakers from different telco verticals. The newest ones for this cloud native telco day include sustainability in telco. So if your telco has environmental sustainability goals. Like share the challenges and the plan. That is a new track. Another new track is. Telecom operator expectations and vision of cloud native. How operators expect to. Run networks with. Yeah, that's a native network functions. And their new track. Is production and commercial launches of CNF. So as. The cloud native. PSPs move forward in their journey using. Kubernetes and other cloud native tools. Things that are maybe going into real world production. So we'd love to hear use cases and. Experience with that. In addition to existing tracks like cloud native best practices. Networking applications, which is. Group focuses on. Developing and testing cloud native network functions. How people are using telco services in the cloud native way. Networking and Kubernetes. Sharing approaches and challenges, integrating. Helpful applications with Kubernetes and existing network environments. They're also interested in seeing observability, resilience, service availability and. If anyone's using. Multi-cloud or hybrid cloud. I'll go use cases and experiences are. We're interested to hear about that too. So it will be a half day. Events. If we had a variety of CSPs and hopefully we can have. A program that is well rounded. Exactly. Yeah, the other team is like, this is only an in person event. So there's not going to be a chance to. Watch all these sessions remotely. So. That's right. The program itself is. In person only no virtual. Real time aspect. But the events team is really good at. Putting the content on YouTube within 24 to 48 hours. So we'll be available to view, but if you're able to travel. To Amsterdam, if your company doesn't have any. Travel freezes and it's safe to travel. To keep on Europe. The coupon now has a all access. In person ticket. That provides access to keep on as well as all things. Yes, co-hosted. And so if you do plan to go to keep on in person. Be able to submit. For. Great. So. Any, any question, any comment? Any. Anything about. Cal Native date. All right. If there's no any question about it. The other thing is regarding the upcoming events. Probably the most closest is. The elephant developer testing forum, which is going to be virtual. Free. So you can, you can access to that. And. There are a few. Interesting topics there, which are encouraged to take a look at them. The others are here. I'm sure in the next screen. We just mentioned about. Also the club in. Local day. The open source. So anyone interested in going on any of these events. So probably we can jump, just jump to the. To the PRs and discuss what we have open. Okay. I just opened this PR. It's quite simple, just fixing a few things, especially the LinkedIn issues. As far as I remember, someone was reporting. I probably the major thing is like. This, which is not. What's a typo was more like a. Fixing a. A definition. So we have. We're surrounding and forwarding, which is. We were just missing that. Make a total difference. And the other thing is. Talks just changed the way to. Pass the environment variables. Instead of white spaces are using commas. And the lender was complaining about. The headers. Given that we were mixing the headers. I have to just change it to be consistent. Using. The same. The same format. Few, I guess the other are just few. Missing words. For the other thing. Yeah, it's. It's quite straightforward. So I don't know if we can. Just Mercedes or like, or someone has any. Any, any opposition to this is change. No opposition from me. I'm happy to approve it. I can. Likewise. Let me just pay the. To the chat. The quick access. Yes. We have quality. Now coming back to the issues. I think that we have. Some use. Probably the latest one was. This one. You went to mention about this one or just give an overview. I mean, it's just mainly to move. The location of the fires, right? Why just to put them. Yeah, just to make it. Where we have a consistent place to go. I mean, no poor question yet, but. There's anyone have any thoughts on that. Is it. So they did the work, but. They used to put user stories and user cases under. The dogs folder, right? Everything under that directories. Yeah. Okay. Yeah, go ahead. I just. Trying to display this. Yeah, I think I added that one. After as well. I just didn't put a link to move best practice folder. That would be the CBP piece. Okay. And it seems like we have a volunteer so. Yeah, probably. We need to help them help him to. Make sure that he understand that what he has to do and all these things. Yeah. And. Move the folder and then we probably want some sub. Task saying update all the links. Oh, that's right. Yeah. Because probably. We have some cross reference internally. Yeah. I mean, if it's, I guess, if it's going to be, you know, just someone random that's taking it. Which when you, when you add the. Good first issue tag, then. There's people that are just searching for those. And that's probably how they found it. It might be good to split it out, but we could, we could just say. As long as we add the tech, you know, the. This is just moving the folders. We need to say, move them and then update the links. I'll go add that to the issue. Okay. Relays the subject as, as, as a misspelling fix. Yeah, the other thing that I was thinking is how, I don't know how much time we can give him to respond to this. I mean, this. Definitely. Any, any help on this is appreciated, but. We don't have to rely too much on. Probably I was just thinking maybe like, giving a chance to like. One or two weeks. He's not responding. Probably when I sign it and try to find another volunteer. But yeah, it's, it's, it's. Let's give you a chance. It's too early to make conclusions for now. As soon as we feel like it, then we can do it. If he's done it by then, then that's fine. That's how I see it. Whenever that is, we got other things to work on right now. This is a low priority, but. Yeah, that's right. All right. How's that for the. Was there anything else for. I added to that ticket. Go back in it. Wow. Yeah. Good enough. It's much, much better. I like it. I mean, other links outside of the repo will, you know, not work, but. We can only deal with what we know about. So I think. All right. Let's, let's move on to the, to the next one. So. I think this, this seems to be that we can just start into. Start creating like kind of a trap for, for this one. The last time that I checked in the glossary. They have another. Terms like. Like non trivial terms, like. I think it, it helps or. Yeah, like DevOps. That's a cop. It's computing. So. I think it's, it's, it's a good time to start thinking about. CNF as a new term in the glossary. Probably. Yeah, I know that there is a lot of discussion. What is a CNF and how can, especially. The starting point, like. Some, some can consider like CNF as a container network function. Another, once you're like a cloud native network function. But whatever, like, we consider that is a proper definition. I think that we have to start the discussion probably here. Proposing something. Maybe receiving feedback from, from that point. Instead of like. Trying to get a consensus between us. What's under edge computing. All right. Yeah, that's, that's usually the template that they are following. They split the term in, in. Like three main paragraphs. I didn't know if this was a category or a. It was just a term. So everything on the left is a term. Yes. Yes. Okay. They're few, which are not like following this. Let me see if I found like a. For example, this is like more like a property. Okay. Yeah. So, yeah. And they have some special tax. Let me see if I. So internally, what they have is. H, right. So in the age, they have like this section. And they split like a different categories. Technology or. Let me see if I find home. I don't know. I don't know. I don't know. I think computing could be. Concept. They have some special tax. Like. So they're using those things to group the concepts and everything in the. Certain areas. And also they have. Let me go back. Different status. So I think only this. In the web page. But you can submit others. Under. Feedback appreciated status. Let me see if I can quickly find. Something in that category. It's going to be hard to. All of these things are. Yeah, probably it's going to be hard to find. I don't know. Just want to. That particular section, but. Yeah, we can also use. That status, like. Submitting something like a trap. I'm looking for feedback. Trying to. Move from, from that point. So. Probably going to start collecting that information and. So what do you think? Sure. I mean, we have, I think. A pretty good definition already that we can put forward for cloud. Network function. And then if you go into. Go to their glossary, they have a cloud native. Apps. On the. You can go to. Yeah. It's under a concept. First. All right. That one's pretty minimal. They had something else, but. I was trying to think if you can reference existing terms, then. That can be good to tie everything together. Which is what we've done somewhat with the cloud native network function. But our. Definition of cloud native applications is a little bit more expansive than what this is. Yeah, the other thing is we have to think about this particular. Answers to. Questions to answer. The problem that we are trying to address and. Trying to. Simplify the explanation. And I have seen. Like others. Especially. Like the scaling scaling is. One of those which has some references. Of scaling. Yeah, for example, this has a definition is a property. But it's referring to other terms. Like horizontal and vertical scaling. But I think that in our case. It's more like a. It's not a property. It's like more like a. Three questions. Yeah, but probably just starting the submitting that concept here. Maybe we can. Just initiated the discussion. And the good thing is like, they can help us to. Just simplify the concept, maybe. I mean, some of them are technical contributors. So in terms like the understanding. The concepts. But others are like, especially like Catherine, he, she's like, she has a marketing background. So it's going to be nice to have. Non-technical. I don't know if it's going to be a good effort. Yeah, I like the idea of working on some of those. Does it. Anyone have. Can you go back to the issue. Victor. Yeah, let's go ahead and maybe in the comments, we can add some ideas for. Terms that we want to define, maybe. Well, I guess you have definition. Definition. Is there any other ones that we want to put in here? Suggest. The other one that I was thinking is service mesh. I guess it's here. If I remember correctly. Yeah. Are you thinking of the mesh or the, the, the endpoints. Something about. What are you thinking about for that? Well, just, just in general, I mean. I guess. Probably this is good enough. The other thing that we can start thinking is. Check in. Or reviewing the existing best practices and all the documents. In the, in all the documentation that we have. Try to find some. Terms that we have. Probably. Export in. Oliver. Okay. Let's, I guess we can come back to this one. Unless all of her, you had anything or anybody else. Yeah, nothing to add. All right. Okay. Great. This issue. In December. I think that. Everything is still. In their discussion here. I don't know. Tom has. Something. Modified. I don't remember he. He was still working in this particular graph. So probably. He's on. He's still on. This seems to be also. Sometime, but. Probably we haven't. Discussed or like. Things in this particular proposal. Maybe the only one which could be interesting is like this one. But. I haven't heard anything from Gregory and Watson. So. We just continued. In the discussion or start proceeding with the creation of the. The draft for, for these best practice. I think, I mean, I see where you're going, Victor. I think as far as kind of push it forward, but it would be good to hear back from. I didn't, you know, whether that's Watson or, or only. But. It would be interesting to hear. I mean, I've asked internally within, you know, in terms, you know, in matrix as well, just to sort of get the views, you know, and there are a lot of discussions on this topic as well. So. And related to sort of the right level of granularity, if you will, and per, per, per, you know, per container or, you know, for microservices, but. Yeah. I don't know. I guess it would at least just be good to see get back, you know, to the response that you, that you had written. Before moving forward, but other than that. I understood Taylor's point last time too. I mean, best practices, you know, you may step away from some of them. I obviously, I think we should encourage people. Or not encourage them. I should. We're hopefully the best practices align well. They won't always lie to everyone. So I get that point. Yeah. I don't know. I guess it would at least just be good to see get back, you know, to the response that you, that you had written. For moving forward, but other than that. I understood Taylor's point last time too. I mean, best practices, you know, you may step away from some of them. I obviously, I think we should encourage people. Yeah. That's true. It's interesting. And it's also kind of controversial. Yeah. Yeah. I mean, I think that would be. Well, I don't know. I mean, maybe this is a stupid comment, but I think in some ways we were looking at, you know, cloud native network. You know, applications, functions, whatever you want to, you know, whatever term we want to use there. I would think that some of that would also drive some evolution or some change or some, you know, maybe some differences that, you know, exist to what has existed in the past. Otherwise that would basically suggest there's no challenges that, you know, for, for, for the particular area that we're looking at. So. Yeah, probably, probably also maybe the best practice is not to, and to not to use this particular approach, probably, but it would be nice to have strong arguments to not. I mean, I like what Gregory was saying, like, performance and all these things. But if this is affecting the performance, just show me the numbers. Like, okay. Or at least a simple use case where, where anyone can experiment and say, well, yeah, that's true. Yeah. Okay. Yeah, I mean, this is a, I think you've brought up a good point too. I mean this, you know, I don't know how other people, maybe people can talk to all these topics, but I know that, you know, for myself, there are times when I can bring someone who I think is more relevant, you know, or has some more experiences to, to share with the group, but I don't know when those are going to be, you know, don't necessarily know when they'll be discussed. So, for example, if we wanted to say, you know, next Monday, we want to have a conversation on this particular item, I can look and see if I, if I have someone I think that could maybe bring them to the, to the conversation, right? If it's not me. Yeah. And, you know, pros or, you know, comments pro, you know, for or against, right. And to your point, just, that's, I think that we're looking for is trying to understand the different differences of opinions. And as then, you know, what, what are we backing it up with? Do we have any, do we have any facts? Yeah, otherwise, I mean, the filing here could be like, I don't know, like, like an agree on his proposal. So, but yeah, any, any, anyone that you know can provide any interesting point or anything here is very valuable in terms like starting the discussion or like, no, continuing the discussion because the discussion has been started. So, yeah, try to, try to encourage anyone to, to, to help on this discussion. I mean, any, any particular comment or is, is valuable. So the main idea is to provide a best practice and we nice to have all the different perspectives and, and point of views. So, absolutely. Let's go back to the introduction of the, you remember this one Taylor seems to be something that is easy to do it or I don't remember why he's going to be honest. It was just like, so go ahead and go open it. It's probably easier after seeing those, the merging the final paragraph, current focus, etc. So let's go over. So that, yeah, we've, we actually did clean it up. What, what does it say? Well, now I can't see because it says three days ago. If you went in the history, I think we did this couple of months ago. We did something to clean it up and remove a few things, but the test suite is mentioned at the start and then the first paragraph at the bottom. So that, that was really just for readability, readability, there's some redundancy and stuff that could be adjusted. Okay. In this particular section, right? What's that? No, no, no, I was just saying that the redundancies in this, in this particular section, right? Yeah. So that last sentence to the first paragraph. And I don't know, it's a, the whole thing could just be cleaned up and make sure that we're clear about our, is our purpose still aligned or we put, you know, one of the things we did was make that best practices for CNF developers. We added that made sure that it was visible quickly and read me at the top. That's all. Do you think that we should add? Good first issue to this. Probably. Things needed for. For the issue, like probably we can have some fresh eyes on this and give us some. I think it'd be harder to have it as a first issue without more content. The, there's also the concepts and like. Mission, whatever, all the different things that we're thinking about for this, that you wouldn't have context. It's harder to put that sort of thing out. I think as a first issue. If there's a specific item. That doesn't require as much context. So if you can. If you can describe it explicitly, then. You can make it a. Tag it as a good first issue. Okay. Yeah. I think that one's something for us internal though, and more of. If it's a kind of a lower. Priority maintenance item that we need to get around to, but not. There's other issues I think that are more important to. Focus our time on. Yeah, okay. This is still trying to remember about this. Remember to be great when one of the sessions. Still trying to remember. Yeah, this, this was something where when we were like modifying the, the structure of the template. So it is, it is not done. It seems like it is on, right? Do you know any. Add to the, okay. So we don't have, can you go open the. Add to the table of contents. I think that's for the. Seeing enough dev best practices. Under. Yeah. Yeah. Go down to the bottom doc. In the scene of best practices process. MD. But these don't have like the security. Oh. Oh, Adam to the table of contents. To do the best practice proposal. I don't know where was this supposed to be listening to where. Add the list of the scene of best practices process to publish. Oh, it's under docs. This is more of the confusion. Best scene after. There we go. Yeah. But it is here, right? Oh, it's there. So this issue is done or not. Lucina. Oh, it's completed. Did it. We should just close it, right? Yep. Thanks to say no. All right. Any other. Issue to discuss. We still have 15 minutes, but. Have anything else to discuss or. Any particular topic. No, maybe next time. Here about the Nephi of. Oh yeah. Yeah, yeah. That's right. I didn't quite catch that. What did you say Taylor nephew? What are we saying about nephew? We can have that as a topic for maybe next week. Okay, got you. Mm hmm. Okay. And by the way, are you there? And given the video also mentioned. About the next coming events. Yeah. They're going to. There's a lot of people adding. Topics in. In the elephant. The bloper and testing forum. So. One of those are matching. Well, if that is. Everything that we have on the agenda and there's not anything else to discuss in the meeting. We can just conclude it. So, right. Thanks everyone. Thanks Victor. Thank you Victor. Bye. See you next week.