 The agenda in here, if you can add your names. I saw some teams kind of made an update. So hopefully they will join as well later on. Cool, cool. So let's get started. So we have the tags somehow half implemented. So we did something we wanted to iterate and then the issue is kind of like stuck in the pipeline. So I think the recommendation would be for localization team do not implemented yet because then you have to do it all over again. So it's like, I thought it would be quick because we did like, okay, let's do this really quickly and then do the other change. So yeah, I'm always kind of mindful or I tried to be because I feel bad when people do double work, right? So I would maybe just not touch it. And also we wanted to provide some guidance as to how to handle tags and the documentation but we wanted the updates to be live yet because we've seen that in some, in two or three maybe or two, I don't know, terms there were like several tags. And it's like, yeah, sometimes you can add like lots of tags because it fits into, from a broad perspective it fits into various things but then the tags are not useful anymore because they're not really telling you. So we wanted to be very deliberate and thoughtful about how we use them. So they can be useful for the user when they're looking for terms of understanding how this fits in versus like putting all lots of tags that suddenly just are lots of noise and don't really tell you anything about it because everything is technology related. So we also started the, in the discussions the, we started a discussion in GitHub for how to handle updates. So it's not already provided feedback. So basically there is no right approach right now here and we just want everyone to maybe share their own approaches and then kind of figure out what the best approaches and when we found something that the most, and again, like everyone can handle it the way they want, every team can handle it the way they want to but we wanted to kind of first gather some ideas and have a conversation there before we kind of say like, this is like the recommended approach. So Team Portuguese has one, if anyone else has one, it would be great to share it here or comment or just like engage in that conversation because it is kind of, oops, not this one. It is important. So again, like here to see how you appears and handle it and let, please, please let's have that conversation. Glossary at KubeCon, great news, Lightning Talk was accepted. So that's great because it's a five minute talk. It's generally like people come to see the Lightning Talk so it's not necessarily people that come, oh, I wanna hear that particular talk. So you have a much broader audience, right? It's a much bigger audience. They come to see the Lightning Talks, they come to see a lot of things. So you are touching, you're getting to, you reach people that not necessarily picked you or not necessarily, they didn't see your talk or whatever on the list. So it's great for awareness. The goal of the Lightning Talk is saying like, this is the glossary, this is why it matters. This is why you should use it. If you wanna contribute, this is why you should contribute. We're also localizing, wanna localize, this is what, so it's like really kind of like, really quick, short explanation of what it is. It's purely awareness. So people know that it is there and that they can participate and, yeah, and contribute as well in the localized effort. The panel discussion, unfortunately, well, not our first nation state because wait list means that it was, it was like getting a talk in KubeCon is very hard, right? There's a ton, like we've gotten lots of rejections this year. It's very, very hard. So wait list means that it was good enough, right? Like it was really good to pass that bar but they didn't have enough spots. So they do sometimes speakers cannot come or something happens and then it opens up. So there's still a chance. The panel discussion, again, for those who don't know it, we invited several people from the localized team. It was very localized focused. And then like why everyone thinks it's important to have a localized version of the talk and so on. So, yeah, we wanted that to be like an opportunities, particularly for some of, we cannot invite everyone, of course, but some of the team leads of the different localization efforts to give them a chance as well to talk to a bigger audience. Then we also want to empower you to, we would love, like, and that's like, if people are interested, you know, like what we're, of course, we want to do this on a larger scale for the glossary in general, like localization in general. But I think like we just started this effort, localization, the localized glossaries are still not complete. They're still work in progress. So probably not a lot of people in your region know that there is a glossary available in Korean and German. You know, like they don't know that, right? So, and they don't know that it exists and they don't know that they can contribute. Like, so both things are important, right? Like having them knowing that it exists and using it and contributing is another thing. But I think like getting the word out there for people to use it is the first kind of step. So, we would love for you to, you know, go talk at meetups, KCDs, national conferences, why, like you are part of CNCF project, why it's important, yeah. So I think that would be great if you could do that in your, it's a little bit good for the teams as well, because you can then become really the face of that project in your respective regions. And so we created the stack here. Let me just go real quick over it. So basically, just like quick explanation what it is. But it walks you through, okay, first like cloud native definitions in general, right? Like for instance, right now they're really, like really driven by vendors, why it's not ideal and why we need kind of a very easily accessible one. So this is like in general why we need cloud native definitions or the issue with, or the problem statement with the current state without the cloud native glossary, then we talk about the cloud native glossary, right? It's trusted vendor-neutral community driven. That's really important, right, for all these things. And people can keep it up to date, right? Like if you have a vendor definition, the vendor definition is going to be outdated because it's not their priority. Very often it's a marketing tactic. I know it because I'm in marketing. So there's like an SEO search engine optimization you're trying to, so you do it once and then you don't update it. So you see a lot of these things out there and technology changes far too fast for it to let like a stale definition out there that just because like it got a lot of backlinks or whatever pops up at top, it doesn't mean it's the best one, right? So having something that is trusted from the CNCF, vendor-neutral does not bias towards their solution or how they wanna view, let's say, observability or whatever, and community-driven. I think it's really important, right? And then our goal, then how people can help, right? This is not necessarily for the people who want to contribute. First, like just use it, you know? Like when people are, when I learned I'm out of native, link back to definition and so on and then help as well improve it as you use it. And then we wanna talk in general a little bit about contributing in general. So this is like from, a lot of this came from Rael and Victor, they've been talking about this. They also did a KubeCon talk about contributing to docs but like more towards gear towards technology, technology, no, KubeCon, Kubernetes docs, sorry. And so here are a lot of inspiration from there. Like first of all, like what, how can you, what are the different ways of contributing, right? It's not just docs, it's not just code, right? Like they're all these different things, right? And we're gonna talk about this. So where that fits in, why localization matters. This is like what really important for localization teams, right? And then why you should do it, like how you can kind of, the contributor ladder, then like about your team and how to get started, okay? Like if people are interested, what should they do? And then I think like it's basically kind of that's like the resources and so on. So, and again, the wrong one. So, no, I'm always, I have too many tabs open. So basically, and I don't know, like maybe someone has ideas to improve it too, you know what message do you think might resonate? Again, we wanna make sure that we are a team, like all localized people as well, like work together. Like if people start using this and talking at conferences and see something resonates particularly, like just put in like something, you know, let's improve the deck so everyone can improve it. So let's make this not like something, oh, I use it and then I figure it out the best practices and don't report back, right? Like the idea is kind of helping each other. And so, yeah, if anyone is interested, let us know, I mean, we would love to help you, like, you know, like whatever help you need, I don't know. And it also like if anyone has any other ideas about what we can do to get the word out specifically in the countries or I don't know, doesn't he wanna have an idea? I know it's a very kind of, my only idea was like talking at conferences, but like I'm sure there are other things that we could do. I have a question, more organizational one. Where does the slides live? So is there a folder or something that we can share? There is a, yes, there is a folder and there's a business value subcommittee folder on the CNCF drive. G drive, yeah. Yes, because not everyone has like created. Yeah. I was thinking of maybe we can have one place where the template lives and also the localized ones with their adjustments maybe. So that we have everything on one place. Yeah. And then we can- It would be great because if someone leaves from that team and just like disappears, the next team doesn't have to start from scratch. Yeah, and also people have the chance to yet to see what maybe the other teams adjusted in their slides, yeah. Yeah, it's gonna be difficult sometimes when it's, because if it's all in their legs, it could be fine. But you get a sense, right? There's a lot more text here than on the other one. So probably there's more. Yeah, I think that's a good idea. I think, yeah, I'm probably, I think we can share, make it, because I created a folder promo, cognitive promo or something I called it in that folder. So we can probably share that folder and maybe link to it in the glossary channel on top. You know, and then if anyone has ideas as well, like whatever, whatever, like, I think this is a team effort, right? Like whatever we can find to improve it. Any other ideas, top of mind? No? Yeah, something to continue thinking about. Oh, okay. It's more a question that's better than an idea, but do you have some meetups per country? You, a list of meetups, you know, we are already involved. The CNCF is already involved. I'm not really a meetup guy, so it's not something I'm really used to. CNCF. Yeah, I guess there's a page for that, right? So the CNCF has a page for every, at least every official CNCF meetup. Let me check. Maybe you can go, and I don't know, Berlin. See, Berlin, here you have different ones. So here's where KCDs also live. The KCDs, they put them here. So KCDs, again, for those who don't know, it's Kubernetes communities. These are more conference-driven things, but then they're also like different chapters. So this used to be on meetup.com, but now the CNCF kind of moved, like a year and a half ago or something, they moved. So here we have Canada, and yeah, just go here and see. These are all CNCF, so they should be all relevant. A lot of them are still doing stuff virtually. So if there is no meetup in your region, and the other one would be meetup.com, right? Because meetup.com, that's another one, right? It's not so some, yeah, on both sides. It doesn't have to be a CNCF-affiliated one. It could be a DevOps one. It doesn't matter anyone who is using Cloud Native, but we're not saying it's just the CNCF community, right? So yeah, and like, virtual is always easy because you can do it, right? So it's worth checking maybe a little further. I think most are kind of going back to in-person just because it's so much nicer and people are sick of doing stuff virtually, but I think some are still doing virtually. So yeah, or maybe the other thing is like, whenever you have a trip, a work trip or whatever, like keeping that in mind, you have to go travel, I don't know where, and see ahead of time if there is a meetup there and then say like, oh, maybe I can talk there. And so that's another thing. It's like, it's easy to forget, but like, yeah, you're not gonna travel somewhere specifically for a meetup, but sometimes if you're gonna be there, but that requires a little planning ahead. Yeah. And so the Bengali team's blog is live. Go check that out. Very cool. I mean, it's, I love working on them because I kind of learned so much about the different languages, specifically the ones I didn't know about. And so Bengali, like a whole little story, backstory, which was interesting. The Spanish team is going to go live on the 19th. Oh, I do have the Korean one. I haven't looked at it yet, but that is on my to-do list. And then team Portuguese is TBD. And, okay, I think this is Seoko or Jiwon, or? Yeah, I added it. So in our repository, the sign-up is required for new commits. So every new, I mean, every contributor should use sign-up when they make a commit. So if you don't do the sign-off, then pre-test for a PR will stop you. So it is now actually officially required. So please add sign-off to your commit. So is there any question regarding this issue? But handling this deal for new commits are very easy for us, which we need to guide to new contributors. But when we try to merge commits in branch to another branch, they will generate some DCO issues since we still have some commits which does not have sign-off yet. So folks who are managing your development branch needs to aware of this situation. Maybe we need to disable manually the DCO for those PRs to help PR that want to merge commits in a branch to another branch. So it is kind of reminder. Thank you. But I think now it's automatic, right? Because I remember at some point it was like, oh, you have to sign it. And now as I submitted a PR and already auto-signed it, which... So if we use GitHub, GitHub GUI, then some parts just in automated. I mean, when we make a commit using GitHub GUI, it provides the sign-off option typically. So it is automated. But maybe many people does not use GitHub GUI when they make a new commit. They need to provide an additional option to provide a commit, sign-off commit to... Sign-off commit. So it is kind of... When we make a commit, we use this kind of command. It commit. M option is for message. But with S option, you can give the sign-off to the commit. So if you use just to get a share line, then it is not automated. So content creators need to take care of this. Yeah. It's an extra set. Yeah. Yeah, I guess this is something we have to add somewhere in our documentation, I guess, yeah. Yeah, because we did ask if we could like sign-off if we could like skip it, but the CMCM set up. Yes. So it's something that they need in its global. So, well, yeah, we'll have to add it somewhere. So first thing is really about this. It's like Noah said, we need to type, we need update type so that people can add the sign-off in their commit message. And then we need to find a way to resolve the situation that TCO blocks a PR, which includes many commits in branch to another branch. It still stops our PRs. So we are manually disabled this TCO for those PRs. So we need a way to resolve that. I think that's all for the TCO. Any updates from localization in general that Soko Jihoon wanted to mention? Yes. So I think just one you say it's about French, but since there are many approvals from French. The right representative kind of tell us the news. And that's actually the first language that is up next. So, Davia. Yes. So with the French localization team, we made the initial PR. Thank you, Soko, for review it so quickly. So the PR is ready, but I wait for my two, the two other maintainers to review this one. It's quite complicated right now because one of them is in vacation for like a long time. And the other one is just doing this, I think in the few days are coming. And it will be pretty ready, you know, I think like in maybe one week. And on the other side, I'm currently working on translation on other terms. So it's, it advances slowly, but slowly, but surely. Yes. That's it. Thank you. Awesome. Well, really glad to have you and seeing that things are moving forward. So definitely excited to see when, whenever you can go live and that will, yeah, will be awesome. Just one, just one, one question, sorry. We, the, the dev effort branch is behind master branch from like eight or 10 commits, I think. Should we rebase this one. Before after remade the initial peer. So all of this work for generally for your, your, for your team. So if I. Yeah, I think I can answer your question. In general, you can make a PR open up PR whenever you want. You think. Your development branch need to be updated. So it was. You, you are going to translate and localize your localize the source English document. If you don't update your development branch, your source can be updated. So if you can. Frequently, I suggest to frequently update your development branch to think with main branch. In that way, when you try to dip bars. They were apart development branch into main branch. The conflict will be minimized. Okay. So we should open a new peer when requesting merge from master into dev. Dev or effort. All right. Yes, right. Thank you. Right. Thank you. Okay. Well, then I think I go next. So team Germany is also making super slow progress, but the program is there. So we have six terms ready. That is one more than the last time. And we have three terms in progress. So I'm a little bit disappointed because I made a LinkedIn post and it gained some attention and people were super enthusiastic. But then. Unfortunately, nothing really happened. So there was there were no additional contributions from them. So what I did is I. I looked to the Kubernetes localization efforts and I plan to maybe join joined the Kubernetes localization meetings to see if I can, can somehow get folks from there in. But so my, my first impression was that that I think also with the Kubernetes localization team, team Germany is not really active there as well. But I will have to check that again. So that's, that's my plan. Yeah. And I hope that, that there will be a little bit more, more folks joining. I'm just thinking that actually, I know the LinkedIn post got attention, but at the end it didn't translate, but maybe like for our promo kit for the teams, we could also create like some social media post ideas that the teams could get off. That would be awesome. Yeah, people can just, you know, like just like translate and enter their language and then kind of like, or use as inspiration or whatever. And maybe we could create also like little carts, social media carts with, you know, something that people can, so, so people, yeah, just to give them tools. So I think that's another idea. So we have talks, social media posts is another idea. So if there are any other ideas. So you did have an idea Noah, but you didn't think about it because they were, because I think it's actually a good idea. It's just, it just didn't. Yeah, it's just a difficult. Yeah, I don't know. I don't know what. So I have the impression that the German folks are not, are not that, that active in the, in the community. That's one thing. The other thing is that you, you told in the, in the Slack channel, in the Slack chat that maybe all the German folks are using the English terminology. So they don't really use the German localized ones. I don't know. Could be. Yeah. I mean, a lot of people in Germany do speak English and like a lot of tech companies have teams, international teams and they speak, even in Germany, they speak English at work. So that's a reality. So that, like, why would you. People are like, but still, like, still, like some people, you know, it's, it's still easier. It doesn't, it just, I think it's more difficult to make a case between people, among people who actually are very. Comfortable with English. But there are people who aren't, and it means like it's, we should still create it. It's just more difficult to find people. Yeah. I don't see anything for Hindi here, but I see that Kunal is there. So I'm just going to put him on the spot. Yeah. Hi everyone. I think it's been long that I've like attended this particular meeting. So to be honest, like I wasn't in sync with the Hindi team for a while, but I've been like reviewing the chat and like total 15 terms have been localized till now. And four or five of them are, you know, we are working on that. So I wasn't in sync with the team. So I'm not able to like fully update on that part. That's fine. We're still happy that there is like some Hindi representation. Thanks. Okay. And so I don't think anyone, someone from the Italian team. I don't think so. Yes. So Italian team, I think there was also like a little summer kind of whole because they were very active. And at some point I said that's going a little slower, but they have 15 new terms and deaf branch ready to merge and six new terms currently in review. And more coming soon. So, and hopefully next time someone can join this meeting as well would be awesome. Korean. Do you want? Let me. Okay. Let me introduce Korean progress. In case of Korean, actually, you know, you can team. Who is one of the approvals in Korean localization team. He met many students who are willing to contribute to our recovery. And he is, he giving some effort to invite them and guide them. And currently we have six terms are working in progress. We have six PRs. And then one new term has been added. But this work is in our development branch. And maybe when we merge those working in progress here, we will put our development branch approach to main branch so that they can be led. Also, we are, we have, we we use the an issue to trace Korean localization progress. But we determined to use this question capability. I mean, you can find this question in our repository. And we will keep track the Korean localization progress using this question. So in that discussion, we have some guidelines to contribute Korean localization and what are the essential document to be localized. And then people will contribute to us. We could message in this question so that they can be assigned to the job. The reason why we use this discussion is that some localization teams are using issues, creating individual issues for initiating new localization term. But I think sometimes those issues are overwhelming for our repository covers four pages of our issue pages. So we try to reduce that issues. And if we use this discussion, then make Korean contributors don't need to make issues by on. And then this issue can be entrance point of Korean localization contribution. So yeah, that's all from my side. Is there any question regarding Korean localization or those using this question? But I think it's great to see what the other teams are doing to kind of figure out what, because there is no right or wrong, right? There are different ways and different things work for different people. So it's great. It's great. Yeah, it's great to see that. Yeah. Yeah, we also have plan to update. I mean, update how to trace the outdated content. Yungon is preparing a method to keep updating the outdated content. You will put it, the discussion that I mentioned before. Okay. And then team Portuguese. So a new approver, reviewer is coming soon. And then they're working on a guide or checklist for approval. And that's a really good idea to have like how I wish like now maybe a little hint. Maybe they could do that in English too. And then two terms are ready, but need to rebase the main branch first and blog post version one is done. So I guess we should see that very soon. And if we have that like with Korean and Portuguese, we would have all blog posts for every single language that is live now. So, so that's, that's cool. Another thing that's new, I forgot to mention. So we are finally able to record this meeting. So I'm going to go on a YouTube channel. So other people can see that on their own time, specifically with people in, on the other side of the world as Seho Ko and Jihoon can say, it's tough to make it to the meeting. So it's good that we have that. And whenever team members also share their knowledge, it's not like it's there and captured and people can see it later on. Anything else that someone wants to discuss? Oh, Matt Young, hello. Didn't see you. Yeah, I had a conflict from 9 to 9 30, so it's just lurking. Hello. No other discussion topics. Okay, I think we're in a really good shape. I'm excited to see localization efforts moving forward and I really hope that we can do the little promo things localized. So I think I'm excited about that. And I hope that the different teams are excited about that as well to be able to, you know, talk about it and, and, and, and, and different meetups again, again, like please reach out, happy to help however we can. This is good for the project. It's good for the team. So if you have, if there is something we didn't think about, but also if you have other ideas, right, like we have the talks, we have social media posts, like if you have any other ideas that would make it easy for people and we're creating this promo kit, basically, right? It's like, okay, you want to promote it here, the thing. So what else should be in that promo kit? Please let us know. Okay, but I think I had a quick question actually that brought me here today. The landscape graph project has been kind of quietly bubbling along in a good way. I mean, we've been working together last month, a month and a half, some things took a little longer, but we've consolidated down to a serious design that is scalable and, and have started documenting some things and have figured out how to do graph composition, right? So different domain experts from different tags and different groups can contribute in a way that they don't collide and that we can have CI and CD. So one of my questions about the tags that are being defined, not technical advisory groups, but the attributes that are part of the glossary, are those localized? Like I'm to the point where I can start to bring in categories and tags in this new well-formed model that uses GraphQL as an interface definition language and a way to standardize on something that is an actual standard GraphQL as being the API surface in and out of the graph. And so now I'm starting to actually do some specific data modeling and so. Yeah, the question about the tags, are they localized to different languages or are they just? I think so. I didn't pay attention. Yeah, I mean, I know all the definitions, all the, all the terms and things are localized, but the actual metadata. That's. Because otherwise it doesn't make sense, but like so cool. I don't think we have implemented the tags. Not everyone has implemented tags, right? Yes. Currently we implemented tags, but not fully implemented. So we didn't guide each localization teams to add, I mean, their own tags or localized tags. Yeah, but some of, some teams are working on translating and localizing tag itself. So some, some localization teams have, for instance, Korean localization team also try to translate tags, but currently it is in their own development branch so far. And when we put it main branch, then you will see the localized tags in Glossary website. Okay. Cool. Yeah. At this moment it is, this is premature, but you will see the localized tags. So, I think so. Okay, cool. Well then I will, I will plan accordingly so that I can do that. Except localized tags. Do you know, I was planning to implement it such that, you know, whatever is there will bring in, but if some languages, if some, if some tags don't have translations or localization in some languages, that's okay. I won't make it break if they're not there, but if they are there, I can display them. So, you know, you know, code and all of that. So it should be, it should just work, but it'll be the first kind of actual localization testing or, or non. Yeah, so I might find out that somewhere along the linkage in the data model, you know, we're not correctly handling internationalized or localized strings, but I'm pretty sure everything is full unit code throughout so it should be fine. I think if we have some mature localized tags, and I will share it through a link, so that you can take localized tags, but not, not very many tags. We, in case of glossary project, glossary partially we don't, we didn't define not too many, I mean, pure tags. Maybe we have six, seven tags country. Not too many. The tags are very high level, and we're really kind of steering away from having one term with lots of tags, and they're kind of like the idea is to give us a broad overview of how to categorize that term. So it is less is more kind of what we're doing. No, that's, that's perfect. I just want to make sure I was correctly set up to handle multiple languages. Yeah, yeah, and we are I don't know if you were, because I cannot see when people join when I'm sharing, but like at the beginning we're still, because the tags are not fully updated. What we like the way we envision it in the English version is that we're also, we're kind of actually asking or like recommending not to work on the tags for now until that it's implemented so there's no double work so it is a little bit on hold, but I know that your project will take a little, anyways, it's not like it's going to go live. Yeah, yeah, I'll have to catch up. Yeah, I came in at 35 minutes after so, so I'll have to watch the recording. I put in the chat, sort of the current state of the graph with the GraphQL stuff I mentioned. That's more of a, just a bunch of links, but it's sort of a summary of the various pieces of technology that we're bringing to bear in the actual implementation of the graph. Okay, cool. Okay, well, thank you everyone and see you hopefully all next month. Thank you. Stay cool. Have a nice day. Thank you. Goodbye. Bye.