 I'm now Nishijima from Hitachi, so I have 15 years of experience under OSS contributions and Linux kernel and OpenStack and Hyperledger, so I have contributed to the Hyperledger community and since 2016 and I was one of the organizer of the Hyperledger Japan chapter, so and yes, I was a blockchain person and but so this April, I started to contribute to the CNCF project and I became CNC's ambassador this fall and today I'd like to make a presentation about building and growing the CNCF Glossary Japanese project and cloud native committee Japan. Let's start this agenda. So, why contributed? So, for my reason, it is fun, so it is important to that thing, and I love learning the new things and the contributions that help everyone, so I can help so someone I don't even know the name of the, so of course my skill will improve in the in the past six months. I have learned a lot of the a lot of the cloud native things and I have a lot of the new connections, so I think this is the most important thing is to make a new connection for the contribution and building the community. So, I'd like to introduce the cloud native computing foundation, so as you know CNCF is one of the biggest OSS committees, so since 2015 this project has started. So, the CNCF is a non-profit organization that's sorry and CNCF is a non-profit organization that supports the growth and the wide-spare adoption of the cloud native system and the technologies. It hosts many popular OSS projects like Kubernetes, Prometheus, and Istio and so on. The CNCF provides a tool and service for building scalability applications and running them on the public and the private and the hybrid cloud. And there are 117 projects and 220,000 contributors and join the disk community. So, my first impression is there are so many projects, so I don't know what's going on with this project. So, I was a bit confusing to the where to start. However, CNCF has documentation for the beginners. There you will find many opportunities to contribute to the mentorship program and the technical advisor group and the committee group and the ambassador. Then, I found a non-code project. It's a cloud native grocery, so I'm a beginner. I'm not good at the technical in the Kubernetes or something that technically, but it is suitable for me. So, cloud native grocery is a project led by the CNCF, the beginners value subcommittees, and its goal is to explain cloud native concept in the clear and the simple language without the requirements of any previous technical knowledge. So, it is important things to... It is important things, so it's very important to use the same word, meaning when discussed with non-technical people. So, it reduces miscommunications. And of course, this grocery is a useful beginner to join the community and the contributions. Currently, cloud native terminology has been translated and localized to any language. And in this CNCF cross study, the important thing is that so localization is not translation. It also requires a cultural context. It is very important. And so, I'm not good English, so I know non-English speakers have a hard time reading the English document, and so it takes a long time to read the documents or white paper. So, translation tool is like a deep-air or Google Transition, a not-good solution in the technical article. Some phrases are missing, so sometimes it doesn't make sense. So, they are very good to get an overview, but not yet good enough to be used for technical writing. So, CNCF grocery in Japan. So, I started a Japanese localization chain in this May. So, this is a basic requirement to start a new localization chain. It's at the three branch here and the two approvers. And to merge the main branch to minimum number is 10 translated terms. So, currently, Japanese localization chains have nine contributors and 14 translated terms, so we can merge the prerequisites to the main branch anytime. So, our community operation is very simple. So, the only tool is GitHub and the Slack. So, if you join our community, just chat and assign me on the GitHub. And if you need any advice, so, ask me on the Slack. So, Japanese is fine. So, the review, technical term review will be pointed out in Japanese. So, Japanese translation rule as a follow. So, Japan has already, Japan already has a Kubernetes document community. So, our rules are also basically based on this community. So, we make it easy for people to come and go in the each community. So, they are also proven specific in the Japanese language. So, three things are long bar and the katakana and the propranam. So, what ending R or R E have a long sound, like infrastructure. This word adds a long bar in the Japanese. But, however, the container. So, there is only exception. Many Japanese engineers say container is a container, not at the long bar. So, this is a cultural context. And the katakana, so, cloud is Japanese word called a kumo, but we say cloud. So, it is the propranam's closure of the English. And the propranam, so, if you use translation tool, infrastructure as code, the translated code, but it does not make sense. So, if we use the translation tool, so, we need to create those dictionaries. So, what's next? So, there are currently 85 words in the CNSF glossary and we have made a minimum request word, count the merge into the main. So, I sent the prorexel yesterday, so, so, but we found some confusion. So, after finish this presentation, I will fix that. And we hope the translation all the words in the next year or next next year to achieve this goal. So, we need more contribution. And the CNSF glossary is not only the opportunity to the non-technical contributors. And so, CNSF has a project called a technical advisory group and those projects also need the translation. CNSF tag will oversee and coordinate the interest in the logical area of needs of end user and the project. There are eight tag up activities, so, tag security, tag storage, and the tag up and the network run time. Sorry, observability and the environment sustainability. There are a lot of the tag. And so, CNSF security technical advisory group so, facilitates the collaboration to the discover and produce resource that enables secure access policy control and the safety for operation. And for another minister, developer, and end user across the cloud native ecosystem. So, this tag publish security white paper and I translated this white paper. So, this translation experience was very, very, very good for me. So, I learned many things, many security time and the concept. And I could understand more deeply than just reading translation documents. So, I have been waiting for this document because became a PDF. So, Japanese white paper is not yet available in the PDF format. So, I'm waiting. And many other documents are available. So, software supply chain based products and secure software facility and the platform engineering maturity model. CNSF white paper, there are a lot of the document is here. So, those right sides, those two are translated into Chinese. So, if you're interested, we can trust it and localize it together. So, before I finish my presentation, I'd like to introduce the cloud native community Japan. So, some ambassador including me and the local community member launched the cloud native community Japan as the Japanese chapter of the CNSF. So, for a long time, cyber community has existed, but so it's like a Kubernetes community, Kubernetes community for beginner or some prominent use community. Also, cloud native community has a hundred of the participants. However, those community is no connection to the CNSF. And so, it was not visible to the CNSF. So, CNSJ, cloud native community Japan, aim to connect the Japanese cloud native community with CNSF and on the world. So, this picture is a cloud native community meetup. So, December 1st, it's severe. So, if you are interested to join the cloud native community in Japan, so please feel free to join us. And so, I'd like to conclude my talk. So, thank you so much for your kind of attention. Do you have any questions or comments? Thank you for your presentation. So, I didn't know the CNSJ. So, how often is the original grocery updated? So, is it quite stable? Or are the, sometimes they're changing drastically? How often is the original grocery updated? So, yeah. It's so often updated so that maybe a little difficulty or the problem to catch up the localization. So, CNSF grocery has a monthly meeting. So, they have discussed the new terms and if the CNSF grocery GitHub has a list to make a grocery term. So, maybe there are a lot of the, maybe 100 or 200 times. And the bus for now, there is 885, 85 term is okay. Thank you very much. So, yeah. So, we need to keep the trial localization team. Yeah. Thank you. Thank you.