 recording that we can share as well. So let's just start the official time. Like, no, okay, so welcome to the glossary meeting. A few glossary updates. Nate, the CNCF deaf advocate will help with technical reviews. And we've been talking or I've mentioned the cloud native learning journey for a while, because we've been like, gathering ideas, basically, I have all these different resources in one spot, like all CNCF resources, right? Like starting with stuff that is very basic, and then like going with more advanced and advanced. So we have developer assigned, which is the same as for the Chris Abraham, the same person who does the glossary page. So we're working on that. So that like actually kind of is kicking off. And the goal is to have that live by KubeCon. And then have the CNCF push it out. And yeah, just so people can discover different resources, including the glossary. And Seoko, are you all his audio is connecting? Can you hear us now, Seoko? Oh, yeah, thanks. I can hear you. You are somewhere outside. Yes, right. I have difficulty in connecting to zoom meeting in mobile phone. Oh, okay, okay. Do you want to do your section? Do you want to talk? Do you want to talk through your section? Sorry, Al. I can put this. I'm not sure. I am actually using my mobile phone. So I'm not sure. Can you see this? Sure, I can. I can check. So you already talked about the glossary update, right? Yes. Yes. So we're now here. Yeah, I just want to show some mOSPR in Okay, so what is it in South Korea? Oh, yeah, it's kind of the night sight in Seoul, Korea. I'm sorry, very sorry to late this meeting. Yeah. So I actually hope to share that some latest update in localization related issues. I hope to share that there is a new localization initiative from Japanese. So we already included Japanese members. Can you hear me? Yes, yes. Can you hear me? Yeah, sorry, it is outside. So I'm very sorry. No worries. So we already initiated the Japanese and we are we already created the Japanese Development Branch and they already opened initial PR for initiating their first to compute configuring their localization branch. So maybe after we approval a PR that needs to need maintenance approval, then they can start their translation job. So I'm going to ask you maintainers to approve that Japanese configurations here. Yeah, that's that I want to share the first topic. And second one is actually about the some configuration changes regarding the Chinese content. As you know, we got the traditional Chinese localization team. And there has been the simplified the Chinese team already. We already have. And between them, we need to some coordination between them. Actually, the traditional Chinese, majorly used by Taiwan people. And the traditional, I mean, simplified the Chinese used by the mandarin and mainland Chinese. So somehow we need to coordinate them. And my proposal is that the we have to change the context to original context to Chinese to into the simplified Chinese. And I'm sorry, it is kind of Korean musical was funny. Yeah, so I'd like to suggest to change the current Chinese content into the simplified the Chinese content. And we already added the traditional Chinese spoken to the mainly by high faith. Yeah, yeah, actually, I yeah, no, why did you see that discussion at all? I think we already discussed. Yeah. Yeah, I don't know. Yeah, I didn't know about that. But I mean, sounds sounds like a fair approach to do. I mean, yeah, I like I learned I didn't know there was like simplified and traditional. Yeah, that's crazy. Just knew like that we had Chinese and was like, Okay, now the Taiwanese are doing something. And they also speak Chinese. Like, okay, like something needs, you kind of just say Chinese, right? And so apparently, yeah, I thought it was really interesting, which you can see here, this is much more complex, right? Like, there's much more. So this is like a simplified version. And they use the more traditional version. So I was like, Oh, this is so cool. Like learning. I had no idea because it's like, yeah, it's interesting. It's not a phonetic language, right? So it's like, this is just the same thing. But in a simplified version. And I was like, when you look at it, you're like, Oh, yeah, this is so much complex. So much more, you know, so yeah. And then like, we came to the discussion was like, Okay, what is the actual way to kind of differentiate between the writing styles? And so that was a interesting, because we didn't think about that when the first team came on, right? And we want to make sure that we accommodate different, different countries with different versions and different. Yeah, who use like, yeah, different writing styles, like to be sure that we can accommodate all of these if you want to have them eventually. Anyways, I thought it was interesting. So I learned a lot. Sorry, so yeah, I just want to say that it is the based on our discussions between other localization groups, as your address, glossary maintainers, we didn't just decide we consulted with the localization experts, including the simplified Chinese as well as the traditional Chinese is the main point. Maybe this decision is maybe very useful to other localization communities. Is there any opinion or question regarding on that? Yeah, thanks. Actually, we already decided this matter, and we are going to change some content regarding the existing just Chinese content into the simplified Chinese so that you can accommodate both simplified and traditional one as well. So we are going to do that. Actually, I hope to see folks who are maintaining co-maintaining Chinese, but I don't see in current meeting. So maybe we have to post this message to like again. Anyway, I have to go to the next content. I'd like to share that we actually have to keep localization members have to keep update this TOML file, which can convert to the localization content based on some variables that can use the frequently. So if we change English content in TOML file, it should be applied to localization content address. So recently, we added this some UI, GUI, regarding the, you cannot see, but our sensibly related content in English. So localization members should check the TOML file, and they have to make their own their versions TOML file. Yep. As you, Catherine showed the link. Yeah, we added new TOML file content. The section should be localized for all localization content. So I hope to share it, but I guess currently, people who are joining this meeting are English and the overall maintainers. So let me share this message to localization channel. Sorry, there are lots of my colleagues here. Yeah, your colleagues. Now you have to tell us where you, why you're there, and what are you doing? And what we're stealing you from? Yes, some of them know some ladies. Yeah, I will introduce you later. Actually, really exporting using private cloud and public cloud in just usual cloud manner or cloud native manner as well. So maybe I hope to invite some of these men members to contribute to this localization effort, or our glossary effort as well. That would be great. Yes, I covered the third item and first, the last item is about the workflow to report outdated content in localization content. As we as we know, there are many several localization branches. And since the main branch English content keep changing, we need to keep update the localization branches as well. And it is not easy. And in case of Korean localization team, we, we already have a experimental workflow. And actually, it is contributed by majorly contributed by Yun Gong Kim, who is active maintainer of Korean localization content. He he introduced the workflow GitHub action that automate the difference checking the difference between English content and localization content and making a report for using an issue. So you can check the link I provide. Yeah, should do you want me to click on it now or just like for Oh, yeah, yeah, sure. Since we have three of here. I'm not sure why. Sometimes it's like, no, this is a four or four. That's weird. Yep. Catherine, you can you can just check the link and yeah, yeah, that that link is also case. Yeah, yep. Yeah, you say it is issue. And it is kind of a report. And Korean localization team tried to check the changes during Korean localization job. Regarding the English content. So we checked the changes in English. And we found four files has been changed during our localization job. So based on this report, we can check which content should be changed before Korea. Okay, that is that is really good. I mean, it looks that this can be automated. It's kind of crazy. So I know it's great to capture them here. But we were we were kind of thinking of creating a page on the glossary like in the docs or something where we can capture all these workflows. So there's one place like no one will go through. I mean, if it's here, it's going to be lost at some point, right? We want to make sure that the are these things are all captured somewhere where people can go and find them all together and not search for them within an agenda. So we're because we were talking about it, right, to create like, I don't know, we have, or it doesn't have to be here, it can actually be in the because we have a localization, right? Section? Right, actually, it is kind of automated feature provided by GitHub. And based on GitHub functionalities, we made workflow effective to Korean only. But once Korean team think it is very beneficial for, for all localization teams globally, yeah, then we will keep share how it works and how to apply it. Then I think it is very beneficial to other localization teams who are struggling struggling in the update English content to their localized contents. Yeah, I mean, it's a question that comes over and over again. So if you figured a good workflow, we have to put it prominently somewhere on the localization doc so people can find them. Okay, so if you say you want to test it first and kind of be sure that it works, that's great. But let's not forget to because to add it, right? Okay, cool. Sure. Thank you. And I would like to say that it is not perfect. It cannot be perfect, actually. It is based on my experience in Kubernetes technical documentation localization. Since after the four years, it is not perfect. But you have to keep update. We means the Korean localization team hope to collaborate and keep update. And actually, we need more collaborations from other localization teams. I hope to mention that. Okay, yeah. And I mean, none of these things are always but it's like, we don't like a huge help, right? It doesn't have to be perfect before it's like how like there was no way of actually seeing this. So that's good. And that's kind of maybe like put a call to action in the localizations channel as well, like for other teams to help with that. Sure. Okay. Okay, that next site. Yeah, I can we can go to the next item, localization of team update. Yeah. So the Italian team wrote here that it would be nice to have an automation that creates a new issue for localization teams every time a new term is merged in the English French. That kind of goes into the same direction. But I guess like it's not a change, right? Could it also include new things, new terms, like your workflow? Yeah, I think it is another way to keep updated. Localization branches or localization content. Yeah, if we keep changing the English content, localization team may not have to keep follow the changes and apply those changes. So I think it is requested on the based on that situation. But I'm currently I'm not sure the changes in English content is not that frequent. Am I am am I right? Yeah, like there are not that many new terms merged. Yeah. Yeah, especially the not new terms but the change of the terms. Yeah. Yeah, we're not like we wanted to like a review of all of them, but I like we haven't even started with them. So maybe we can balance. Whenever we have changes, something and making our issue opening issue is not good for maintenance. Since we have to keep trace the changes. Yeah. So maybe we have some consensus on the trade off in this manner. Since we the people participate in this meeting is maintainers. Maybe another way is to creating a new label for localization. So that if we make lots of changes in terms of where we make a new term in English, then you can put new label localization. So that other localization teams keep checking the new changes or new terms. Yeah, how about that? Yeah, so that's on us to remember to do that. The same thing would be with a new with a new term, right, a completely new term we could remember to post something in the channel as well, right, like more or do like and do an issue. We just have to remember what I kind of don't understand is if the solution that you were talking about circle that you already have, and you have to test it, if it can detect both the changes and the new stuff. Yeah, actually, the report that shows outdated content in localized content. Okay, it's just about the already translated or localized content only. So if we say there are, I'm not sure, 30 English terms, and Korean localization team translated 15. And we keep checking the differences within the 15 Korean localized contents, whether the related 15 English contents have been changed. Yeah, if we didn't translate it, we don't need to care actually. Yeah, is it understandable? Yeah, I got it. So so so this this concern that is had and people brought up would not be would not be catched by that solution. So we maybe would have to think about such an automation, right? Sure, actually, I think in case of a Korean localization team, we tried to make a workflow that automate checking the outdated content. But the other localization teams don't. So in case of Italian localization team, think if we keep changing, if we're making us some changes in English content, then they think our why English terms keep changing and how to apply and how to sense the change this content. So the reason why I suggested to making a new label localization is that I would like to announce the localization home maintainers can check major changes in English terms so that they can handle the differences. Yeah, yeah, sure. But I guess for them, it's it's more for I mean, when I get it right, they are talking about new terms. So they want to get notified whenever a new English term comes up so that they can also probably create a task to localize it in their language. I think but like we can do the same thing, you know, like we could like create a label for major updates and then like the same because it's like that's something like because we're sure. Yeah, of course, I mean, I like the idea. Yeah. And then an issue with new terms, right? And say like, attention, localization team, new term, whatever, and then yeah, okay, okay. So both are big changes, right? So yeah, I mean, I mean, in the very end, it doesn't really matter from automation point of view, if we create the label or or a new issue. While I'm a huge fan of creating labels, then issues to be honest. But yeah, I guess we, because this topic is already showing up since a long time period, I guess, maybe always in different kind of shapes. But yeah, I guess, I guess we should investigate a little bit. Sure. No, we have to investigate and keep saying that it is the workflow from South Korean is not perfect. And the supportive way is making a localization label so that provide, we can just put the localization label or actually repector label to the PRs that changes English content a lot. Yeah, I think it is both ways. So yeah, in case of Noah, you care about the cross story, overall, as well as the German localization. So if you are the co maintainer of localization for Germany, then maybe you can check the that report repectoring or localization label to keep up to date your German content. But maybe maybe sometimes later, if Korean localization team or Brazilian team have make new best practice to update the changes in English content, then maybe you try to follow our in-apps. Is it acceptable? Yeah, yeah, I try to I try to catch up if I got everything right. So your suggestion is to introduce the refectoring label, for example, and that we apply it to pull requests that would imply changes on the English term. No, it's the other way around, right? So every time Yeah, I have Yeah, maybe it could be issue or PR. Okay, maybe changes suggested by majorly by PR. So if we change some thumb in English, then and we maintenance maybe think it is too much changes, then maintenance or localization maintenance can put that kind of localization label or localization repector so that other members who maintaining localization can check and check. Yeah, it is just my idea. Yeah, I'm fine. I'm fine with that idea. We should just write it somewhere. So what what what we kind of agreed on. So again, to sum it up. So whenever we have a pull request that changes in English term, we add localization refactoring label or what? And then every localization like leads or team members can check if if they need to update their localized term, right? Yeah, I think it should be the if there is lots of changes not the simple change. Yeah, typo. Yeah, yeah, yeah, major, major changes. Like stateless application and you know, which are now going to be a concept. Yeah, yeah, yeah. Okay, I'm cool with that. You're honest. Yeah. Yeah, yeah, actually, I need some feedback from localization core maintainers or approvals. But yeah, I'm going to share this matter to select channel as well. So that others can provide any feedback from on on this issue. Yeah, that would be cool. And then we can maybe like bring it just bring it up in the next meeting again and and see what the feedback was and then we can kind of Okay, I will I will bring it to the next two meeting as well. Thank you. Okay. Okay, then I guess it's it's it's time to to give an update about the German localization. So I guess the blog is finished. We have all the content, right? And Thank you. We'll be published tomorrow. I think they sent June first. Awesome. Oh, tomorrow. Yeah. Nice. Very cool. Nice. We have 13 terms. But I checked that only 11 are online. We I just need to to do a rebase and to get to to to merge the we need to merge the branch with the main branch to update everything. We have three terms in review at the moment. And we have one new active kind of active person. And it would be cool if we we can manage to to keep that person in the team. Yeah. So that's basically basically yeah, that's always good news. But it's it's it's hard to kind of keep the momentum. But yeah, but you see, it's like always waves, right? Like a team is very active. And then they're completely dead. It's like, I don't know. Do you want to do the French as well since we don't have the French team here? Um, yeah, I mean, I can just read it. Yeah. Yeah, the French team has as well one new active person, which is kind of cool. And yeah, it's pretty similar to our team. The team is starting to be more active and have more exchanges. And the path to publish the first version has been shared and agreed between us. So apparently they have kind of agreed on a workflow, which is a good thing, I guess. And I think something that Christoph mentioned last time is they want to go live with a lot more than 10 words. Oh, oh, wow. Okay, that's cool. Because they came to the conclusion that 10, 10 terms is not really valuable, because it's like, in one term, you kind of link to another one. And they were saying, makes sense. Yeah. So they decided as well to kind of select terms that make sense together. So they kind of they didn't just do it like, at Hawk, which was kind of interesting, they had like a strategy. So I was like, Oh, interesting. So once they go live, it will actually be pretty solid. Like there will be a lot more to it, which is kind of cool. Round Robin, I would like to, I guess, I think, Soko, you put some KCD info in here. Yeah, sure. I'm preparing some talks to the Korean KCB, as well as Taiwanese, Taiwan's KCB. And I, I suggest to, to a small talk to KCB, Taiwan, and accepted. So I'm going to say about some strength of cloud native glossary efforts, as well as how to contribute non-contributions to cloud native in Taiwan, KCB. Also, I'm actually co-organizer of KCB Korean. Oh, nice. And it will happen in July. And I already have an appointment regarding Hengon for non-code contribution in cloud native. The content should be majorly in cloud native. Fig docs. But I hope to introduce regarding the glossary as well. Yeah, and just be sure to let people know, I think, like, at the beginning of the conference, like, you know, just letting people know that there is a glossary that they, because it's not only contributing is like letting people know that there is a glossary in Korean, right? So a thing that doesn't need to be a session or anything. But like, since you're one of the co-organizers, if you're on stage or doing like, welcoming people or something, just, you know, let people know that there is something like that, right, in their own language. Sure. I think the first part is about introducing the glossary. And the second part is how to contribute. Yeah, including the English content as well as the localized content. In case of the KCD Taiwan case. But in case of KCD Korea, I got a Hengon session. So may not have too much the introduction pages, it will be just majorly focused on how to process it, how to contribute to censorship, as well as Kubernetes. So, let me handle those presentations and I just hope to share. I'm working on that part. Okay, awesome. Thank you. And I will check the writing session from Catherine. And I know we have good content, shared content regarding cloud growth story. I'm going to fully use that content. Awesome. Yeah, that's what it's for, right? Like, we don't need to reinvent the wheel, like, let's like, in each time we can improve it, you know, like new ideas and then have something. So, if someone else is very happy. Okay, and then do you want to suggest something to remove permission entries from the CNCF glossary repose settings demo file? Because it's overriding from written by CNCF people? I don't know what this is about. I guess there is no June, right? No. Yeah. Yeah, I have to tear his daughter. I'm sorry if core from June eyes. Luckily, I aware of what this is about. And I have to introduce that we are using using setting workflow in our GitHub repository setting. So that workflow applies our setting configuration into GitHub repository. So if we need to update approvals or maintainers permissions, new development branches, then I'm very sorry. It's very hot place in South Korea. And those settings can be done by GI in GitHub GI. But we are using setting GitHub workflow action. And we in order to update our configurations in our repository, we have to update settings configuration five. And that's how we work when we add new localization members or when we change maintainers permissions. But recently, CNCF organization added new workflow kind of workflow you have in that covers whole repositories in CNCF GitHub organization that effective to CNCF organization, which is a sheriff boat. This boat checks all members in CNCF organization and actually cares and sheriffs whether individual repositories at not confirmed or invalid members or permissions. Is it understandable, Catherine and Noah? Yeah. Well, I did see like some changes on some other repos and I saw that they were doing like some some things. But I think like the whole thing like how to do like the whole the technical stuff like honestly, it's like you and Jihoon are kind of like always been our leads. It's like just do whatever you think is there. Yeah, that's what I was going to say. So I mean, I cannot really say if it's like good or bad that way. If you guys say that. Yeah, your first target in our gurus for all that stuff. So whatever, yeah, just just I think like for that type of stuff, whatever you and Jihoon decide, just go with it. Yeah, thank you. And yeah, we will our duty as maintainers. I'm very sure Jihoon will do that. And the reason Jihoon why put this item into our agenda is about that some changes previously we only cares about the settings that YAML file only for automate automatically update permissions and settings in our grocery repository only. But since there is a new policy from CMCF organization regarding the sheriff board. So maybe we need to reduce the capability automation capabilities from the settings workflow in the our repository and then apply the overall settings from the CMCF organization. So that's the what you suggest in this issue. And surely I agree. So as Catherine and no maintenance mentions that yeah, I think Jihoon and I and maybe Chris another key city of CMCF can collaborate how to resolve this issue. So I just share the current situation on the apple of Jihoon's comment. Is it okay? Yeah, so we only have three more minutes. I just want to be sure that we get through the suggested terms as well. So I put the little thumbs ups and downs and question marks that we had on Slack. So I don't know who did what like to be honest with you. Sure. The message views has two thumbs down. Mark, do we have a question? No, I was just suggesting that we just maybe maybe for the ones who are clear like cloud storage is three times thumbs up and the chrome drops like three times times down. We just we can just go on and label them accordingly. I could do it right now. And the rest could be like, yeah, still open, right? Yeah, so fault tolerant, I would say, but it's like that's not necessarily like a cloud made in the firm and doesn't We have like a few minutes. Seoko, could you just put like on mute? Yeah, it's really hard to concentrate. Otherwise we want to be at the party too, or like... I'm sorry, I'm not sure how this roundy picked you. We're just jealous, we want to have fun. I hope to invite actually in South Korea. Yeah, is it okay? The sound is okay? Yeah, now it's better. Yeah, it's like... Yes, I think the the terms overly, I think they are very fundamental terms except the web assembly part. So I mostly put the thumbs down in case of me. And in case of the message queue, I put a curious mark since I think the I think the message queue are very involved term when we talk about some cloud native applications. So in that perspective, I think we should include that term, but as you know that term is very general term, general technology or general functionality in the cloud computing but also in just computing part. Yeah, that's what I was thinking. So I don't feel like it's that necessary to understand cloud native and it's not cloud native itself and we do have the event driven as someone. Yeah, so I think I saw very related term already defined term in cloud native glossary which is event driven architecture which includes some kind of description related with Kafka. Actually, Kafka is a solution that provides the kind of message queue. So they are very related, so maybe we can read the contributor to update the event driven architecture terms about the message queue not just not affecting them. So that's the reason why I put question mark there. Yeah, that's just my opinion so please feel free to decide others. Thanks. What do you say, Noah, about including it? I said something down so I think event driven architecture is valid but message queues is like a certain technology. So I don't know, I don't think it's also it exists also without like without cloud native. So I would not accept it. I think and most of the two of maintainers decided to include this term so I do like to give point to them actually. You mean like I'm going with thumbs down? Yeah, yes. Okay and we always said if we're not sure it's better to first say no and then reconsider later instead of having someone work on it and then, you know, just get rid of it again. Okay, so the rest we can do offline. I'll just update the message queue issue and then Awesome. Awesome and then let's decide for the other ones in the next coming days and update those two and because I didn't I honestly I didn't I missed them so I didn't see those. I was like oh there are all these issues. So let's respond. Okay, cool. Thank you everyone. Thank you. So yeah in case of the web assembly part I think we got some agreement from Chris and I and I remember something about it. Yeah, so I was like then we decided that we forgot to okay so I highlighted that. Yeah, so please the trilogy that issue. Okay. Yeah, I can just do it because I'm already on it. Awesome. Thank you. Well, thanks Soko for taking the time while you're out with your colleagues. I'm a blast. Yeah, I'm very sorry that I'm involved in other things. It's a change of the regular office and like I mean it's 10 now it's 11 p.m. so it's like you can do whatever you want. Yeah. Yeah. See you around. Thank you. Thank you.