 Okay, then let's get started. Okay, so welcome everyone. We now are as you know we're recording as well so for everyone who's not going to be joining today live, you can all watch it. I'll watch the recording later. So quick reminder this is a CNCS CNCF meeting so please attend to the CNCF code of conduct which basically means be respectful and kind to each other. Not too difficult I think. Okay, quick update on the glossary. So I think I mentioned that before we are working on a glossary marketing plan with the CNCF. And the goal is to have more members media analysts to use it in their own material right kind of like seeing like okay we have these vendor neutral definitions there and whenever we're referring to that they should at least kind of look at glossary and see if that's a good point. We're also kind of talking about a cloud native learning journey page, which will be something where all the different cloud native resources will be like right now you have all these things in different places when you want to so it's like really difficult if you want to learn about cloud native. You have to find them there's no one place so we want to put it all together. Start with the easiest right like the thing. Like, first of all will come like a very easy. What is cloud native. The second one will probably be the glossary. Then, I don't know we have several things that we have to build like have to add there like the cloud native landscape guide and so on and it will get increasingly advanced. So there is something for every, and it will be clear what is one on one to two and so on so I think that will be really helpful, and it will also help visit the game visibility for all assets. Again, so last time we were talking about how we would love for the different teams to talk about the glossary, the own project in their own regions and I've seen that the Korean team and the Italian team have at least like created their localized, or their own deck in the localized folder. And I was wondering if, yeah, do you have any concrete ideas already or was it something that was like just just to get started. As for the Italian team, we just started. We haven't spent much time yet. We will focus on it over the next two weeks probably. So maybe on the next meeting we'll be able to tell you something more. Yeah, do you have any, did you, did you find any, because one of the things like finding opportunities to submit this, because I think that's probably the more. Yeah, yeah. I think we are thinking about case the Italy, it will be in November. Oh, that would be awesome. So, so that could be a first, a first opportunity. We have to think about presenting it within different companies, for example, we have, we are six contributors from different companies so begin from our own company could be a start. Yeah, yeah, awesome. Yeah, not more than that sorry. Not at all, I mean like that was just a month ago that we put it out there and it's like again like the first, you cannot present anywhere if there is no like opportunity you have, but I don't know so it's great that KCD Italy is still like available to open. It's like once it like what it's closed you have to wait for a whole full year right so I don't think there's a KCD Korea yet right. Maybe team though. One more thing. Yeah, and yeah so I assume the same for for you. So go and she won't write like still. Yeah, actually, we also created our Korean version. And we actually utilize this presentation to contribution academy in posted by Korean Korean government agency. We introduced this material to around 20 mantis. Actually, June and I are mentor of the program. So we already introduced it. Since the club native of glossary project to them, and also the Korean localization. So it is the first version of the introduction for Korean folks, regarding the our project. Awesome. Cool cool. And again as a reminder so there is a promo kit folder link here that should be accessible to anyone that has the deck. We also have are trying to keep the localized decks in there so other people can see them so you know like if other people have good ideas or whatever. So we want to share as much as possible. I also started a social media because I forgot that I was going to do this and I started this morning. And but feel free of anyone I know and at least as also in marketing so if you have any ideas, because I think like two things that we want to. And again this is for the teams to like you personally to promote on your social media account to you know, your network. And I think there are two goals one is like getting like, so there are two kind of posts that we can do like one is like hey there is a glossary inquiry and check it out right so for people to and then another one is like hey, there is a team, we need some help right like two different things because we need both we need people to know about it to use it but also to contribute. And so again like whoever wants to contribute potential posts or ideas that they have or once you've posted them and you've seen like some got a lot of engagements is like oh maybe that's something that resonated like put it in there the more we have the better we can all share. Okay, I think that was from me so now is. Thanks so cool. Yeah, I hope to introduce new PR template. Previously, we didn't have PR template. Recently, in maintainers meeting, we have decided we decided to make new PR template so you can check the first link it is. And could you click the first three. Sorry. So it is PR template so you can open up here. Now you need to describe your changes in this PR and if they are there is related issue then you can put a related issue. And then the contributors need to check the checklist for opening up here. So we are regarding the. The originality of your work and the sign up procedure. As you recall, we, we applied this seal in our repository. So you needed to do signing off sign off for your commit. So it is about the checklist for this seal. So, yeah, that's all for the. This PR. PR template and maybe you can check the. It was an pleasure people are using this PR template. Yeah, I am. If you have any. If you find any investment point about regarding the PR template and you can open up here for the PR template as well. So, thank you. I think so. Yeah, we can move towards. Okay, cool. I'm sorry for the weird witness in a moment. Okay, so, next is overview that's also so far right you wanted to announce we have a new Spanish approval. Maybe a station team, since there is layer here, I think. No, that only that we have a new member on the team of the proper team. We are about seven writers and reviewers. And now we have a new approver that is Nicholas. In fact, there were two members that I wanted to, to gain as approvers. But we choose it Nicholas, because the other member was already an approver in order to complete this project so. But it's nice to have several people trying to get involved with trying to join in as a progress reviewer. So the team is working really really great. And regarding to status, we have 11 terms that are published, two terms that are having added in the last month, and we have three more in progress. Another good thing is that the blog post about our team was published in the 19th of August. So we got some some publicity for our team. So far, I think we don't have new members joining us writers but we are stable, we are using also the project board and so far is working really good for us. And we are applying the same thing to this Kubernetes documentation. Now we will be able to create also a project board for the team. Yeah, we are joining efforts between the Kubernetes documentation team and the glossary because at the end we are working on this smaller class the same things the same time the same concept so it's, it's nice to join forces across teams in Kubernetes community. And that's all regarding publicity probably we will do a talk about the glossary and another localization efforts in the cafe Spain that is also taking place in November. This is just after the Italy, because it is so I think it's the next week. So, yeah, trying to get the, the people to know that this is a project going on, how they can do how they can participate on contribute to this to the glossary to the this organization also to other CNCF projects like the security way paper that we are also localizing or the covenants and dashboard the interface that she's made a full with covenants. So here we have other people is back as finish spanish speakers trying to, to get these projects and a lot of projects on the CNCF in in their native language so I think it's working so far so good. Yeah, and I forgot to add about the blog post so that I will add in the yeah so a link to it so that people can see it as well. And I just thought like because we were talking about social media posts that is something else that we should use in social media over and over again right it's like hey join our team here is why whatever so instead of linking to the glossary so the blog post something that each team can use over and over again as a resource to learn what like why the. And especially because in the blog post there are some context of why it's important in your language so in those we had some history about why Spanish is is why they use it so it's a better entry point that just a random repository with a lot of features open so it's a more human way to start getting into a project. It's a lot more personal right so it's a very. So yeah and I love those blog posts because they always learn a ton. Okay, so French please stop. Yes. So first of all nice to meet you all. This is the first time I'm joining this meeting. Flavia was not able to attend today. So this is really the beginning of our journey. So we started to do a couple of. But only a couple because we really really want to review them all together so that we can be aligned on some terms and do we need to translate this one on and this kind of stuff. So that's what we did. We hope that we'll be able to integrate them and to merge them by the end of the week. And after that, we will continue so we really hope to be able to have the first batch of 10 words that needs to be translated for the forgoing live by the end of the month. So, yeah, we will try to do that. Let's hope we'll be able to. That's exciting. I saw the case of the France for next year would they bake. Yeah, yeah, it will. But yeah, yeah, I know them but actually I'm not living in France anymore. I'm living in Montreal in Canada. So, yeah, I know them. But I don't think I will be able to attend this one, but just before COVID we were planning to have a KCD here in Montreal. So, I think we will resume that quite soon. But right now I think most of the things are a bit under the ice on the ice because on the ice because of the cloud Cuban coupon, which is arriving quite fast here in Detroit. So, most of the effort will be going towards that. And I think we will resume that right after. Yeah, and so you said we are different. Oops, sorry, good. No, no, it's okay. But we are really close to the, let's say the Cuban it is a local community. I'm quite a lot. I was involved in the KCD that we are selling to do in before the COVID. So, we definitely plan to have something related to the glossary as soon as we have published something. Awesome. And I know that something that you discussed because Flavien told me that this is something that you have discussed in the past that it would be great to be present on meetup and stuff like that. So, definitely this is something that we will do. Yeah, but yeah, again, like, still don't don't stress too much about the, it's a lot of work so don't worry. We want to know. Yeah, yeah, yeah, yeah, I know. You know, but excited to have you on board. And one question maybe how, how did you end up joining the glossary meeting, the glossary, not the meeting glossary. The glossary. So, basically, I'm, I've been really involved in the open source community for a very long time. I've been the leader of the French open to community for six years, and stuff like that. And I've always had the translation in my mind. I did quite a lot of something that that's always I started to enter in the community. And I did that for the last 20 years. And I saw and I'm part of my job is doing some kind of technical curation for my team, team workers. And I'm, I saw, I don't remember which one, maybe it was the Korean glossary that went live. And I talked to Flavien and Ludovic and told them, okay, I saw that there's a team that we need to start a team to do that. There is no, nothing going on for the French one. So, let's do that. Awesome. Yeah, Ludovic and Flavien and myself, we were, we used to work in the same company in France. So, yeah, and with Flavien, we still work in the same company here in Canada. Okay. Oh, yeah. Well, yeah, excited to see the French glossary coming to life. Yeah. Yes, yes, yes. I think I really think it would be great. Yeah. I don't think we have anyone from Team Hindi here, do we? No. No. You can see it there, 15 live, five new terms and 12 work in progress. Okay, let's move to Italian and Lisa. Hello. Wow. We managed to translate localized 10 new terms that currently on review and some of them are accepted, but waiting for merging. The new terms are actually in progress and we counted 35 terms out of the total 73, 73 terms of the English repo of the English as per now. At the beginning of August, they were 33, 73. We are a bit struggling because the team was made up of six contributors. One person is still in sick leave, unfortunately, one is paternity leave, one is on holiday for one month, so we will see how to catch up and speed up because our goal is to complete the glossary by Detroit, by the KubeCon, Yeah, we decided to have that goal so that we will do our best effort, we will do our best, but at least we have an ambitious goal. Yeah, it is very ambitious, so don't stress about it because as I said, like we want you to stay and not burn out and then say like, I don't want to. I'm not stressing the point is that in these days, only three of us are working on it, and I'm struggling with the technical workflows and everything so I'm slowing down the team. Otherwise, the other two are translating to three terms per week, so they are Yeah, yeah, yes. I think we need to understand as a team how to keep up with updated translations. I mean, I'm talking about the source language, because if English gets updated, we need to try to understand how to trace it, how to monitor it, and how to define your recovery terms. Yeah, I know I saw it. I saw it, but I'm not sure I can understand that so I need someone, not the team that takes on charge. That kind of issue. But again, we'll see. And that's okay. Yeah, that's a lot. That's awesome. Yeah. Great plans. Yeah. Nice to go. Yeah, yeah. Korean team should follow. And Korean does follow. Who wants to do the Korean part. Yeah, maybe you can introduce. Can you go. Okay, I will start. So I'm very glad to join this meeting. And actually, this is my second time to this meeting, but I'm still a little nervous. Anyway, let me start. Since the last meeting, we have localized five more terms and we have, like, nine terms are working in progress. And as you know, we share and check our localization progress in the discussion. You can see our progress in the discussion. And eight new contributors have participated since the last meeting. And also the. We have planned. We have a plan to merge the Dabco branch into main branch. Maybe this Sunday. Maybe that's all. Thank you. Awesome. Okay, and Spanish we've done already so. Any. Sorry. Don't be nervous. I was talking to Duncan. Oh, yeah, not at all. Oh, thank you. Thank you so much. Yeah, any discussion points or anything that you have that you didn't put on the agenda or. Okay, cool. Then we don't have to make this longer than it is. I know the people in Korea want to go to bed. So thanks again to you for the most present team and the latest. Okay, well thanks everyone. And we'll talk to you in a month, I guess. Sure. Thank you. Bye bye.