ステーションを始めますアミューキー、ヒタッチ、ダイキー、シェクトリック今日はここで感謝します今日はここで幸せです今日、私たちのコントロビューションについて話します日本のハーブレッジファーリックのコミュニテーションについてお話しますとにかく、ハーブレッジファーリックは世界中で使用されています私たちがブロックシャンのテクノロジーを使用している人もいます私たちは英語の話をしていますそれから、英語の話を読んでいる英語の読み方があります英語の話をしている英語の話をしていますこのヴァリアーのハーブレッジファーリックのコミュニテーションは地域によって翻訳するお話をしています日本のファーリックのコミュニテーションはこれでもあります今日は、私たちのコミュニテーションについてお話します私たちの絶対についてお話をしていますOKはいおすすめということをお願いしますOK.So after this session, I hope more people will start the translation effort.So the first topic is motivation.Why we are here?Fabric is a great blockchain platform, so many people use it.However, English speakers have had time to keep up withfrequent updated hybrid document.There are two problem cases.The first case is translation tools do not provide enough quality.There are famous translation tools like DeepAir or Google Translate.Those are great tools, but they cannot understand the technical context.So automatically, translation documents do not provide good quality.In other case, some local engineers write blog posts in their local language,but those articles are updated soon because Fabric is updated frequently.For example, some guys write how to deploy Fabric V1.4,but when Fabric V2.2 is released, those documents are outdated.In short, no native speakers have language barriers.To overcome those language barriers,Hyperfabric Documentation Working Group has started initiativeto translate official documents into local languages.The goal is to enable more known English speakers to learn how to use Fabric in their local languages.If the document is available in the local language,more people will adapt hybrid technologies.Under the Working Group, there are 11 language teams.Each local community has their own contributors and they are working on translation.Japanese Working Group is the fourth group.The Documentation Working Group helps start new language translation.They provide good guidelines and communication tools.So, why we translate?I think we have three good reasons.The first one is learning blockchain technology.To translate the document, we need to understand the technology in detail.And the second reason is learning open source contribution.Contributing code is little difficult.So, translation is a good starting point to understand the contribution process and tools.Lastly, we can connect with local community.We can get feedbacks from local guides and we can connect with client companies in local community.These are the motivations.So, the next topic is community development.This graph shows the overview of Japanese Documentation Working Group.Contributors pick up English document and then they translate it into Japanese.And they submit the doc to the JTAR repository and mention the jacket and the document is erased.Contributors follow contribution process and they use communication tools.These contribution process and communication tools are supported byHabitat staffs and the Fabric Documentation Working Group.This graph is the latest version.So, when we start in the team and there is no concrete process.So, we faced a lot of problems.So, we solve those problems and we build community management like this one by Troy and Ella.So, let me share some problems and solutions today.This is the history of our community building.Launching translation working group.Develop contribution process.Standize translation rule and recruit contributors.So, first topic is studying a translation team.Studying a translation team is building a new open source community.However, we do not have enough knowledge and experience for organizing a new community.We didn't know how to build a translation team.How to call for contributors.So, our parent group, that is Hybrid Fabric Documentation Working Group helped us to organize a community.They provided us communication tools and contribution guides.Next, Japanese also helped us.They called for contributors in Japan because they have connections with local engineers.I am one of them.After studying the team, we had a communication program because original members used emails to connect with others.So, communication was closed.So, new members cannot access to communication logs.The other program is English is required to ask questions at FabricDog.ItemChannel.This is also a communication barrier.So, to solve the question, we asked hybrid staffs to create a new channel for JavaScript working group.Thanks to their effort, now we have Weki, Disco, and GitHub Zoom for JavaScript working group.So, we communicate in Japanese and everyone can see the communication log.This is how we solve the communication program.Next topic is setting the milestone.You know, Fabric has various active versions.Which version has to do with it?So, which version is best for translation?To answer this question, we said criteria.The criteria includes LTS version, number of users at blockchain services,and it's for a long time.When we started the project, Fabric 2.2 was the latest LTS.However, most blockchains provided Fabric V104 for their cloud service.So, readers read articles in V104.Concerning the situation, V104 may be a good candidate.But it may not be used for a long time.For the future, we decided to translate V2.2.It was a good decision because now most cloud providers provide Fabric in 2.4.So, it was a good decision.After setting the milestone, we decided the priority of translation because there aremany documents.So, where do we start the translation?To answer this question, Fabric 2.2.1.1.1 group provided as priority guidelines.There are three levels.First topics documents for document contributors.They include contribution guide and grocery.Next topic, next priority.It has high priority documents for developers.For example, key concepts, getting started, tutorials are equaled.The topics for developers.For example, operation guides and architecture reference are equaled.So, we follow this guideline.So, we first translate first topics and satisfy next topics.Now, we are working on others.So, the next step is developing contribution process.Contribution process is important to collaborate efficiently.The first solution is contributor role.Japanese digression working group consists of engineers,fabric code contributors, and professional translators.They had different level of experience about hybrid fabric.So, we need to find a way to collaborate efficiently as one team.So, we introduced three ways for contribution.Translator is a role for traffic document.They don't need to have any requirement.Reviewer checks the translated documents.They need to have previous experience about hybrid fabric.For example, fabric code contributor, fabric application developer,and the certification holder of the explanation.Tweakup support is a role for support using tools.So, each contributor can pick up a role as they like.Translator flow is also important for collaboration.So, we decided a translation flow.The requirement is simple contribution processbecause our community has been about open source contributions.So, we looked for translation process as an open source community.The most famous one was Sphinx.But we gave up using following Sphinxbecause the contribution process is very complicated.Fabric has modified formats like .me and .rstbut Sphinx only supported .rst.So, we gave up using Sphinx.Instead, we introduced more simple translation flow.We just followed Fabric's GitHub contribution process.So, each contributor picks up a file.They translate.And they just keep the document forward.So, it's simple, but we think it's effectively working.And next topic is task management.So, there are many pages waiting translation.So, we need to collaborate as one team.So, we use GitHub cover board.Yeah, I know you are familiar with cover board.So, this event shows the cover board.And the left side is to the tasks.And the next lane is a progress task.And the right lane is task completed.So, each contributor can pick up an issue.And we can share who is working on what tasks and what is left.So, the next step is standardized translation rule.The purpose is to keep the quality and productivity of translation.So, we introduced translation rule book and terminology.So, good documentation has common styles throughout all pages.But we didn't have common styles.So, when a translator submits a request,reviewers had to compare with the previous documents.So, contributors and reviewers had no time to check the styles.But we wanted to focus on the content itself.So, to solve the problem,we introduced a translation rule book.Translator checked the documents before submitting.Reviewers used the checklist as a checking point.The rule book itself is updated anytimebecause we may find some new problems and tips.This use shows the examples of translation rule book.It includes terminology, Japanese style,no broker format, PR template.For example, no broker format is usedto check if the documentation format is not broken.For example, the link to other documentsmay be broken after translation.So, we need to check it.Once example is PR template.We have a rule.One comment has only one pagebecause we want to avoid a large conflict.So, we introduce this rule.And we also have a rule that as a tag.jgpbecause all language groups share only one gt repository.So, adding the tag is usefulto pick up only Japanese document issues.And let me explain the terminology in detail.This is very important topics.We studied the translation.We used fabric grocery to standardize terminology.It contains 47 pairs of English and Japanese words.However, it did not work enough.So, 47 words are not enough to cover all words.So, we initiated a special subgroupfor creating new terminology for Japanese.So, we collected terminologiesfrom previously translated documents.So, we found 463 terms.And we categorized those words into four levels.Level one is the highest priority.Those words are fabric words, like order or endorsement.Level two is production words, like cryptocurrency.Level three is additional terms.And level four is common IQ words.This terminology is still in progress.So, we managed those articles on github.This is an example of our terminology.The left lane is English and the right lane is Japanese.So, continue to check if they use correct terminologybefore submitting a pro request.Create a terminology to introduce another problembecause we have over 400 words here.So, checking all words is heavy work.So, how much to translate those reviewsfor the terminology?To answer this question, we introduced a practical policybased on the levels.So, contributors must follow level one and two.It means that we need to followfabric words and blockchain words.And checking level three and four is additional.So, this is how we balance the qualityand productivity of translation.And the last topic is recruiting new contributors.A year after the launch of the team,the number of active contributors decreased.It often happens at open source quality.So, we need to do how more new contributors.So, we had meetups with Black Spanish Japan.At the meetup, we introduced our translation activityand we shared the very little contributionand explained translation flow.After the meetup, remember to join the meetup.Thank you.He is also the new contributor.So, we are very happy to have you with us.This is the current status of our team.We have completed translating 90% of the document.We hope we will complete all tasks soon,probably by the end of this year.As the translated document is available here.So, if you have time, please check it.And there are many languages here.So, please check it.We have French, Chinese, Spanish, and so on.Okay.So, next topic is translation tips.So, I pass my mic to Daiki.Go ahead.Thank you, Kondo-san.So, from this section,I will explain three translation tips.So, at first, it's the point of translation rule.As we mentioned before, we made a translation rule.So, I introduced the point of a translation tipsand a solution for a language-specific manner.In Japanese, there are two points of view.End of the sentence and punctuation mark.So, both of them, there are many types in Japaneselike punctuation mark, 10.And sometimes Japanese use dot and comma depend on documentslike thesis.It's actually up to people.So, we put a solution for a language-specific mannerto a translation rule.And another thing is a permutationto working members.And, you know, that's the important thingto use translation rule by working members continually.So, we tried many things like share by Wikiand put to review process like that.So, next is a sentence not to be translated.Sometimes it's better to not be translated to local languagebecause sometimes you have a technical problem or contents.And, for example, we have a technical problemwhen we translate link sentence.We couldn't go to jump to your pages.So, we guess it's a language-specific problembecause Japanese is not Latin language.So, we decided that link sentence is not to translate itinto Japanese.And, after that, we put them to your translation rule.You know, it's so important thing.So, last, it's for reviewer to understand easily.You know, Japanese is so complicated sentencebecause conclusion sentence is last.For example, in terms of grammar,Japanese and English is subject and verb and object,while Japanese is subject, object and verb.So, that's why Japanese is so complicated.So, for example, you translate this example sentenceby machine translation, you get left side sentence.So, that line is conclusion sentence.So, by machine translation,it's conclusion sentence is separated.So, we endeavor to try to make sentence shorterand conclusion first.Maybe it's very easy to understand.So, next, challenges for our work better.First, call for more contributors.So, actually, we have only seven active members.So, to activate our working group,we have to recruit more contributors.So, we try to do something like these things.Second, catch up to next LTS version.We know that the next LTS version will be released soon.So, we have to think about how to get new release versioninto documentation.Third, evaluation for Japanese documents.So, we want to know how useful Japanese documentation is.So, we think that we use metrics for page viewers too,any kinds of tool.But, you know, we have some ideas.But, we do not have a specific plan.So, actually, we would like to discuss with you.So, last conclusion.We showed four things, motivation.We want to remove the barrier for no English speakerto understand hyperlature fabric technology.And, through documentation activity,we can understand hyperlature fabric deeply.Community development.So, we tried many, many things to build, develop,and improve constantly for our work better.Translation tips.We showed three translation tips for solution specific problems.So, last challenge.We will try to three things for our work better.You know, our work activity is still developing.So, thank you so much for listening.And, special thanks for relaxed foundation staffs,fabric documentation working group.And, thank you for everything Japanese documentation working group members.Tsujita-san, Shimosa-san, Sato-san, Uchiyama-san, Maekawa-san.Thank you so much.So, thank you for listening.So, if you have any queries, please let me know.Regarding another language, actually, do you know it?The quality?Yes, so I think contribution process is very important for collaboration.So, because if we work on translation by one person, it's very hard work.So, collaborating with other people are very good ways to translation.So, to work efficiently with other guys, contribution is very important.So, Fabric documentation work group provides good baseline,but each language has different situation.So, I think it's a good idea to improve those basic guidelines to fit their own language.For example, Japanese team introduced terminology for Japanese,because English and Japanese don't fit one-to-one.So, we need to decide the appropriate words for Japanese.So, yeah, I think creating the contribution process is important for the language community, too.Welcome.Go ahead.You mentioned that you have tried using Google Translate.Have you tried other translating tools like DPL, for instance?Yeah, we also tried Google Translate and DPL.Yeah, of course, they provide translation documents,but they cannot understand the technical context for blockchain or high-performance fabric.So, sometimes they display weird translation.So, yeah, we need to translate by ourselves to provide good quality documentation for leaders.Property, I understand that Japanese are very particular on details of documentation.So, is it okay to ask you to express your personal opinion about quality of the public documentation?I understand this is a tricky question, but you don't need to answer it.You don't have to answer anything.Yeah, I think it's a good question.So, I think fabric contributors provide good documentationbecause it's very well organized.So, they provide the getting started tutorials,the quality concept, and the reference architecture.So, we can check the token at best of our levels.So, Bias can use tutorials and getting started.And if an operator who are working on production leveltake care of these reference architecture or operational guides,so, I think the documentation is very organized.So, yeah, of course sometimes I cannot understand some of them,but yeah, overall I think fabric provides good quality of the documentation.Does it make sense?City, does it fit your expectations as a Japanese industry?I'm sorry?I understand it's a good documentation,but does it fit your expectations as a Japanese engineer?I'm not satisfied with the documentation.You would like to have more details.Oh, and I know, yeah, in Japanese culture,editors, customers want to build quality of the documentation.But this is the open source community.So, if you want to improve the quality of the documentation,we can contribute.So, yeah, I think it's a challenge,but our next step is to contribute to fabric documentation itself.So, after completing the translation,yeah, we can propose some improvementsfor fabric documentation itself.So, yeah, I think it's a good contribution from our side.Yeah, thank you.Any other comments or questions?Generic question, I'm sorry.I have questions because we work in Japan a lotover 20 years, kind of from the standard of culture.So, what is the main issue in introducing morelike a hyper-logic technology of working in Japan?So, it's more generic question.Oh, thank you.You have an idea?Okay, let me go first.So, I think it's similar as a language.You know, we have many political concepts,but we have only a full production level services.So, you know, what is the root cause of its issues,but it's helpful as to go to the production level.So, it's a combination in Japanese production world.You're welcome.Thank you.You have any comments?Actually, in terms of technological documentation in English,I think it's not enough to build like prototype hyper-logic system.So, actually, it's not technological problem,but, you know, English documentation is also important, I think.So, I want to community to improve documentation contentsmore deeply.Thank you so much.Standards that all the documentations would followso that it's easy to translate it to different languages.Just like we talked about some standards,shall we have those standards when we make documentation in English?So, it's much easier for you guys to translate it tothe language also.Thank you.Yeah, I think it's a good suggestion.So, I think we can share some levels.So, yeah, we can standardize at the sub-levels becauseconditional process and terminology are common problemsin other languages.So, I think it's a good idea to share knowledge betweendifferent language groups.And they can also customize some points to improvetheir all-language specific problem.Yeah.Thank you for your advice.So, digitizing the documents, like I've been workingwith some organizations who have like 40, 50, or even 70old documents, which are still relevant for them.And they wanted to digitize them.So, as part of the deal, which is many challenges.But one thing that we understood was, if we weretelling on the same point, if the documentation, when itwas done, it followed certain principles.Like, this is the format, this is the form.This is how a paragraph should start.If it followed those things, then the job was veryeasier.The same job that would take someone a year could bereduced very well to a month.12 times or 15 times, you can reduce that if the documentation was done in a particular object.So that you can build tools and reusable components,which can actually stand through it, which can actually read through and find out, these are the documentation marks.These are the sum of the headings.So all those things it could figure out.So that was my experience of NEO.And we did about 4 million pages.We converted 4 million pages of different books and different formats into a very specialized XML format.OK.Yeah.Thank you for sharing your experience.OK.So thank you for coming here.We got a very good feedback from you.You appreciate it.Thank you so much.Thank you so much.