 So, let's just get started. I'm not sure we'll show up. Okay, so I'm going to put this in the chat. I'm sure you all have it, but just in case. I'll put my name in a little bit. Okay. Welcome to the glossary meeting. So, this is the CCF meetings to please. Appear to the code of conduct. Glossary updates. So we did update the how to doc or we Valeria did that and so she's from the Spanish team. She is a docs, a technical writer, and has a lot of expertise with technical docs and was like hey what, what do you think if I do some best practices and things so that's great because we just did it. But like what we thought would be right. Right, so she added like a few things that make it really good and also I took the opportunity to again like update the who can contribute a little bit more to make it even more specific and I think one of things because we're saying if you're a newbie. I cannot really do this, but we're saying like, you can if you tag team with an expert, right, because if you are and if you, if, if you have someone like you, like, you're collaborating with them and if the expert says this is ready to go then. So it's like it's absolutely possible but you will have to find someone who works with you. It cannot be the maintainers right like the maintainers cannot take that role. At least it gives people an opportunity because we're saying localization is better for newbies but not everyone speaks another language right or is proficient in another language so that at least gives people who want to contribute to the English one an opportunity to do so. At KubeCon so as Annalisa knows, we're going to have a panel discussion. Annalisa will be joining us as well where we're going to talk about all the different things that people resources people have to get started with native. We're also going to have lots of re stickers available. So remember the little sticker boxes with the project boxes last time that we're gone right away. So, yeah, we asked if we could have them again. There is no way to see like how good it is but if people stick it on their computers, I guess like some people will see it and most people probably think it's a CNC sticker because they look just the same but at some point they realize it's a glossary and I was like what is this right. So I think it will work. And then Taylor will be mentioning the glossary he's kind of is now on the CNC and CNCF part aligned with the business values the subcommittee because it makes a lot of sense for because he's like the head of ecosystem at the CNCF. And so he talks to end users and end users need all these resources so he is, he sees the value. And that's really good because he is someone who has keynotes, right. So it's to have someone who is on that big stage and can power just just. Yeah, yeah just tell people about it because big stage is where most people will hear about it so. So that's exciting to have him on board. And then the issue templates have now a little, you don't only have to confirm that you want to work on it you also have to come from that you want to work on it, and that you have read and agreed to the who can contribute like that that applies that you qualify right so. So if you check that you are a cloud native expert. It's like, or you have someone who is an expert who's working with you. Right like you cannot write definition from scratch if you don't know cloud native. So that's clear. That's going to be very difficult. And then that's it from the glossary I think so over to you, Silk. Hi, I just hope to share that we previously we tested to update or localization development branches and as you can see our teams. Updated their branches according to the issue so I just say thanks to every localization teams. Quickly. So, there's no discussion issue but I hope to share. Yeah, and the next one is about all the teams localization effort, they are about to finish their first live version. They wanted to finish it. Finish it before coupon. So that maybe they can, they hope to share their life with them to others people cook on. So I will actively participate in. Helping with the team to make it right. So that's all from the localization update. Okay, and maybe if they do manage, we can tell Taylor and maybe he can just mention that that latest language came life right so I don't know because that would, it's actually almost breaking news. Thanks. Yeah, we can go to the specific team updates. Maybe no I can. Yeah, I can, I can start. So, as I said in the beginning, lately I have a hard time to follow up on all those things but what I did is I, I made sure that the blog post is kind of ready content wise. So it could be reviewed for more editing maybe. So the link Catherine or and some, some channel and mentioned to maybe you can have a look. And right now I, I'm reviewing the chaos engineering term, just work in progress. Yeah, that's basically it from the German localization team. That's nice. Progress. Yes, at least some small progress. I hope to be the blog post. Yeah. Yeah, the next team, maybe Korean and I added one item. Korean also have some progress. We are working on and finishes on terms, text terms. So we are going to open up here to merge those Korean terms into main branch soon. That's all for the Korean localization team. And maybe I'm not Lisa you can introduce. Yeah. We don't have much to say today, unfortunately. Yeah, we got, yeah, we got, we got back to you of the initial members that got lost due to familiar and personal reasons but they are back. So we need to go quicker from now onwards, but we do not have great, great news for today. I would like to work more on the how to contribute part because I realize that we only translated it from English, and we didn't localize for real but we do think about the workflow the processes and steps that Italian contributors should take because they are a bit different from the ones that are dedicated for the main language, the source language from English. So that will be my next commitment, let's say. I will keep on translating, and I should focus on that too, because otherwise, new members get lost there, they don't understand exactly what to do. So that's, that's what is in plan. Yeah, and maybe like one thing that you can do as well, Valeria from the Spanish team is super nice and approachable and, and as I mentioned, that's what I wish I want. Ideally I would love for a different localization team to kind of help each other. And she should be on the slide. Yeah, if you don't know exactly who she is or whatever because she did like well if you if you don't know, like let me know and just ask her maybe for best practices or something, you know, like, because we have someone who was really good at documentation and so we should ask her. Yeah. Thank you. Okay, and then I'm not sure who wrote this but it was me. So I, I went through all my GitHub notifications. And I, I recognize some stuff that I added here and so two terms EPPF and ingress don't have an assignee right now so I'd say we are looking for volunteers to take over this term in English to write something about it. Yeah. It's basically. Yeah, and I was assigned to it like I saw still so I took him off because like yeah, a long time so it's because maybe people like in our docs we say it is assigned here or not a lot so it's like, it's basically yeah, good. Yeah, good point and see that it is up for brass. Okay cool and then, since we're talking about that we have the runtime discussion like going on in the chat. So, whether to include it or not. And no you were saying to be cloud. My question was like if it is a fun because it's like in the, in the landscape you have the runtime later so it's like that's why I was like yeah like if you look at the landscape there's runtime provisioning and it's like, what is it. I think, I'm not sure if it needs to be specific for cloud native if it is a fun fundamentals to understand because it's like the runtime and that landscape architecture does not necessarily. I mean it is a lot of cloud native landscape but, and I have, I'm actually happy that Chris kind of suggested that because runtime is something that has been kind of mysterious to me too I don't really. Someone explained it to me at some point it was okay and it's like container runtime blah blah runtime and it's like and then I forgot and it's like I have to say, no it's part of our lexicon it's like, it's not part of my link and service mesh. You know world so I don't really ignored it so. Yeah, I'm looking forward to so I can learn. So what do you think about versus cloud native or just like fundamentals like, what is the data center what is a, you know what is a cluster. What is that concept so you can understand the landscape right. Yeah, it's kind of tricky. And also with the fact that it's an important fundamental term, but I just wanted to make sure that we that we that we know that when we're talking about runtime in our grocery it's like runtime regarding cloud native, but there's also run times. In the non cloud native world, like in the program. If we, we would have to capture that what we said like runtime is this and in the cloud native context, it means this. So because yeah exactly to understand what runtime is before to understand what it means for top. Yeah, yeah, so. I wanted to make sure. Yeah. And then adding the context. Yeah, it's fair. I remember that we have a similar service. In case in our grocery we have service town and we. The term division start with in cloud native. We say service. So maybe runtime can be a pretty couple to stay me. Yeah, yeah. Service services that you said. Yeah, I think we have service right. I don't remember having done the but it's like, yeah, I haven't looked at that definition for a long time. Yeah, I think we have kind of service and it is, as you know, it is general time in cloud native or not cloud native but we when we added to grocery, we mentioned that this time is about the cloud native. In cloud native domain we think services like this. Yeah. Yeah. Yeah, runtime is a very similar thing and yeah, we can put many places, the runtime runtime have very common terminology in it earlier. It can be container runtime or virtual machine runtime, program runtime software runtime library. We can apply that time in everywhere but if we add the runtime in our grocery we have to keep focused on the. What is runtime in cloud native domain. Yeah. I think it has many different meanings. It's not always time of execution is something else when you combine it with some other words. Oh, okay. Yeah, I mean it's it's not a context I'd say I mean it's, it's true what you said it's about running something right but it's it's more yeah it's it's more levels I say it's more context I mean and in the context of a programming language for example when you take Java, which is a major programming language. There's this Java virtual machine, which is the runtime for Java code, right, which which runs the Java code on them on your machine and when you are talking about the container runtime. It's the thing that runs containers machine or whatever. And, yeah, and when I when I was looking at the tag runtime and how many projects or which projects they listed that are included to the tag runtime I recognize okay for someone who comes from the programming side of things understand something different for for runtime than someone who who's on the native realm. Yeah, so it's container runtime or yeah runtime now. It's yeah it's tricky but but I'm totally fine when we treat it like service and say okay. We know that runtime may refer to different kind of things but in this realm of cloud native we define it as or we understand as this and that. Yeah. Okay. Good. So, something approved and are we going to call it cloud native or just like just runtime right and then say like that we're referring to run. Yeah. Yeah, different run times within the cloud native, if they are many. Okay, then. Oh, these are the things stateful app. Yeah. It's like, I don't know it's like, and then we had someone who yeah there's always like newbies who want to grab it and I had someone who was more senior who wanted to do that and then he said like no that the other person's like no this is not a newbie. It is kind of challenging. So, and it's like yeah if you see like this have like the history of this is like ridiculous. Here it's like me let me let me let me and then look at me. So hoping so many people. Mommy is in Italy. Huh. It sounds like we chat. What's up chats. Oh yeah. We have this chat for your son, who goes to school and they get mad. And they always have that me me me me me who wants to do that me me. Thank you. Thank you. Thank you. Thank you. Thank you. So, some of the same. I get crazy. So, well I feel like that's something that we should do internally and with we it's like I'm just editing because I know this is like, like with all of them like some of them I can give a first try and then give it to you but this one I Yeah, I know we have like you were working on our back. Yeah, so maybe open it. I had a look and I guess we agreed on something. We just have to. Yeah. Yeah, exactly. So I applied some suggestion, I guess, and I feel like we can now merge it. At least, I mean we, at some point we said the terms and don't have to be perfect perfect. We, we are also happy with the almost perfect version and then we can still improve but I feel like this is right now in a good state. I have an idea. Why don't we have when we're not 100% happy, we make a little disclaimer on top, you know, say like this may need some work kind of like tag like so people who are using it kind of know that okay this is this almost a call to action. Yeah, it's a good idea but but for this specific one I, I feel that it's okay. But in general, I think like if we're like they're almost there and it's like a little this client, because then people may see it and like hey I can improve that because people who use it will see that they will not see the issue, the GitHub repo because no one visit that visits that give top repo unless they want to contribute. Yeah, makes sense. We might get more contributions from people who are familiar with it. I feel like we should write it down otherwise we'll forget about it. Do we have the, then we have action items. We had some action we had this one point. Yeah. I mean you can just you can just add another section. Merge. Okay terms with this. I don't know the language but we can. Yeah, what we can think about what we put like a little I actually kind of. Yeah, for the art. Yeah, for the art back there's in my opinion just maybe some editing. Maybe you can just check if there's anything fine from the wording. And then it should be, I guess it should be cool. Let me put that on my. Okay, and then for. I think for these we just decided that we were going to have just called computing, I thought. I wasn't sure anymore. That's why I just put them here because I felt that that they are related somehow and the communication in the issues and PRs was not transparent, even though we may have decided something. We decided in the meeting not and that's why it's not. So I think we wanted to get like we said, cloud computing can be private. Yeah, exactly. So we just need cloud computing and then we mentioned, and that's where I have had like a back and forth. And then, yeah, this, we don't need this because it will be mentioned. Okay. Now we just skip it. Yeah, okay. Can we just also write that down maybe in the action item section so that someone can like follow up and communicate that to the. How much spacing. So we just have cloud computing. Yeah. I can take that you can write my name on it so I will just make sure that the communication is transparent there. And this is for everyone. That's like a longer process that's like it's not a one thing but we probably I'm going to keep this action item here. Um, continuously so we don't forget about that. Do we have a PR template, haven't we? I think so. I'm not sure. It's a long time ago that I opened the PR. Yeah, I was thinking maybe we can just add a section to the PR template saying, saying that yeah. I don't know if the if the term is not like 100% good. Please add disclaimer or something. But I think that's that's something for the maintainers to. Yeah, sure. I think that I should decide right like because I think they will try to do their best to kind of say and we can say like okay. It's not quite there yet we don't have time to kind of improve it right now. It's good enough to. It's still valuable right like the key is it is it valuable if it's valuable we don't want to hide people right. Yeah, sure. Yeah, we add that little disclaimer and like with an action item. If you know like, if you know how to improve is like please do. And then yeah, I was just thinking about how we can make sure that we don't forget about it. But yeah. I started doing this to you is adding action items I'm going to add a template. Because like when we do action items and here it's like lost. And then what I can actually items that are continuous is keeping them in the template. Yeah. So each time we can look at them like so that will. Yeah, let's see. It's worked for me. It's worked for me so far with the action items. It's pretty good. Is that like you, you, you make yourself accountable and then you're like, Oh my God, it's embarrassing. I didn't do this for the second meeting in a row and then you start doing it because it's embarrassing. Sorry, so glad I didn't want to interrupt you. Regarding the private cloud and cloud computing. We also have the public cloud issue and there is public cloud issue. New, new term suggestion for public cloud here. So it's only need to. Yeah. Yeah, not accepted. Yeah, I would like just just also include maybe the private and public and then I will. So it's basically telling three, three issues. No, enclosing them. But for private and public will say that it will be included. Yeah, existing term. Okay. So it's everything that was on the list. Anything else that anyone has to comes to mind. Yeah, one thing about the grocery repository. I don't know. There are some permission levels, such as maintainer and admin approval. In case of glossary maintainer. No, Catherine. Only I am. Only the admin who can who can control everything in the grocery repository, including course March of PR. That's what I only can do right now. So maybe we need to give that level to other maintainers so that Noah Catherine and June can merge the PR to merge development branches to into main branch. So my only concern is when I see those things, it's like, okay, it's good. I'm clicking work. I don't know what I'm looking for. So if you want to give me that power and if you say that's if you approved or no. I'm fine, but I'm just saying I'm, I may look at it, but I'm not sure what I'm looking at. Okay, there is no approval. There's no real review right there was just like a click. Yeah, so yeah, it should be given to who understand the other things. Maybe if can be and can be right. Yeah, I, I, I understand where this comes from. I mean, it's kind of a bottleneck situation when only one person can do those things right. I understand Catherine when she says okay I don't know what I'm doing here. But yeah I was I was thinking at least to who and who who works pretty closely with the stuff that that circle does would make sense. For me, I mean I understand those things as well but I don't have to have this this rights but more than one person should have those things because I, I think it's not only about merging the PR was also some stuff that was setting up the new, the new localization teams I guess so it's more than just merging the PRs but yeah. Right. So it may be June. Is it okay to give the admin authority to you. I have same opinion as Noah. So, yeah, it would be great to. Yeah. Noah and me and. Yeah, okay then let me, let me open up here. I would like to make June, maybe June first, and to have the meeting of the meeting authority. I guess we are going to. Yeah, and I'm always like if there is like a moment where something needs to be merged and you know it's correct and are confident and like I can always do that kind of thing but I would only do it if you say. This is good. You know, like it's like, not otherwise I, that's why some of the PRs I see there or I ignore it because it's like I don't want to review something that I can't really review so that's not. It's not the purpose to just let go and say like oh, someone approved so I'll just approve and trust it that's not the idea. Yeah. if there is that case and we're confident and like, Jihun is gone and it's just you and it's like, I don't know, like I'm always happy, but it should be like very specific and one of the cases cause, yeah. Okay, thanks. Okay, so who is going to Kupuna Noa and Alisa is? Noa, are you? No, I'm not. You know, but you need to win another prize. So he gets... Please give me anything. Yeah, I still think you have to make a case for your boss cause it's like you're studying, like you're basically your research is cloud native. So it's like, that's the conference. Yeah, yeah. Give me the number, I'll call your boss. Yeah. Okay. Well, thanks everyone. And then... Yeah, thank you. Talk to you soon. Thank you. Take care. Bye. Thank you.