 Okay, welcome everyone to the glossary meeting as a quick reminder, since you have meetings so please, yeah, follow the code of conduct, basically be kind to each other. Exciting news that German glossary is live so we have to representatives here. Yeah, finally, I know it takes a long time, especially since Noah is not only working on the German version but also on the English version so double work, double work and double kudos, I guess. A quick update from Q. Q&A so we had lightning talk. I mentioned that in another meeting but not here I think. So the glossary stickers were gone on day one, which was amazing. Again, I think it's just because they were smaller versions than the big ones of the CNCF I think people got confused and thought that was the regular ones but it's cool because if people stick them on their computer suddenly they will realize oh this is actually not the CNCF regular glossary sticker it's a glossary maybe they can check it out. So definitely want to ask them to do that moving forward because I think it's like cheap and it is a way to discover it. And then for KubeCon EU we resubmitted or with we I mean Noah resubmitted the panel discussion which is like focused on the localization part of his story like and with different representative of different groups. We also submitted a panel discussion. I submitted one with another group about CNCF resources in general they include the glossary. So it's not only about the glossary but there are many more so we want to kind of raise awareness of that. Then Noah also submitted a talk it's not about the glossary but it's about contributing and like how a part of it will also be about non code contributions and I guess the glossary would get a call out. I expect that now it's efficient. I plan to do that as well at the end to give some yeah some little hints that is a glossary. And yeah and time to sorry you forgot that so that's another thing like if anyone has it doesn't have to be 100% glossary. Right like if there is like an angle or something and happy to help with that as well. I mean, just, I mean there's not enough to talk about the glossary to make a whole session about it right so, but like if we can weave it in in different different ways. That would be great right because it would be good for people to kind of hear about it. So, I'm really hoping that the tag will come soon we've been talking about that back and forth. The designer of the CNCF kind of created mock ups. So you've seen tags before but they were not. It was always a half implemented thing so I was really like uncomfortable with them be I would wish they were not live yet but it was like this half big thing that was life. They will be up here so people can filter by tags if they want to, and then here you can see it and go back to the different options so hopefully we can implement that soon we think it will work well. And then if not we can always adjust at least that's what we hope. We also have like a little sheet with the maintainers where we are updating the tax for each term because we want them to be meaningful. I've seen at some point people were just adding whatever like application like anything can be application because it's all related to applications. Right, so then it's not useful anymore right so it's like being a little bit more, more. I think it a little bit through so it makes really sense to have those so they're meaningful and then once we have that I think we're through now we have to kind of update those provide a little guidance and contributing docs. So that's everything I had, which is why I was saying at the beginning, it's probably going to be a short meeting. Anything else from Noah and I saw G horn is here as well. General, I guess. Yes, I think one question from myself like there is, you know, like there's a local case to the events happening all the time. We tried to encouraging some people from the glossary to go to talk about those conferences right like I see there's a case to the Berlin conference happening this year. So we can love it those avenues to talk about the last year because these are the local events. Yeah. Yeah, so we actually have, I think it's pinned in the glossary channel. We have like, it's not super comprehensive but the idea is that it gets better we have, I think, how did we call it like grocery promocate or something. So you'll find the deck that I did for the glossary, then we have like one that's more. So we're trying to put things in there so people can be purpose them. So in our goal like in a previous meeting that was before you joined time. We were actually encouraging people right to exactly to talk at especially if you are. If you live in a place that has a KCD to submit their coupon is just one event it's big and very competitive. I think it's much more effective specifically to get people to use and contribute to the localization effort. These KCDs are so much better so yes like if that's something we should submit and again like we are happy to provide as much or little help as needed right like it's good for everyone. So, yeah, where did you say is that KCD. I just think like there's a German language is going to be polite like Chinese language and Korean language. And these are events happening like KCD and we try to even we can give a template to the people so they can use it for the CFP because you know it's a tough task for the people to buy the CFP because they haven't done it before. So we can prepare some small template for the people to use it for the submissions. I think the abstract is in there too. So I think so yeah, because that's the idea we want to make it as easy as possible so people just have to translate it. Yes, yes. So in the glossary side like we're not able to like the reason I'm trying to go today as well is like, there is a, there's a commonality is winding up everything, especially in the supply chain security part. So we plan to add those in the glossary or in the future or in the road, specifically for the security domain. I don't know, like I'm hearing you very weird. Is that just me or it's like. Something is going to be on my. You were fine before. Like a robot. Yeah, it's fixed now. It was like struggling to listen to here. Yeah, just saying like in the glossary, we have terminologies in the security side, especially in the supply chain security side. We plan to add those in because these are so much of the observation behind abbreviation behind it supply chain security salsa, because now I believe, do we create another one or are these a part of the same glossary that I'm thinking about this moment of time. So the glossary is really kind of, it's a cloud native glossary so we kind of restricted to cloud native terms, and we have had to reject some terms because they were not. We have to say at some point, yes or no. So it's, yeah it doesn't really. It's like that feels like it could be another glossary. Right. Yeah, because otherwise it gets a little messy as well so we're like focusing on things that aren't cloud native or terms that are needed to understand cloud native right if a term is needed is like, you kind of the basis of a lot of definitions and not everyone might know it we, we will, we include that as fundamental right even if they're not cloud native so that's kind of the rule that we've had. Yes, absolutely. I see like there's some open assessor foundations are coming up so they might add same things in their glossary as well, but I get your point absolutely. Another thing I just talked to Chris from the Linux Foundation. So, then we might need to have some localization for the certification exam as well. So is there a working group for that in the CNCF or we click dolls happening when do you know anyone from the CNCF like for the certification side. No, but I'm sure they're like always looking for. Yes, I'm sure they're looking for someone that would be happy to have someone who leads that effort or kind of at least kind of gets it started. But yeah, I don't know. Anything else before we get into two teams that we have here. Okay. So Noah, David, the floor is yours for the, for the quick. Yeah, so yeah German content is live that's what we already heard. We're going to see that on the page finally. Then we have a new reviewer which is who is Boris. He couldn't join today because he has a meeting but he was constantly making efforts to help us to get the content ready. So we continue continuing working on locally on localizing the other terms. So we have two PRs that are open right now. And what I'm thinking of since since a longer time period now is to somehow approach the Kubernetes localization teams as well. Somehow, I had the idea back then already and now that I'm involved with the 166 CLI. We recognize that there's also localization issues regarding the CLI commands. And yeah, so I plan somehow to, to approach the folks from Kubernetes localization and maybe, yeah, convince them to help us or help them or somehow somehow connect with them and see how we can we could potentially work together. Great like the Spanish team where it's basically the same team. They're kind of merged together and like yeah. So maybe you can recruit some people over and then. Yeah, I hope so. But I have to fear that there's no much people for localization because at first, as I quickly did the research. I couldn't find anyone responsible at all. So yeah, I will have to do my research. Yeah. Okay, and then we're do time. Yes, absolutely. So there's a basic is up students. I am actually working with them. I'm delivering a course in this university called fast Islamabad. This course is up to an end. So these people are based these students are basically are responsible for doing these kind of activity but I want to have some student contribution in place because this is their part they need to understand what the glossary is what the pages are because I am I am already familiar with these terminologies. So they are basically taking every step in the way and so I'm actually helping them. So they have submit I think they translated 10 pages and they have submitted a five of them on the marginal PR but when I translated there's some issues in there. They reviewed what they have done so far. I've actually come out like this or do is translated that you have is adding issues in it because you know when you're translating language to the different language that means something different to the different people. So the context is stays the same. So actually the context is not working as I expected to be so they basically working on behind the scene as well. And also in the university there are some professors professors who work who knows who do very well and who have written books on top of who do and converting some English language to those. So I'm helping them. I'm they're actually helping us out because this is like some of the terminologies like let's say Kubernetes ingress Gateway API. So do we translate this into the Urdu. So do we make it ingress Gateway API, but we need to give us some user perspective, what it means in your tool in bracket like we can do it. So there are some limitations as of in Urdu right now. So they're basically working on that but they have done translated some good numbers and they're Muslim PR, but I want to have some more time so when it's going to be live. I can read and educate about it because right now when I'm reading this. I'm not getting the contest out of it. So, so I actually restricted to not make it in the production unless we come up with a good context. Yeah, it's better not. I mean it's better to take it in especially I think it's kind of exciting because basically you are potentially or the team is potentially coming up with how these terms will be called in order because it's like, pretty new people are using these terms like, it's like, is there, should there be like an order term for it and if so you will be able to kind of frame that and people will be using that for maybe decades right so that's kind of exciting. Yeah, in a very cool place and then yeah you should not rush that for sure because if you wanted to work and people to actually adopt and use those terms. It needs to be good and takes time. That's all that was on here. So, as mentioned, short meeting today. Unless there is anything else. I would say we're, we got some time back. Then we will be meeting again next year. Yeah, because it's, it's December right yeah. Oh, we probably have to move that meeting or so yeah. Yeah, so have a great end of the year. I guess. Yeah, likewise. Yeah. Yeah. Cool. Okay, well thanks everyone for joining. Thank you. Bye bye. Take care. Bye.