 Okay. Umar, the live stream is up. Yes. So just change the screen. And I'll be on the line tomorrow, but feel free. I mean, you know, speak in French as much as you like. If you need anything, just ping me. And I'll, you know, I'll be here. We effective. Thank you, David. This meter will be in French. Okay, so I'm going to let us I think. We'll have a little pain in the search. Okay, so the live stream. Um, so I'm going to have this. How am I going to say that? It's a meet-up to start a little bit the activities concerning the tradition and the activities of Hyperledger Francophonie, to start all these activities concerning the French language, whether it's about the tradition, whether it's, I don't know, well, the translation of the document or the translation of the website properly said, because the city-hyperledger.org also, at the moment, maybe it's interesting to be able to translate it. So it's in that sense that I launched this initiative. So here I am with some people with whom I launched the initiative, Hyperledger Francophonie, especially Gilles, Gilles Gravier, who is one of the first to take part in this initiative and who supports me since then. I also have the support of my brother, Ido, I.D., rather, who is a French-speaking Englishman, but who used to be there to explain this to me. So hello, I.D., how are you? OK, so I'm just preparing a few slides quite quickly, well, it's not really a slide, it's just that it's going to be more in-house format than in-house format. So I just have to find the link to share on the screen. David? Yes? I'd like to share my screen. You should have access. Is it letting you? Access to some security measures. OK, OK, got it. I'll share the screen. OK, that's that. Yes, so the first thing is just to welcome you guys to this. Ah, pardon. I wish you all the best. And that's what I'm going to say here. And so as I was saying, the communication methods are quite basic. So what you need to know is to use the documents, the logistical documents, whether it's Microsoft Word or LibreOfficeWriter or Google Doc, these are things that more or less everyone can do. The other thing is to have a good level in French, because that's what you need to do. You need to do documentation, but you also need to do something that is of quality. But I think that for most of the people who are there, these prerequisites are here. So I didn't put the other prerequisites, which might be to say that you need to be bilingual, because it's not quite true. And we don't have to speak English to help translate. So I'm explaining myself. Sure, you need to be able to start translating, but there are several mechanisms that we'll see later on, automatic translation. So that's what I call the first steps. So the first step will be an automatic translation by a mechanical machine. And the second step will be a re-selection by human beings or by people who master the Francophone language and who will be able to detect all these errors generated from context, often generated by automated tools, because they don't have the finesse that humans have. So we really don't have to be bilingual to be able to participate in the translation of the documentation. So there are no two points. The two points are to use it in the logistical of text and to have a fairly good level of French, whether it's an orthographic or a grammar. The other thing I wanted to show you is this page that we created in September 2020 with Gilles. So it's a page in the Wiki of the French documentation. And so on that, I'm just going to share the screen so we can see how it's going. So here it is on this page of the Working Group. So as you can see, I put it online by adding the links that I'm going to use throughout this meeting. So the links serve a little bit on the documents that are in English, but that give the steps to be able to start this process of documentation. So I've already opened them here. So it's not worth clicking on it. Maybe David, you can share the link or maybe I can do it somewhere down here. Oh yeah, when you're sharing your screen, the interface goes away. Yeah, if you click at the top, you should be able to see an option. But I can drop for the documentation working group. Yes, just a little discussion. Yeah, I got it. So the link is here. If you want, you can click on it and see at the same time as me. I had already started with an EPAC on the Translucent Initiative, but we haven't been very far. So here are the pages that we're interested in. It's very, very well documented, the translation. So there is a page of the introduction that is here. So the link is here. The links are there, so if you want to see them at the same time as me. So it explains a little bit how the file structure is decomposed. So the structure is here on the hyperledger link, FabricDocAitinen. So this is a notation for internationalization. So here we are on the local doc, which is the FabricDoc source. So here we have the different translations of existing documentation which are the Japanese, the Russian, the Portuguese, etc. So here it's up to us now to do, so that we have the FR underscore FR here to start our activities. So here we learn that the most important files in the source, they are in the source, and that's all that concerns how to create channels, etc., etc., the different elements. So here is the documentation to translate, and it's quite simple. And there are also parties to build, to build this documentation in local to be able to see live the translation that we are doing, how it will be presented on what will be the online version, definitive and accessible for everyone. So on this part here, which gives us the initial process, create a new workgroup, we did that, which is here. So you can, if you already have it, you can edit the wiki and add your name here, it would be nice. To get to what we can, to get to what we can, to have a beginning, a micro community to start and then in the end, to try to enlarge it. So on the first, create a workgroup, it's done. Then there is Hyperledger disposed of a chat, a big chat, which is, well, on Rocket Chat. And on this chat, there is, no, so I just opened it, there is a channel, a channel called Internationalization or Aetinen. So on this channel, we have a lot of messages and eventually we can discuss the elements of tradition. We can also see what the others do and ask for advice. At least that's what I do with some other people who are in the tradition of other languages. I often ask them how to do such or such things. And that's, that helps a lot. In any case, for the beginning, it really helps a lot. Then, then you have to really put yourself, that is to say, make a fork of the documentation against Github. Once again, you don't have to, on the priorities that I mentioned earlier, it's not the point of being, we don't need to have a technical profile. So everything that is Github is accompanied, if you don't master it, it's not absolutely necessary. I'll explain why, in order to participate earlier without having a technical baggage. So that's for the people who really want to do the tradition from scratch, apart from their machines that are quite technical oriented. So there are the elements of committee, of push, of push, of fork, so they are quite good. So there you go. Once we have put this environment on our machine, we will have to start somewhere, the real work of the tradition. So there are also the first topics, that is to say, the first elements that will necessarily have to be translated before our French language is visible here. Before the French language is visible here, because it is useless to display a French language or a tradition, whereas there is not even the minimum, the minimum being the welcome page, because there you go, the welcome page. It has to be translated, otherwise it's useless. Then there is the introduction page of the initiative and the factory. Then there is the page that explains how to contribute, because that's what we have here. It's to contribute, to give back what the open source gives us, to share what we have at least, what we know how to do. Then there is the glossary, which is also important, because there are many people who help to have a point of view, to know what a smart contract is, to have successfully entered the documentation, the real big documentation, there are people who want to know what the consensus is, so all of this, the glossary allows us, as the name indicates, to detail these elements a little bit. Once we have these four basic elements, we can ask what our language can already be validated and displayed on the real document, the online documentation and the hyperlogical address of Doc Ayo factory. From there, we are very successful. We have arrived a little, we have put our first stone, so from there, we can firmly click here and say that I have brought my stone. Then the other thing is the translation tools. We have tools that allow us, I was talking about mechanical translation, so we have Doc Translator and Textra that are there. So I'll show you a little bit how it goes, which helps to make the first step, an automated translation, because we will not translate it very much. And from there, we are live, and we can attack the topics or the subjects that are suggested here. So also the other important thing that I wanted to emphasize is that we are going to start with the release 2.0, well, 2.2 of the factory. Why 2.2? Because currently, with version 1.4, version 2.2 is the stable version, the long-term version supports. That is to say that it is the long-term version in French. And on this version, the 1.4 and the 2.2, on which the hyperledger factory for developers and for network administrators, network administrator, hyperledger factory and hyperledger factory developers. So it is better to attack these documentation knowing that this is what people will most consult. People who, like me, want to try to have these certifications, they will really base on the LTS, because the LTS, as the name suggests, does not change very often. So the documentation, too. It is stable and fixed. And from this base, we can elaborate on version 3, well, 2.3, 2.4, etc. So that's what I had as an introduction. I don't know if Gilles, you have anything you would like to add or if there are any questions before I attack on the demonstration part? Yes, I will make a comment, Omar, not so much on the method, but on the ideas behind it. Contributing to an open source project, it is not just code, indeed. And many people start their contribution to the open source project by translating the documentation. The advantage of the documentation, as this is the case here, is that we really don't need to be technical. As Omar said, it is enough to be able to use a text or a text editor, and then it's good. While there is another aspect of the translation that is not bad, it is to translate user interfaces, which is also done with text editors. It's not much more complicated, but that makes sense. It's less important for a project like Hyperledger Fabric, which is on a server and for which the user interface is generally quite restricted. It's super critical, for example, for a product like LibreOffice, but what we propose here is really something that will rely on elements that are not very technical. You have to understand a little what we are talking about. But you don't need to be a programmer. That's it. Anyone can do it. Very good. That's exactly what I said. So it doesn't really matter. You don't need to be bilingual, you don't need to be a technician, you don't need to be a NAS. That's it. And then, from there, I can... Is there already questions on... No? Okay. So I'm moving on the approach that I would like to propose here. So I would like that once we have a small group of volunteers, it can be two or three people, we have to start somewhere, that we can take an hour a week to meet and start a translation. So starting a translation is quite simple for me. So once we have created the workgroup and all that, we can come here. They are open to start. That's it. So first topic. So with the tools explained here. So we have DocTranslator and TextExtra. So I tested these two automatic translation types. So I'm just going to start this translation of the approach page. No, not in Chinese. I'm going to take the English version. That's it. So the English version in 2.2. And from there, I have two choices. So this first tool is DocTranslator. And the second is TextExtra. So it's a Japanese tool. They have an English version necessarily for a translation tool. That's it. Then I connect. So quite simply I come here. I type on the introduction page. So I can copy all the text that is there. I just copy it here. English, any language, English, French. So from there, I just have to do a little bit of networking because since I copied everything there may be some small elements. There are especially the images that are copied in text format. The links especially of the images. So that's the title. That's a list but we'll see that later. The night is coming. So English for French, we launch the translation. I think it's translated maybe by little. So there I don't know what's going on. There you go. It's translated by little. I don't know why. That's how it works. So there we have a parallel between the English version and the French version. So there we can see that the translation is pretty good. I find myself on what I tested. So a block chain is an immediate translation book without distributed networks so apart from the translation here this is what I call the first step. So we can copy this translation and paste it in a Google Doc not now. So really very quickly there is work that we can do here at this level on certain elements. We can suggest better translations of the group. As I propose, one hour per week where we regroup we can regroup for all on the same document and from there one takes the end the other takes the end it starts at the top the other at the bottom doesn't matter. And we correct it. Here it's more of a collection but a block register for example it's a good French word for example it's a Google suggestion which is false for me for me the translation here is the good term we classify it. These are the things you need to see So there are things for example, what do we do in English? Anti-money laundering anti-blanching of money do we keep them as they are in English or do we translate them in French? These are questions to know the notions of KYC which are also elements of what we do on these elements of course there are some small mistakes So the translation is really something that allows us to have a lot of documents on which we work and once we are satisfied with the results, we export them and we move on to the technical part of insertion inside the original documentation So it's fast There is also this doc translator that we can also try So on the other hand, we can't copy and paste directly we need to create a text file or something else, PDF or whatever but we will have to file it I don't know, maybe it's me who can't find the button to paste but I didn't see a place where we can paste So we just test 3DF So we put it there we register So from there we load a file So as you can see it uses Google Translate which is a little less accurate than the Japanese one to take the document translated in general we also have a starting element to copy it in a shared document to be able to work all on it in parallel So this is the first part which is the translation of Mechanic and after that we will have to re-read it until then do you see everything well for everyone? No questions? So in this case I will go to once we have a raw translation a little re-read, correct and clean for example smart contracts and a chapter obviously we will have to respect the original form but this is not very complicated So once we are there on I have to connect So there I am on the global documentation So there we are on the release 2.2, you have to check that So the first thing we do is we clone this deposit So I clone it under my name and there I have my repo my personalized code of Deeperledger So the second step we are really on the technical part but we can collaborate on Google Doc and someone who has a technical profile can do everything that is integration in the main repo of Deeperledgerfabric So there I will clone my own deposit which is something quite simple but first I have to do one or two operations so I activate my key here then So I clone my deposit and from there the only thing we have to do is to come here and start reading the code So I go inside and everything is already very well written then then so we are on the 2.2 branch so we create our own branch we will say initialization so I am on the initialization so there we say we have to know which language we are so we are quite simple French from France not from Quebec after we have to start once again so code honor we are already we will see what is on your trick and so we say to add this line to the code so we have to do that and modify the extension of the language so there we are on the FRFR and maintainer FRFR so quite simply but it is things that we have done only once, that is to say that once for example I do it and I put it online you no longer need to do it the the FR language is added we will just add what we will add in addition to the translations not the basic elements so there so if we put a if we put a disc on this file we will see that we have added the language in any case we said that we will add in the local file the FRFR file to sign a new translation from there we also have a new file called DocMaintainer which will regroup all the people who participate in the translation so that's maybe some elements of the knowledge that can be very interesting to show your involvement in this open source movement in the give back as we say in French and so that's the first part so I'm not going to do everything from beginning to end because I already tested it so I'm just going to cheat a little and copy it's behind and copy the elements that I already created so I already created a FRFR file I copied it in local doc and so what gives rather a vision of what we have so we added the FRFR file which actually contains it's not very complicated I just copied the content of the English file because it's the language of reference so I copied English to French but all the content in any case it still remains of the English elements you have to go again and once the base the elements of the base are put in place then we're going to replace as the translations so we're going to arrive like that then we have a suggestion to copy the Brazilian Portuguese to the Spanish-Mexican for example the customized personalized the rhythm to specify to specify to specify what it does etc so here we are so I already did that so the French translation project the perimeter of the initial commuter so here I put my name and obviously we're going to have something that will increase Gilles I can add you you're in mute so I was saying don't hesitate okay cool so I'm going to add your name so if it's just Gilles it's Gilles.Gravier.Weepro.com if you want my mail weepro or it's Gilles.Gravier.org okay the one that corresponds to my github Gilles.Gravier.org perfect so that's what we're doing and then here we are haha so here it gives us a base of the initial contributors and so now what we need is obviously the standard principle a guide art, a guide commuter blah blah blah blah so since it's the first time I've added absolutely everything and here I made a guide commuter type m so here you have to be very careful my back is a little bit dead and I don't like to fall in this trap so I've been a guide for a long time but I didn't know that so this is the first time that I meet him but he's vital because if you make a commuter that you didn't put that it won't be merged in the main repo that is to say this is my field DOC only accept the contribution of the developers who signed an NDA or CLA to say that the code that I give I follow the owner and I know my right to use Hyperledger to do what he wants so it's really a lot of things that the commuter doesn't use especially the developers the agreement of the developer that this code is to him that he doesn't use it and that he has the right to give it to the project so that was what we came and on the interface we hung it on a case and it was quite hard so the people of the guide I'll just do that guide help and we'll see here so here the shooting is somewhere somewhere that's it so here it is it's really a kind of quick signature to say what I give and to me origin so if you need more information you can just do a guide help and read the documentation so if you don't put it it won't work once you have done your push and once we're going to do a merge request so very very important so once we put the S to sign our commit we put our message as an initial commit so it's done and from there we can make our push but once again the push stays on our branch on our local depot because here we have we have copied our I've already checked on which branch we are we'll just do that and replace by initialization so here that's it the push is well done so what we just did is so fork the depot that's the basic element that is to say we click here we fork the depot, that is to say we get a copy on which we can intervene because we can't just come on this main depot because that's it and so we approach this depot by making a copy and once we have done the copy the copy we do this work all that I just did is not to redo because once we have created the FRFR file we don't need to recreate it it doesn't make any sense so we'll just go to the FRFR file to take the elements for example so once we are there we'll just go for example to take a network test to open it and start to translate it so I just we copy that we translate it automatically here and if we have two or three people we share it in a Google Doc and all that for maybe an hour or 30 minutes and once we are happy with the result we come back here and we paste the content and we put the markdown balises that we come with so if the markdown balises it's a markup language it's a balising language a little simpler than HTML so it's a title of level 2 so it's a title of level 2 it's this kind of thing so it's a title of level 2 so if we put a a simple 10 it's a title of level 1 so it's this kind of thing so to make lists we draw non-ordinated lists so markdown simple so that's all I said I don't know absolutely nothing so once we put our code I'm looking for my navigator here perfect what is this who tells me to visit this thing so what does he tell us so there's nothing to compare so maybe there's a merge and a branch so I'm just going to change the branch so all of this it looks a little complicated but it's not there are graphic tools to do that I like to use my terminal that's it once we have that we can start merging work so here it doesn't merge but it's a pull for quest so here it detects that there are changes that are made there's a difference on the original FabricDocs and comparatively on my repertoire so from there we can create the pull for quest to ask for what my work is merged with what is on the main branch so here with a reminder it's a reminder that he says what's in what's in what I want to bring and once we have made the merge request the validator looks if everything is okay everything is in place and from the right there should be no problem to merge what we just did so here it is there's only that and even that it's really put in place after once everything has been put in place it becomes easier and easier because as I always say what is done is no more to do so from there I think I just was there and you put your hand for the most important part it's to ask everyone finally everyone those who are there those who are ready to participate in this embarked adventure and so it's all for me so thank you for your participation so I'll tell you how to say it so I now it's up to you so I'm starting I nominate you I nominate you I nominate you I nominate you and all the rest here on YouTube you're welcome but anyway the planning is really on there one hour per week and then we decide together the collective hour and day and then those who can be there will be there and we all work together to try to put more visibility to the French documentation because that's something that's missing a lot because since I manage a Francophone community there are a lot of elements that go or activities that people on which people can't to which people can't participate and on which they can't come because it's in English and it's a bit of a shame because on a technology like the blockchain really I would really like that our young brothers and everyone can have at least a documentation at least tutorials in French at least sessions or workshops in French to be at the same level as their English brothers because the language barrier of the language exists on the other side English-speaking people don't often see it they mostly see, for example we talk a lot of diversity we talk about men, we talk about women we talk about racial minorities but often we don't talk about linguistic minorities if I can say because the French language is beautiful and everything is done today in English in Chinese we try to write even the French themselves they write in English because they know that everyone now we have to say that there are people who exist in Francophonie and we have to think about trying to join us to you there is no more just regular meetings to make progress yes so I really like the part of each one of you and that's it so meet on the wiki so there is no emergency the wiki I put it back for those who were not there and so from there you just realize and you sign you say that you want to be but I will try to do it so that's it but you can put a mute and discuss there is no constraint you can open the microphones there we are on the science chilling out Kevin we don't hear it doesn't work it will be better it works thank you hello good evening and thank you for the presentation I just had a question a little detail about the TIRES that you have to add to each committee please and it's every time that we make a committee that needs to put the TIRES yes so each committee must have the problem I had is that I made a committee with the TIRES a committee without forgetting the TIRES and another committee with the TIRES so he said to go to the committee of the environment to modify to put the S to be able to merge all these problems so it's very very boring once we forget if you forget it on the last committee it's okay you can just do a guide committee and it will simply change you but if you forget a whole pile there it's a little more sure so okay thank you for the precision I didn't know about the TIRES neither did I and it's quite interesting thank you Serenia Sen who has already created the Sien so I imagine he's talking about the UNIX Foundation to access the Wiki thank you Seren so I have to go back following the link of the Wiki we connect and we have to send it to the identifiers when you add us somewhere if I want to participate how is it going so once you are wait let me see Wiki sorry to make you repeat no no not at all with pleasure so once that once I have your ping so I put the links on which I was so once you have created account identify and arrive on this space there you have the possibility of editing because it's a Wiki everyone can modify you modify there and then there so you modify it you come there you make a tabulation and you put email that's it so ideally you can say what you did here and click here to update me and modify it, that is to say that everyone receives your email otherwise I will see it because I am subscribed to this page so I will see what you do before what happens here so that's it and once I in the end of the week I send an email, create a small group and then we start the activities as simple as that ok thank you thank you so that's it I do not know if maybe Gilles you want to make do you still want to dispense of your sages speak to click listen no I think that I have already made the remark that I wanted at the beginning in addition I have a video conference that starts there in a minute that will be especially thank you very much Umar to have put the call today and then there to see the first contributions it's a good opportunity to contribute to a project which makes sense, thank you thank you very much and I leave you here to join my other video see you soon and the others too so I go to see because I do not want to waste your time David is here no he is not but anyway it's not so I want to thank you all for coming because after there was only the link of Zoom so I apologize for the advance and I would like to thank my brother ID from Nigeria he is very supportive of what we are doing here in Senegal and in all the other chapter of Hippology so I would like to very very very thank you very warm thank you to ID I I just want to see that there is a link on YouTube there is a question that just asked me I will share with you Simon Deve who says thank you do you see my screen so there is Simon Deve who says thank you for this initiative how can we develop you I am not sure to know what you want to say maybe you want to say develop on Hyperledger Fabric well develop and develop Fabric it is very complicated to read the documentation and I do not know to participate in the workshops to try to find a mentor it is a bit like all the technologies that exist you just have to launch and then you have to know the terminal in any case if we want to develop as a network as a network manager to know Docker because it is especially what is initialization and blockchain network development on Docker containers and that's it and then you have to have JavaScript if you are a JavaScript developer write the names if you are a Java developer if you are a Java developer if you are a Java developer you can contact me my ID my handle that's it so that was all for me thank you again for coming thank you for your participation see you next time guys see you see you thanks a lot