 Hello folks. We'll get started in just a minute. Here. Meeting notes are in zoom. The call is being recorded. Hi guys. Hello. It's been. Is this been. Yeah, sorry. Hey, Ben. Yeah. Well, it may just be us today. Let's go ahead and get started. Let's see. What do we have? And share my. Screen. Can y'all see the screen? Should be the. Working group notes. All right. Welcome back. Jeffrey. Can't hear you if you're talking, Jeffrey. I see you're unmuted, but. No audio. I can't hear you. I hear you now. Nice to be back. Sorry for the. Absence. Now the daylight savings time is rolled around. I don't have a standing conflict like I did before. Yeah. And you have a new job. Understandable. Had to work it all out. Glad to have you. Let's see. So. Was there a meeting last week? That was out. And I guess it was canceled. I jumped on, but nobody else was there. And then I saw on the notes that it was pushed a week. Well. We had elections. Close to this time last year. And. We need to look at elections for chairs. Jeffrey, Ian, and I are the current co-chairs. And we got some rules here around it, but. Anybody can. Submit their cells. If you think someone else is a. Would be a good. Chair for this group. Then. Talk to them and have them. Submit for themselves. But you can feel free to recommend people. If you want to. We just want people to. Have the time and want to do it. If they're going to be a chair. Let's see. Daylight savings. So. I guess. EU time change is on the 27th. So. That'll be better for you, Ben. I guess whenever it shifts right now, it's further apart. Right now. Or seven. I'm sorry, you're not that far. Plus two. Plus two. All right. Plus seven, I think is. Pretty far. It's India. Yeah, there you go. And some others. Yeah. Get into the APAC times. Okay. Coming up. And we have quite a few submissions for. Cognitive telco day that I've been worked through and. Looking forward to. That event. I think it's going to. Be a good thing for. The CNC of coupon timing. And. CFPs are open for open source summit. Yeah. I would think. Go ahead. So Taylor, I just wanted to ask, I, it turned out that I will be in Valencia for, for Kubecon Europe. And. Will we have some kind of an event? Okay. Which is like for this working group. Or someone else will be there. What's out of me. Physically. I'm not sure. I don't know. I don't know. I don't know. I don't know if there are any session. We have had them in the past. The cloud native telco day is kind of. The biggest thing related to telecom. That's. First NCF at the event. Right now there's nothing planned specifically for the working group. I'm just going to work from the top down. This is just a, is this a merge. Just a pull request to change. Easy. Oops. I hit the wrong button. Dang it. Let's try that again. Squash is Victor on the call. Yes, Taylor. I'm here. Victor. You want to talk about this one. Well, it's just like a division of the, the recent. We'll never need to discover. So let's stay in the non-root best practice that we have. Just adding more. Material for. Supporting that case. See a problem with that. Just adding. A reference. What about everyone else on the call? This is about the non-root best practice. And this is a. Notice on a security issue. Essentially, saying a big ad did not ever. Less privileges. I looked at it. I saw it and I thought it was, you know, it's, it's a great pointer. I think we had like, not just the CB, but we had like, right? Like three others. Within like a month, which had the same. I wouldn't say the same root cause, but they had the same attack angle. And, and all of them. Would have been prevented. If the container was not running in root mode, therefore the new, these are all things which are, you know, just. Confirming the, what we say that's running is non-roops. Containers is the best practice practice. Sounds good. Would you add a review. Or a plus one on that. Sure. Sure. Slash Ben. What is it? My, my ID slash. No, you don't. Ben. Slash. Maybe it's, you're not. Available as a reviewer. I think in order to see him. Not least. Make a quick comment. The PR. Okay. I can also add. My guitar panel in the chat. Yeah, I got it. The problem is you don't have. Access. For me to just pitch you on that main list. Okay. This is enough. Okay. Remember what's required. You'll have to accept it though. Okay. I've accepted that. Oliver. Can you give a thumbs up or do you object? Yeah. Yeah, I'm sorry. I was just, I give a thumbs up. I just couldn't get myself off a mute there. Everybody on the clock and. Give it a thumbs up and then we can merge this. Unless you object. To adding a reference. Okay. Go give your thumbs up. Everyone on the calls now. I'm going to go on to the next one. A mouse is messing up. It's jumping all over. All right. This is enough. For. Linting. Fixes. Typos, whatever. CI jobs. Okay. I don't know if I found that one. Thanks, Sean. Dependent by. You're good with this, Victor. Sorry. Okay. Yeah. Yeah, I just. All right. I'm going to merge it. If you're okay with it, I'll just merge it. I was just pulling for the group. Right. We're back to one of yours. Yeah. Best practice for Kubernetes system components. What do we have new that hasn't been addressed? Yeah, so there is. So I, and I told. I wrote here in one of the notes that I know that I need to move. You know, this to. Another place. Okay. Another format. Okay. To be in the same format as all the other best practices. I'm just wanted to finish all the, you know, all the comments and all that closed all the content related stuff. Okay. And, and the formal things I want to leave at the end. Okay. Because just, I don't want to, you know, break the comments and stuff. So. So I think that. Yeah. I haven't, I haven't seen the latest comment on, on this question of the A back. Questions. Okay. I really wanted, you know, just to highlight. The comment here in this part. The differentiation from my point of view between a back and our back. Okay. That, that in a back unit to, you know, configure things through files and, and in our back you can configure. It through the API. But yeah, I'm going to incorporate. Okay. The latest things. And I hopefully, okay. move the, the, the fast tomorrow, hopefully I will have it ready by next meeting for, for, for accepting this. I don't think that there are too many open questions left. You gave a couple options. So, and says on that one. Yeah. I mean, I had great comments. Okay, I was happy. Okay. All the things, you know, you've mentioned already closed because things were to the comments for to the point and I could work with them. I think this one can be resolved. Don't worry about that one. All right. Other than those changes, I'm good with all of it. I'm going to click review for everybody and then. Yeah, again, I know I need to move the file itself. Okay, because it wasn't the right and right format. Okay. I actually haven't done this before, but I think that if, if I'm moving the file. I'm, I'm, I'm afraid I'm going to lose all these inline comments. This is the reason why I haven't moved it yet. You won't lose the inline comment. And if anyone makes a suggest change and you accept them, then it'll also be fine. So these will stay. You need to make sure that you work on do your changes in your branch here. Yeah. If you go in this one and you move the file. When you do a commit after the move and push it up, it will automatically update the pull request. Yeah, that's right. I already think I'd already did. File directory change shouldn't affect the comments. Okay. Go in, move it, commit your changes to your branch. And it's just tracked as one of many changes. Right. It's not going to move like release it if you like completely like started a new branch and just copied and pasted a file in there but you just need to like actually go into how it's committed and change the directory like that. And then it'll all be tracked. Awesome. What's remaining on this, other than well it's a web so Hey Taylor. Yeah. I've got to jump at half past the hour. Give a quick update on the. Let's move down to yours then because this is the one we've been waiting on. Yeah, so I just had a couple questions. I've got some things. It seems like mostly some misunderstanding of certain definitions. So I'm going to go in and great does I guess like the main thing is, is should I put like a glossary at the bottom of this, or just kind of weave the definition throughout. And then there was one comment by Pankaj. If we go down to that I don't know if people want me to remove some of the additional context or I think that let's go back. So the questions that have had some extra information. It was at the top, like this one, glossary life segment. All the processes, all of these things so this is, this is on the East case side but I don't, I don't see it as a problem to follow this for the user stories, given people some context before they. I might pick and choose some of it then like because the use case. It has a substantial be bigger assumption of like what's going to be put into it where like we said user stories were kind of specific short and sweet so people can get stuff in. But I'll put the glossary at the top just put some of the definitions in. Whatever is causing problems just add it to the top. And of course if there's anything. See this one also has it. If there's anything that you think could go into the global glossary then it can also go there, and we just link it from this user story doc. And also of course the CNCF glossary project as Victor pointed out. But starting with something in this stock sounds good. Yeah there's a few things like I was kind of surprised I needed to add definitions for but I'll do it. I'll put a little glossary at the top and then see if there's things I mean air gap probably should be added to the bigger glossaries, and then just link to just because that's common thing but feel like upstream and source most people know what that means so I'll just add something for context into the specific user story. Well Jeff, you don't have to worry I mean I went to propose that definition in the grocery so that we can resolve that. Most of it was from like Pankaj's questions so but I mean, anybody should be able to come and read these so if people in our own group are like what does it mean, you say upstream, then I should assume other people will have those questions so. But I don't think like, you know, defining upstream and one of the bigger glossaries probably makes a lot of sense just what it means specifically in this use case. I mean, they asked my main question so I'll try to get this wrapped up before next week at the glossary section and just clean some stuff up so then hopefully we can get this guy. Out of the PR phase. All right. Well, just that's it. The other, well I guess we can go through this one but top here at half an hour so let's see what you have next week Jeffrey and sure will be following up some of this week to catch up on things. Thanks. All right. So this one is about what do you do when when the best practice is not going to work for you. The end user, the one consuming these CNS or whatever the software is isn't following a best practice. The idea is we want to communicate to them. Anything that's an exception and why it's an exception so that they can make adjustments on their side. Important examples will be security. They're expecting things to follow some security best practice and it's not. They need to know how it's being handled. Okay. Victor you have a small edit. That's a good to me. So Taylor, can you retitle up here? I mean, at least remove the working in progress. label seems like a straight to reviews though. Okay, I'll do that. This one was never responded to. Don't most CNF operation have to be compliant. This has to be validated. I mean, I guess this would be like ops best practices. The same as CNS, but I think we're saying anything following best practices. So the operation of a CNF or its behavior is kind of all related. If there it could be clarified, then I think I'd rather on Kai do a suggest that it. And this has been said a few times. Yep. And again there. And again there. What do we have here? I'm going to commit this. I was just clarifying based on his words. Resolved. Commit a way. If your team builds a component use used in NFC or operate to your buddies and NFC. Yeah. This is not agreed. Ian doesn't agree to this and NFC. I'm going to not do that one. Yeah. That's true. I'm going to not commit that one because then disagreed. Two weeks ago. I moved that to Ian. Can we make this? What is this? Preventing delivery of components. I don't know. We didn't list them number one too. They're just a bullet list with no priority. Teams. Deliver. Good enough, even if they cannot are not perfect. I kind of. I don't know. Actually, that has a pretty significantly different meaning. We could, there can be situations where. Something actually cannot be done to follow a best practice because it would break something else. And that's different from it's currently not following a best practice, but may be able to change. So I'm not going to put that. I'm going to ignore the. Plants list. Because it's related to the list or whatever's been suggested. Also. Some wording that you need to review. Yeah. Okay. The mitigations aren't there, but. I think that's it. If anyone else wants to add some comments or say. Like it well enough. There you go, Victor. Okay. And that's it. We've made it through the poor. Is there anything else? Well, I just let. A few comments. Directly to Ben. So that's regarding. The change of keys meeting is required to. To have another. Additional works in the workplace. So forget to include them. You PR. And the specter. No, I just, just put those comments directly. So Ben, if you haven't seen them in the chat. So I mean, it's. I don't know if I have to put them as well in the. The PR. So. Okay. I mean, in the description is missing or. Sorry, I didn't catch that. Oh, well, if it is in the zoom chat. So it's an unbridled message, but yeah, I can. Let me do it in the PR to just to keep it. Everything open. Okay, okay, okay, okay. Yeah. Okay, okay. I see some. Okay. Victor. If, if it's, I would definitely add it into the PR. At least. Okay. All right. Is there anything else? Okay. Well, we will stop there. Thanks everyone. Thank you. Have a good day.