 Okay, I think that we can get started. So, as a reminder, this is a CNCF meeting so we want to adhere to the CNCF code of conduct which means basically to be respectful and kind to each other. So moving to the glossary updates. Let me share my screen. So, things are moving weirdly right now. Okay. KubeCon. So, KubeCon is coming up very fast, just three weeks I think. So, the lightning talk, which I will be holding and I'm kind of excited to CNCF is trying to promote a little bit because we're saying I mean it's basically the lightning talk is a pitch about the glossary why you should use it why it's important right and I think this will help raise awareness normally. I think in the last one there were like about 1000 people were in the room, they're not coming specifically to hear your lightning talk they're coming to hear the lightning talk so it's a great way to discover things right. So hopefully that will work. I also added a link to the deck here. Because, yeah, like in case you want to do this in your KCDs or anything I think it's like, I mean it's just I think lightning talks are really great because it's just like a five minute pitch. You know, there is not a lot to say it's just like it's here. But one thing it's there feels free to repurpose that it isn't that glossary folder, which is linked in our channel as well. And I was also trying to reach out or I want to reach out to KCD organize in different regions and just ask them hey, are you interested in having someone, we're not going to travel to, there is no one from our team we're going to travel to a different country to do a quick talk but maybe they're interested if they're excited about the topic and it's really easy because it's not very technical, or not technical at all. So, trying to see if we get people in different in these local communities to spread the word as well. The glossary marketing side. I had an idea and I hope I kind of like it sounds like we may be able to do that. And it's adding like, I'm calling it an ad but it's like a little banner about the glossary in CNCF material for instance, the CNCF annual report is coming out. It's really handy because people are reading this report. Maybe people are not really familiar with all terms. So it's really relevant people are reading the report may want to have like a glossary handy right so it's like. So, that could be another channel to raise awareness as well. And the CNCF said that they wanted to include it in material for analysts whenever they kind of have like, I don't know they sent them stuff occasionally I don't know exactly what it is and so on. So they wanted to include that I was also thinking to create a little pitch with the keep points to make it really easy. Yeah, that's everything that's going on and marketing. Yeah, I don't know how far on the tags it's moving slowly mainly because of me I'm kind of a blocker because I need to create like a new mock up. But basically I've seen that we've been so yeah, the tags are we're not using the tags the way we should use them right now. But the idea is to be really minimalistic have like just one, like, like the most important tag and so on because like if you add a bunch of them it gets like, I don't know, it loses its value but we have to implement that and then create some guidance so we have the tags right it's like oh it applies to several things somehow right but it's all kind of cloud native related. So, yeah, hoping to be able to do that mock up next week. And, oh yeah and also lightning talk on the same topic today at keep crash and our conference that we're putting together with some open source companies. So yeah really trying to do use it wherever we can so feel free to do the same. If in your local and respective communities. I think this was so who added that like two new terms, I guess. Yeah, which is great. I'm happy with both of them. And then I think to whom were you going to talk about the some order process progress or is it just like, we have a new team I guess. And I don't want to distract you from driving. And if you're talking your mute. Let's let's leave to you and driving. Okay, we have our new localization team. Let's see, I guess. When you can check it out. Yeah, oh it's done. So that's exciting so we have French and or do I think that are working on going live. So people have added their updates here. So Bengali 12 terms. I don't know what that means. Oh our. Okay just are so we have to they have new two contributors. Great. So that seems to be moving forward. Noah. So we have nine terms ready by now, which is pretty cool. And two PRs are open and also bar is joined as a pretty active member, which is also very great because it's hard to find members who remain active. It's always good news. So, update from team Hindi, eight new terms, waiting for two more to open up PR and merge 11 open PRs. I know, my weekly steps updates on the channel. I know. And Italian I know Annalisa wrote this, but couldn't join. So 16 open PRs 15 terms. 13 published already. And 28 in ready in depth. That's pretty cool. Oh and I did like this little video that they were talking about which is very useful. Only in Italian but maybe we can translate that at some point. And for the Korean team. The glossary is life, which is really exciting. If you haven't checked it out, check it out. I learned a lot about Korean language. So, pretty cool. And then we have Portuguese. So, we have nine new definitions that are in life. I spent some time to rebase the bank the branch because it was a lot of conflicts to fix but right now everything it's working. And we have the tags. We have only one PR in review. In the last weeks I was working in a guide for the maintainers, the localization maintainers so just with some process with some responsibilities that we need to take as a localization maintainer. I was working on that because most of the job was done by me so I'm trying to separate the test between the reviews and approvers. So, I create a draft and right now I'm validating with the team. And we started to do, I think, last month a bi-weekly meeting with the team like a off-the-hours just to answer a question to help everyone that are trying to, that have interest to work on this project. And yesterday I sent the blog post from Catherine finally. We finished that and I think that is it from the Portuguese team. Awesome. And that guide I assume it's in Portuguese, right? Yeah, yeah, yeah. I think this could be something to share with. That's something that other teams could benefit as well. I mean, like, you know, figure it out like write it, you know, make sure it works. And at some point maybe kind of share it with. I can do a short summary and I will send a message on the glossary channel just with the sections and sure, I can share it. I mean, always good to share best practices that different teams have identified. And then the Spanish team was not able, they said they were not able to attend. Victor, of course, is in California, so it's far too early, but he added some terms here. 13 terms added in the deaf branch, two pairs open, six issues in progress, ready to emerge into the main to go live. And they did present at a workshop and there is a link to it. So that's really cool. Because, yeah, again, we really want to raise awareness as well. Among different language communities to to to recruit more helpers. And there's a new approver, Nicholas. That's it. And then topics Noah you had a topic about. And what is what is, yeah. Yeah, so I recognize as I was localizing one, one term that I, I couldn't remember which tags are available. So, I think we need to to list them somewhere. Yeah. Yeah, we need to get. That's why we're saying like ignore the tags for now a little bit because it's like some of them are. But yeah, I can maybe post them in the channel we have to, because we have to implement the changes so the tags work the way we want them to work and then we have to update the contributor. Yeah, I don't like when we did push it before we had it figured out, because it took a while figuring it out so it was probably not ideal. Yeah, this is something that we should probably do as postponed to the tags implementation of the website. So after the implementation is done we should list the text somewhere. Yeah, and we have to go through all of them and make sure that the tags are because some people have a high tags and it's like that. Yeah, so. A lot of things would not, it's not, yeah, but it's not the way it's supposed to work. What were you saying, sorry. Yeah, and the other thing is that I recognize that we didn't add the links of the recordings to any of the meeting notes, which recording the recording of this. Oh, yeah it says watch the recording here but there's no thing. Oh, I don't know. I don't know where we can, where we can grab them from. It is. Yeah, I think last time we had to remind Libby. She does it at some point. And then it's on the CNCF channel. Because there's so much going out that you have to kind of make so we have to look out whenever that is live, but I can send her a note and ask, can you let us know when it's live and then we can do that. Cool. Anything else. Okay. Thank you for joining, but that's fine. I feel like it's a little kind of like there was lagging somewhere, at least for me, I've been really distracted with other things, but hopefully. KubeCon is always distracted. But yeah, well then let's leave it here. Thanks for joining everyone. And we're in touch in the glossary channel if there are any questions and otherwise we'll see you next month. Thank you. Take care. Bye.