 Hello, hello everyone. Hey, I just wanted to check that I wasn't missing any conversation. Yeah. Yeah, I think Bobby is waiting for people who want to join. Right. Hello Bobby. Just talking for five minutes on the. Sorry. Okay, perfect. I've gone through the meeting already. We're, we're, we're well into it. So let me start again. Hi everybody. It's the documentation standard meeting. We're getting started a little late here because of technical difficulties on my part. Today, Arunama is not here because she is doing something to complete her master's program and we thoroughly support that. But together we have tried to organize this call so that. We can achieve the objectives of the documentation task force slash mentorship documentation. Initiative for this summer and into the fall. I am right now where this group is, is that it started as a task force a few months ago. We analyzed the documentation. Current situation in the environment and hyper ledger community. We've broken out into subcommittees where we feel that that documentation. Is categorized by because it's a huge, huge community, huge amount of information and trying to get it. So that all of the maintainers have easy access to the resources they need. Users have easy access to the resources they need and community contributors know exactly how to get on boarded. To the community as well. So again, we'll go over the subcommittees in a minute. Today's call basically we are kind of regrouping and looking at exactly what our deliverables will be our deliverables. Again, our suggestions for what the community should do what became interesting. So we broke out into the subcommittees. Best practices, get hub templates, get hub read the docs, regular community templates and onboarding with user guides being something that runs basically through all of those things. It became very interesting. Again, one of the things that we're going to do as an end result of this committee is we are going to do a lot of presenting our findings. Mostly at the global forum, we will present our findings to the entire community or suggestions on how documentation should be accomplished. First, we're going to do it through the TOC. They're going to either approve our recommendations or not. We will also be presenting this to the Linux Foundation as a whole, because during our research and analysis phase, we came in contact with Richard Reeves, who is the head of the Linux Foundation Strategic Development Department. He is fascinated by what we're doing, especially since we are trying to, or we will like to be positive, incorporate current AI tools into the documentation workflow so that it's seamless, easy, and everyone can create the same excellent user guides with the same look and feel and consistency that makes Hyperledger Standard the finest in the industry. So that's basically a caveat, like an extra bonus for our little task force, is that we're not only going to presenting to the global forum, we're going to presenting to the Linux Foundation, to the TOC, and also to the global community of meetups. We're going to organize a meetup to present our findings as well. And the more we can use AI in this process workflows that we suggest, the better off we are. So we've had great people step up to chair the committees, two people are on the call, Kojal and Gianluca. We're going to go through a round of introductions, and then basically we are going to kind of regroup as to what the recommendation deliverables look like for each one of the subcommittees. So Gianluca, if you'd like to introduce yourself, that would be great. Yes, yes, thank you. And could I share my screen? Absolutely, hold on one moment, let me stop sharing mine. Okay, thank you. I have to find my zoom controls. Okay, go right ahead. Okay, thank you. I'm sharing the screen because I have also a short presentation. Okay. I think this is the whole logo. I will change. Okay, I'm Gianluca Capuzzi from Italy. I'm a software engineer. And I'm the chair of the subtopic GitHub template. And I prepared these few slides for talking about how I'd like to contribute to this project. A beautiful goal for my in my opinion should be to integrate an AI tool in standard documentation. An example could be chat like chat GPT GPT engine for natural language processing. For example, if we have a chatbot that can reply to our answer about documentation, this could be an example. If the TOC or in general the average team will approve this idea, I could go ahead with it. And I in the previous presentation, I expressed my interest in investigating this in investigating this kind of tools, the GPT tools. And some of them are free in a face community website, but also there are other website and other communities with that are working in this kind of engine. And I said a bit the GPT engine and I discovered that the technologies, the background technologies in this kind of natural language processing system are the recurrent neural network and the generative adversarial network. Okay, so now the last week I studied this kind of model. And I also implemented an example using the IMDB movies that are set. The ideas is very, very simple. If you want to see an example, I can I can show you. And the example is very easy. I trained a regular neural network using this movie, and in particular the review of that movies. And now the system is able to classify if a new review is good, is alike or dislike. I have an example here. The system is already trained with the data set. It takes about three hours for training for the training stage. Now I just load the system with the existing weights, the existing parameters is written in Python programming language. And the system, this is a short list of the architect architecture. And it asked me a comment. And for example, the movie was very bad. And he replied me, it replies me saying that you don't like this movie. So I can test the system using another comments, another review. For example, I like it, but it's not good. I think it is another because the number result is good. I think it's a wrong reply. Again, I like the movie. So it's not perfect. I also tested the accuracy. The accuracy is more than the 85%, which is not the best result, but it's a good system to be studied and to learn the technology. And for the next week, I'd like to investigate the generative adversarial network, which are the second technologies and model as background of GPT engine. And in the meantime, also, I'm studying, I'm having some course on GitHub. And also I'm finding the open source GPT engine. So I think I pretty finished. If you have questions. Okay. I also found some other documentation on how GPT engine works, and I think that it's possible to train a system like chat GPT with our existing documentation. And it will be able to reply to our question. Sending us, for example, the answer about how to install Hyperledger tool or with also the comments on Linux and other kind of replies. So I think it's possible if could be, if you agree Bobby and other people on the team, I will continue to in this direction to investigate if it's possible also to share the code and the documentation that I found and I am writing at the moment. Absolutely. I'm going to open. I see that Rama has a question. I'm also thinking of where this would fit in in our documentation. I'm going to let Rama ask his question first, and then I'm going to ask mine. So go ahead, Rama. Okay, Bobby. This is interesting. I mean, just a simple question. I just wonder if you can use these techniques to automatically create an FAQ page. Because that's one of the things which I think many document writers struggle with, you know, you can you can write all the documentation you can think of but how do you populate the FAQ pages so just wondering. Yes, I think so, because the GPT has this ability from the generative adversarial network to generate information data that could be an image or could be a text and depending on the training set that we use to train the system. So I think it's it's possible. I'm at the moment I'm writing this, the code for again, using the Google collab technology. So in that case is the system is in the cloud. The previous example is Python code on my laptop. And now I'm I'm implementing again in Google collab in my account. And after that, the next step could be to start with GPT, especially GPT open source system. So this, I'd like to go to it. Okay, I don't know if you have any other question. Not right now, but thanks. If I can pick up anything else. Okay, thank you. So Jen, let me share my screen for a moment. I want to show how I feel this is going to incorporate. So this is definitely, and I know Kajal's on the call as well. Incorporates with our, let me share my screen real quick with more of the, this kind of thing to me like the FAQs is more of a onboarding thing, which we do have a committee for on the task force, which she's not here today, the head of that but what I was thinking is, so this is, let's just go here first, like this is the new website it's beautiful it's gorgeous. You see about there's members governing board charter projects all the all the labs all the projects participate. This is like joining. Learn and use are confusing to me, because I think learn case studies use tracker webinars white papers excuse me a second. Sorry about that. I think that's all like great and useful information, but I agree with Rama, it would be great if under this use. There would be the first button of ask a question. Not even FAQs because we want again like what you've shown this robust system can handle if we can train it with all of our user documentation to have that button there. And in your own language say, what are my requirements for setting up a fabric network on a Windows based system or a Apple based, you know, like that kind of thing so you could ask it in your language and it would give you whether it gives you a chat GBT curated answer or directs you to write to the GitHub repository read the docs. I don't know how that works. That's something that we'll have to figure out how advanced these natural language models can be. But that's where I see it and I not only see that FAQ button or whatever asked me a question button library button whatever we call it I see it here. I don't like I is these frequently asked questions are doesn't get anybody anywhere. I mean it would be hit or miss if these questions actually answered your question. It would be great if there was a button where you could just type in your question. So that's what I say and I see it also on other other sites and like all the others you know there's four other places, people on board into the community. I see that button on all five. Does anybody else have any thoughts on that? No, I, if possible, I try to to have a short answer about your, your, your question. So far as I know is already possible to use the chat chat GPT API to do that, but I'd like to investigate if it's possible using open source GPT engine other other engine, which are open source. With using the chat GPT APIs. Now we see I think it's already possible to train the system with using our wiki and it will reply with the right answers. We also can integrate the system in our wiki, but I don't know I think could be better also to try other open source engine that could be integrated more suitable in our, in our wiki. And once we have like the recommendations down in a presentation to give back to that to give back to Robert Reeves. He was saying that he is going to be interested in investing time and resources of the Linux foundation to, you know, model what we've done for the rest of the community, and invest in possibly some of the tools to get them where we need them. So, again, this is wonderful information for this is not working. Okay, I'm just going to update this. So that's great. Thank you so much. I would say keep investigating that that that's the way to go. Thank you. Thank you. Oh no thank you you've done such great work. So continue on I know ramen you'd briefly had a question but you want to introduce yourself and why you're interested in this task force. I actually had put my name on this task force the beginning of the year but I didn't get much time to join activities sorry about that. But in the last hyperactive to see meeting and just for everybody's knowledge I am one of them like Bobby I'm a member of the hyperactive to see. I lead the project badging and life cycle task force which is just getting started to investigating whether or not projects need badging to indicate how they're what the current health is and at what stage of the project life cycle they are in. So, Bobby suggested I joined the meeting of these of this task force to and because there's some overlap between what you guys are trying to accomplish and what we will need to figure out the right metrics to to call out for a project sales. Thanks. Shinji. Can you introduce yourself. Okay, we'll move to cause off everyone. Bobby first of all, a very congratulations. I'm very, very happy for you. Thank you so much. My grandson is so adorable. Maybe that's cute. I have a few questions. Like you showed us the website the new website of hyper ledger. So, like the theme is standard for all the documentation website or the project can use any like team color or one because I was thinking like I saw the documentation website of many graduated students like fabric and they have different different teams like the color and the point and like the accessibility and where the this button should be where the content should be like all have like they have like all projects have their own projects. So like I like I am the, I am working on the template. So I would like to ask you that can we like create a template standardized template for every project. Or like the template would be same like the hyper ledger new color team is like green green shades of green. So like I was absolutely that could be our recommendation. Yes, because like I think that will bring the uniformity to the hyper ledger foundation, like anybody then any new user when came come to the website, they would like to see like uniformity everywhere like the point thing and the, like the content like we have about the project participate this in hyper ledger a foundation. So like I would like to do the same thing for the documentation thing like I have talked to the caliper caliper maintainer. So he asked me to like improve the accessibility of the caliper doc. I would share you the link of the dog. I'm sharing my screen. No, I'm sharing the link. Okay, in the chat. Okay, here we go. Yes. And I think, Ram. Ram has a question. Good clarification. I was suggesting that all projects follow the same menu or for uniformity or do you want them to all use the same color combination. I'm not sure that is really nice. We want the uniformity and uniformity we get the same color same font same team and same font style and also the same like menu because like the caliper website is different. So like it shows that every project have like like as a user perspective what I thought is like every project has their own documentation and like they are working on like I was thinking to like it will show the unity thing. I like in short, I would say because the caliper has users, it's like the color combo which is like purple and all bevel is different like so I was saying this. So do you want also the different logos of the projects to somehow follow a particular color theme like you showed you had fabric fabric logo just opposed to the bevel logo and they had somewhat different colors one had purple one had red and green. Is that something you want to make uniform as well. We can like if we have changed the hyper ledger foundation logo. So I guess we should also modify the other other project logo if we can. Yeah, I'm not sure if that is possible for us to modify the logos. Only because that's like a whole. So I basically what I was just thinking was like again, like maybe taking it like when you said color coding like basic would be the documentation could be all in this color firefire purple that the colors that are in their logos already. I would use just just for guidance is great. That's a great idea and I would definitely so let's just regroup for for just getting back to the test because the new website is like very user friendly and it is also attracting the user. So like they're in the joint but then they have also given the bottom shadow. So like I was saying like we can use the same template thing for the project documentation, because it would bring the uniformity thing also. Well, again, I can't say enough about how much I like the new website it is really well done just this is gorgeous. And also like the user experiences. Again though I do think that it needs in use and learn that button with that AI engine that just answers your question I mean that would be a home run for this group if we could get that recommendation somehow defined. I really think so anyway so let's just regroup real quick because I know we only have a little bit of time left on the call so the documentation task force now we've done a lot of stuff we've gotten our name out there. People are interested in what we're doing. So again with these task force. We're going to do best practices last because we have from on the call and it's probably going to be the most talked about one so far this in this call. So to regroup the GitHub templates what we want as a deliverable is a suggestion, and I have an email to Tracy I want to meet with her this week to discuss what she thinks and I will put that out to the group for everybody to join. What she feels needs to be in the GitHub repository template for the maintainer so this is the templates that again through the project life cycle. What template would a maintainer need at that particular stage in the life cycle so if like for instance, Jan Lucas open source project about the chat GBT maybe that needs to become a hyper ledger lab. Where would he look to get the template for that what needs to be in and I know we have one in the community but it's really difficult to find again organizing that so it's easy to find in our library. Having a maintainer come in or like for instance Jan Lucas come in they okay I want to put this up in a lab so that everyone in the community can help me with this project. So what do I need and clearly the template would be there same thing when we're done with this great lab discovery phase, we want to put this project into incubation. What does that GitHub repository need and tied into Rama's group of best practices, when would badges be earned for those and again we're going to get into that in depth in a minute. Same thing with the GitHub read the docs that we need to define we know what everybody's using it's all over the community. So we need to define, we're going to have a meeting with David Boswell to define what each group suggested they're turning their repositories into user guides again with our color code whatever we want but how is that going to be uniform through the community. I'm just going to give them choices we want them to have but still give them choices. I'm just going to have to pause for just one moment and I will come back just give me one second. I can't find my controls. One second. Okay sorry about that. So the GitHub read the docs. We've done is this. So we've done an analysis of who's using what process for the read the docs. Let me just see if it's here. Sorry I tried to avoid the dog barking but it didn't work. Excuse me for scrolling so fast. Okay. That's the mentorship programs. Here we go. So this was the analysis of what's currently in the environment and what people want. So as you see for turning your GitHub repository into usable reader usable guides for people to be able to use the product people are using different things they're using Sphinx they're using read the docs make the docs. Some people are using again so it's all over the place. So what we want is we want to be able to provide the community with suggestions for taking their GitHub repositories and making them into user guides using again we have paid tooling policies one of them is the make the docs gives us extra bells and whistles. So let's look down with David and find out what they suggest. I am not sure if we even need programs like Sphinx and read the docs now that we have AI engines who can take a GitHub repository and make user docs we might be able to customize these processes ourselves. So I'm not really sure how that looks but that's what we have the rest of the summer figure out and into the fall. So we're going to come up with suggestions for the entire community so this is uniform as per the survey we sent out that's the main thing people want they want it. They want a choice of visuals they want it more to be user friendly. I know that I have spent more time monitoring the forms for for Hyperledger it takes more time for me to load the class up on a system and get the artifacts up and get the Docker that just takes too long and it needs to be easier in my opinion. Before you even start using and defining your organization it shouldn't take you more of the class to get set up. So that is again something that this committee will be trying to get that GitHub repository more in a usable format for people to test and decide if this is the way they want to go. So that's read the docs and these templates are just community templates. So if I am a business person working in trade finance on their special interest group and I want to write a rate paper. I want to have batteries running well hold on a second. I want to be able to supply the community with templates for white paper so that they don't have to spend half the time searching for the easy template to fill out same thing for white papers use cases. They should all in the community be kind of the same. I see Rami have your hand up is that from before or is that for now. Oh no I was you're talking about the different tools one could use to build documentation so just I was offering a data point because Tracy had a template documentation using make docs. So I was I'm actually in the process of finishing creating a character documentation using make docs with using Tracy's template as a guide just to note that cacti has both cactus and the Viva lab and cactus use things we will have used documents so we're just trying to integrate them using what Tracy suggested. So yeah I mean if you if you're if you use make the docs or make docs that would be perfect for us it'll you won't have to do any trouble but yeah I'll be watching out for whatever it is you recommend. Yeah yeah that's she yeah definitely make the docs is the one that we want the community to use at this particular point it's the one that we pay for it's got again it's all ready to go we want to encourage that what this. Subcommittees is charged to do is give a user guide for that so what you've just done we need a user guide for people so that they can do what you've done for their project really easy so they don't again have to reinvent the wheel. So if you would like to just jot down on this page edit this page and put cactus make the docs steps step one put a link to the template step two you know hit this but do that step three publish and let people know like whatever that would be great to get us to get started because what we want to do with this is we want to introduce this as soon as possible to the mentors who are creating documentation for their project so that they use this the recommendations so this one almost has to be done as soon as possible so we were going to definitely but again here's a question for the people on the call. Do we think from what we've researched with AI. That. Program like victory or or gamma or I'm not even sure what what's out there in the environment today would be better than paying for make the docs like can I take over force and do the same thing. That make the doc guys now that's really not a requirement of this task force but that is a kind of a requirement that that for the Linux Foundation. When they want us to research AI I think that that is definitely. One of the things that we can comment on saying. That that would be great so what do you what are your thoughts do you think AI can do what make the doc does or we over shooting. I can use like I think that we can use to. AI tools and also make the docs because. Like in gamma we write up wrong to create a template or like design so what we can do we can like we don't we have to create our standard templates so we can use the AI tools to create the template the structure of the. Networks because only using AI tools would like would not be like would not help us because. We have to like give better prompts and we need a reference like like every like every documentation that's it has used the. Networks template and all so like we can use we can take the help of AI tools to create the network website I don't think so like only AI tools will be needed like only. I think so interesting thank you that's what I kind of thought as well I didn't think how you know maybe further down the road but not yet I don't think it's there yet. And again I will reach out to David maybe have him come to our meeting next week I know it's really early for him in California or maybe we'll have another meeting in the afternoon. Where we can sit down with him and tell him our recommendations and see what he thinks. As they'll go by so just to finish up here the templates are just regular templates for. The community whether it's. White papers or use cases and then the user guys follow everything everything's going to need a user guide and I kind of see incorporating that with that natural language frequently asked question. I would like user guides to be attached to all the answers to those questions so at the end of answering a quick question a link to a user guide should always be supplied for more information. And those user guides again that's for simple things like we're not talking about using the product products necessarily but how to use things in the community like if I am joining a special interest group how do I do that if I want to create a special. Interest groups how do I do that if I am a maintainer and I want contributors how do I run a hackathon that kind of guides for the community to be effective. So they're different than the github read the docs on how to use the products these user guides are just how to get a Linux. Foundation ID we want these little user guides to be everywhere whether it's I would love to see a consistent avatar teacher throughout the entire community when you ask this question he or she pops up and tells you the answer and where to go but that again I dream big. So those are the user guides this is just where we store our presentations and here is where we want to talk to the. Mentors and the project and tell them what we have to offer for them and offer our assistance in leading them down this new documentation. Consistency hyper ledger consistency pathway so that's basically where we're at now the best practices. I'm going to turn over because this is we talked about this at the TOC meeting about documentation best practices and again how they're along the life cycle. How that badging I even suggested again I was listening to when Alfonso from learning tokens mentorship program was talking about what he was doing. He was doing having the badging be tokenized and on a dashboard so that each one of the maintainers can go to their dashboard and see what they need to complete the next step for their next next best practice badge. So with that said, Rama, what are your thoughts on how we can work together on the best practices to get this done. I tend the best practice meeting I guess I'll start to schedule that end of this week. More specifics I'll have to think a bit more. I think clearly there needs to be. We should have some one or more badges that indicate how well or how mature projects documentation is so that so that could be. A metric that the TOC can use to determine whether it ought to be upgraded if that's on the if that question is on the table. But yeah, most specifics I have to think about a bit more. But please feel, please join the best practices group meeting I tentatively will be setting it up for Fridays at one hour later than this. Definitely I will definitely try to attend that. Again, we thought that there would be the four stages the entering a lab going to incubation graduated and maintenance that you would earn a badge for. And then again, there would be a matrix under each one of these what you need to get the badge. And again, I'm not dashboard you'd be able to see where you are in your project for badging. And hopefully that is in line with what you think the best practice badging system should look like to. Yeah, no, I think that's a good way to start. Sounds good to me. Awesome. So again, what we're trying to do. Arunam and I talked about. So again, with the best practices, we're trying to define what documentation best practices need to achieve for each one of these phases of project and how to get badges for that. Hopefully a tokenized system blockchain tokenized system would be nice and that's what we do if we could do it ourselves. That would be great. And then the next one is the GitHub templates. We need to clearly define in a user guide or a frequently asked question. When you're creating a project all the different stages of the project. Where do you get those templates and how do you fill them out in order to get the badge for that. Definitely would be part of the best practices go really, really hand in hand with this group as well. And then the GitHub read the docs. We're just going to sit down with Tracy. She has her templates. We want to incorporate them into our flow so that everybody who is creating a project can have awesome user guides. Read the docs and people can use their and test out their products seamlessly. The templates, this is for community creating presentations, seminars, meetups, any kind of thing that you want to create. We don't want you to have to think about the design of these things. We want you to just be able to open a template with the graphics with the categories and just fill in your information. Again, onboarding. There's the six spots that people onboard to our community and we want them to be able to get two clicks to where they want to go. Shouldn't have to be three clicking. You should be a two click environment. So if I have a question, and if we get that Jan Luca, I'm going to call it the Jan Luca chatbot on there. We can really have that done in one click, but keep our fingers crossed. Again, and user guides are just going to be wherever in the community that people have a question like how do I get a Linux login? We should have a user guide for that. How do I set up a template? We should have a user guide for that. And then again, supporting the mentorship projects, we need to set up a meeting. So my to do is I have the email set up for Tracy. I'll set up a good time and email to David to set up a good time. And then we have to set up a meeting with the mentees who need documentation. So we'll put out a call to Min to have her send something to all the mentees saying we're having a special documentation for you guys session for you guys on documentation. If you'd like to attend and we'll set that up for some time in September. So does anybody have any more questions or want to talk about anything that I might have forgotten today? I have a question not related to this thing. Like I have mailed you a thing. Could you please see the mail and whenever you are free, could you please reply or response? Did you send it to Ledger Academy or did you send it to a Gmail? I sent it to Ledger Academy. Okay. Okay. I am way behind on my email for that one. I'm going to catch up this afternoon. I will definitely respond. Okay. Thank you. Thank you very much. Any more questions? Okay. So I will send out these emails to people and then I'm going to go through these pages and just put a category on top of each one that just says recommendations. And if you have any suggestions that would go into our recommendations. If you have time during the week to put something down, that would be wonderful. If not, we'll catch up next week on how we're really going to start setting up a schedule to present this stuff on our recommendations. So have a great week, everybody. If you need me reach out, I will be answering my email this week. I am back from vacation and working all week. So no more not being able to find me. Thank you Bobby. Thank you Bobby. Thank you. Thank you. Thanks everyone. Goodbye. Goodbye.