 Good morning, Iruna. How are you? Hey Bobby, I'm great. How are you? Good, good. Just a second. I have to run and shut my door. Yeah, yeah, sure. So how are you? Everything good? Yes, everything is going great. Okay, I'm going to share my screen as usual because we have to talk about something exciting. So let me just get to the right screen. It's very exciting. So, where am I going here? So last week I got an email from men talking about how the Linux Foundation is interested in possibly discussing how to use AI in documentation. Which it was just an email from men, David and the head of strategic development at the Linux Foundation. And I reached out to him and set up a meeting. His name is Robert Reeves. And I had a meeting with him last week. And he was, again, he's like a real big wig in the Linux Foundation. He was completely blown away by what we had introduced to the mentees last week in so far as using AI and trying to do a workflow. So I have a meeting, another meeting with them right after this, which I love it if you could stay on and yeah, I can see. So what he wants, or he envisions and he was very excited. He was like floored and blown away by not only the fact that we're encouraging the group to use the AI tools but that we actually assigned them something to try. He was like floored. So I told him like we tried to, you know, see if this is going to work and we said for everybody to give it a try. So I'm hoping that in today's meeting at some point after we go through the stuff we have to go through like trying to figure out the deliverables for each one of the groups that we have time to see if people actually tried this. A little things got a little confusing because men set up another meeting which is the one that's right after this. I don't think she knew he and I spoke, and he and I have another meeting Thursday, in which he wanted to see what our group came up with. So in today's meeting when we talk about this opportunity which is it, we might be organizing the user docs with AI and then introducing it to the Linux Foundation at their events to so this is like a step above hyper ledger it's an awesome opportunity. Great exposure for you guys, and I'm very excited. So, that's what's going on with that and I just wanted to give you a heads up before the meeting. So, what do you think did you think anybody tried it or played with it because we do have till Thursday. And should we actually see if they want to, or should you and I just try it. Okay, so from my side, I have been using charge you for a long time using these prompts and all to actually document my code and write the read me files in my projects and a lot of things. So I have always blow me away I'm very excited. It's actually very useful, even, even for like every small thing it helps a lot so I've been using these tools for quite a lot of time so I don't know if others have tried it or not but I think maybe a concha and, and the poor or casual has tried it out. So what, so what basically the goal is, is to use these tools to automate user guides so far down the road like the ultimate goal is that when somebody updates their GitHub repository, wherever that I'm going to use a old term web hook, wherever that web hook is it would automatically update. Okay. So right down the road but right now what they want is, they want to be able to create user guides using AI quickly. So I had showed them the flow with, if you look at the screen, putting something in chat gbt which again I've been using it for for months as soon as it came out I was like the first one signed up and love it. I think it's awesome. I just learned about how to do the dictionary and the gamma and I'm sure there's other programs for this that we could research or look into. So what they're actually asking us to do is kind of come up with a really good workflow that would create user documentation so you know when you pick a template the template would be a hyper ledger template obviously. Grab the template, put your documents or put your words from chapter gbt and, and either have a user doc or a presentation or something. And they'd like us to try to organize that. And we'll find out more in that next meeting after our meeting today. So what do you think about creating user guides for not just a hyper ledger but for the Linux foundation as a whole, not creating the user guides themselves but creating the workflow with AI is basically the goal. And that would be a very interesting thing to try out and it's, it's a great opportunity to explore different AI tools and also a huge opportunity for all of the mentee so we should definitely try out and you know let others also know about it and they can try out from there and as well so it's a great opportunity. Yeah, I'd like to see what you know if, in fact, anybody has played with a workflow and try to figure out how that workflow would manage user guides from the assignment last week but then moving forward I mean I don't know what this Thursday is about but if he wants us. I would like the mentees to explore these tools for user guides. I mean, after being in the meeting so often, they kind of already know what what we're looking to do by the end of the summer. I think today some of them won't be able to join they said me because they are not well. I think Victoria and Kajal they won't be able to join and I think the rest all of them will join so I think we can ask them and those are not those who are unable to join I will definitely connect with them over LinkedIn or an email and ask them and let them know about this opportunity and like see if they have tried out some some of these AI tools or some other AI tools also so we can get their input as well like that. And if Robert Reeves wants a meeting with Thursday with other people to get involved, I'd like to maybe have us meet Wednesday. At some point to go over what we're going to present to these people if it's just him informally we don't have to do that but if he's bringing other people in, we should do that and I think we'll find that out of 11. I don't know what time it is for you sorry at the meeting after the meeting. Yeah, yeah. So excited. Yeah, it's actually the AI tools make the work really really easy. And if we can think of a reason I can't say how many times I use charge you to actually rearrange my points on like I just write some random points that come into my mind and I asked it to you know write it in the form of a paragraph and it, it actually organizes and it has been writing blogs and everything. Yep. Awesome. Yeah, me too. I actually use it. When I write courseware to do the multiple choice questions for me. Like, alright, here's my text give me 10 multiple choice questions with answers. Yeah, that's actually very useful. Okay, I just have to run and grab a cup of coffee before our meeting so I will be right back but that's great so whatever flow you wanted to do for the meeting just leave time to discuss this if you want to do it first. You want to do it last whatever but we should bring this up in the meeting. So what today's blue. And I'll just I'll summarize my call with Robert, and then we'll see what what happens. So I will be right back. I think we should wait for a few more minutes and let everyone try for two to three moments and let's see if everyone joins. And then we can start with the meat. So I think we have Gianluca and three put in the call. So for today's agenda, we will just be going through the basic interruptions and list down the delivery bills. So, just let me know if you have any, any help needed or any, anything regarding the deliverables or frame the timeline for the upcoming weeks of each of your subgroups. So starting with triple triple you can go ahead and introduce yourself and let us know if how is the task going on. Hi everyone. Hey Bobby. You have read the dogs. Okay, I am back. And I have my coffee. Hi Bobby. How is everybody going good. Good good. Okay, let's get to the screen. Okay, as usual. Arunama did a great job on the outline for today so I will let her take over for the beginning of the call, and we'll go from there. So, it's all you Arunama. Okay, but we should use share the screen or. Okay, so should I share. Okay, okay, I'm going with sharing the screen. Perfect. Okay, so the starting with policy so if any of you want to move the conductor you can go through the introductions. So first we have those. Arunama, we're losing you. Are you there. We can't hear you. Yeah, I think my internet pant off like we share the screen again. Okay, someone at the door please give me a minute. Hello everyone can you hear me. Yes. So sorry for the interruption. I had someone at the door. Okay, so starting with the introductions. First we have people. Hi everyone. Hi Bobby. Hi Arunama. I just want Arunama to go over the GitHub read the docs page. I'm updated it. Oh, okay. Oh yeah, we have to do that too. I forgot about the. Yeah, yeah. So yeah, for this week, I have made a table that what task I have to do. And by what time I will be completed and by that I will take box all my progress and in the comment section I will I have mentioned what I will be discussing in the meetings and what will the things will be as I was working with the working on the standard guide. I realized that I cannot do it in a week because it's a very lengthy guide and I have to come up with like I can only do it. And like in the sidelines and while I'm working on so long because I will not be able to update it. Like I should like as I like updated like completed first and then go to so long. So I thought like completing it section wise. So this week I will taking the step sections in which I will include step like steps for creating a user guide. Then I will go in detail. I'm already working on it. If you all want I can share and moving on to the second task for this week I have this meeting with Solana as I was not able to set up so long so long in my computer so yeah I will be joining the next meeting I was not well this week sorry guys. And so can I just ask a quick question. What was the problem when you tried to set up so long. Actually I have a Linux like I'm using PopOS so when I was setting up I was not able to give the path and if I I also mentioned the path then also I was not able to like get the file open. So I was getting issues on that and for me like even though I know tech after that also I was not able to set up so long properly I have I've tried it multiple times I don't know what the problem is coming. So would you say in your opinion it's a user guide issue or a product issue. I will say it is a user guide issue because like all all the people who are not able to like understand technical language and who are first timers will not be able to like if one if I can show you the like screen is shared. Sure. Go ahead. Is it visible. Yes. So the first thing about Solang which I was like installing it I was not able to see like Solang compiler in binary and like all these things then we are going from directly how we can download it. Then everything is very mixed up like for for Mac OS they have specifically done it. But if you go further for Linux they have just given this but not mentioned because everything is mentioned for Mac OS then we have to on Linux we have permission to execute this but after that we have nothing like know what will be the like outcome. No pictures or any screenshot like how we can confirm that this is right thing that we are doing. So I wanted like we should include a screenshot after and also after that and also like like separate all the downloading process like first of all mentioning the Mac OS then after that second will be Linux then after that Microsoft because as I was going further I was getting more and more confused. The first step was downloaded from I was not able to understand from like what the person is talking about because as someone who don't know anything about tech and that person read this they will be very confused. But if we go further then also I was really confused like how I should confirm that it is set up or not. So yeah then also in the like they have mentioned the options then after that there are no screenshot in like I must mention this like also that they have mentioned the step one installing the LLVM libraries for like extra patches. So here also when I was downloading this and after starting the part I was not able to confirm if I'm doing right and then I got error. So yeah I will be discussing with that with the Solang team and also in the step two again the same thing how should we confirm it is building or not like if you are not in tech and you are the first timer then how will you confirm this. So these are the things that I found like missing in this thing in the installing part. Okay, no no could you could you go back to sharing your screen because I wanted to point something out to everybody. And great that was a great analysis I found the same thing when I was doing the two fabric courses, setting them up took more time than it should. It was ridiculous it took like days to set it up in minutes to do the course, but could you go back to sharing that screen. Bobby are you telling me. No no the screen we were just on with the Solang user guide. Okay. This one. I wanted to point something out if everybody will look on this screen. It says bottom left. It says read the docs. Yeah, so here's the thing. And somebody can correct me if I'm wrong, but read the docs just takes to get a repository and put some bells and whistles on paragraphs and formatting and throws it into this format. I'm noticing that there's no screenshots that happened through this process. There's no really checking to see if it works, except for by the actual users. And is this what people are finding again because this is where they want us. They want us to be able to have the community using the same, whether it's make the docs read the docs, Sphinx, whatever, using the same one of these to get the best outcome. So that's what we as the task force have to come up with saying we don't like read the docs because it doesn't do screenshots and there's no way to check to see if it works, or we like make the docs better because so that's basically when we say, get hub read the docs section or committee, that's basically the decisions you're making so you're not going to be responsible for checking every projects reader or creating user guides, we're more charged for just figuring out which one works. Does that make sense. Yeah. So what do you think of read the docs personally. So you're suggesting that we should work on, like make the docs, rather than read the docs. Well, okay. Here, let me share my screen for a second. If that's possible. Where was it. Should I share the link of the same documentation. That would be great. Yeah. Yeah. Let me just go where was I going to get rid of this. I'll just need a minute to get. Yeah, it is in the next section. Okay. And I'm going to turn I swear to turn the meeting back over to Arun. I'm looking for the analysis we did way back when I still think it's on here. Yep, here we go. Okay, so these are the mentorship projects that need documentation help after we're done. Here we go. Okay, so this is what each project uses. They're all using the read the docs, some of them are using make the docs, some are using just the docs. And so paid the, the technical documentation user markdown materials for doc so this is the one that hyper ledger now pays for. Everybody all these other projects created all these GitHub repositories hyper ledger gave them no guidance, telling them how to create user guides. It just said you should get a repository, create something for the users so that people can use your product. So again, we're charged with trying to get that into some sort of template in help. And now so the hyper ledger community has paid for this materials for doc. So what we're trying to do so is take this, and I'm not even sure what this is probably directions on how to use materials for the yeah. So this is the make the docs web page. It talks about how it works what you need to do. So, I don't know if this helps you at all, but what we're trying to accomplish with the task force is to get. I guess a user guide for the maintainers that uses make the docs, or that paid tooling policy as a suggestion for taking GitHub repositories and creating user guides. So, I guess the next step for this task force would try to be since you're familiar with the soul and read the docs. I would just see if you could take the GitHub repository and run it through make the docs and see the difference. Yeah, sure. Yeah, I don't know how hard it is I don't think it's very hard to run the GitHub repository through the make the docs, but the analysis would be priceless. Yeah, okay, I will do that. If it's not too much. Yeah, I don't want to waste an hours and hours and hours it should just be a simple, you know, let's see if it works, and then just compare the two. Yeah, it will be my first time to do that and I will try that if it works for me for like in, like if I get able to do it in a shorter period of time then if it will I will be able to set up it otherwise it will take the help of the soul and community Yeah, it is not your job to get their documentation to work. They need to get the documentation to work it's your job to make suggestions on how that documentation should appear. Okay, and again I like your idea of screenshots a lot. I think they are helpful I found with the fabric documentation. It would say do something and it would never let it would show you the end result of a successful line of code. It would show you if you got an error but it wouldn't say you know, oh this is what it looks like after you're finished this is the prompt you'll get and you can continue. I agree with you 100%. Exactly and that was me that makes the user more confused like they if they get the error or if they don't get anything, then they will be like okay is this setup or not how will we check exactly. And there is no like a way that there is written like the first word that we always run is hello world. Now there is nothing like that that if we can check if this is running that means you're good to go. So yeah you can also add something like that. Thank you I'm going to be quiet now. Yeah, yeah sure. And thank you so much trip would run Bobby I guess so much really to your problem because I was interning with Sodana when I was an image fellow and I faced the same problem, so I can relate a lot. So, next we have Gianluca, so Gianluca you can go ahead and introduce yourself. Yes, yes hello everyone, do you hear me. Yeah, we can hear you very clearly. Perfect. Okay, so I'm. Thank you, Bobby and Ronima for your messages on GitHub on LinkedIn. Bobby you shared me to a couple of links about existing documentation on maintainers on GitHub documentation maintainers. I read all the links all documentation existing and also I planned some activity for next weeks. And I, I've written a list of a list of activity in my template page. And these are, I don't know if you can, can. Yeah, thank you. That one. Yes, on the bottom of the page. Yes. I've planted some activities. The first two or three weeks are about training a training stage. And a question is about the documentation. What are the most important goals for the end of this project, because I see now documentation is is there is documentation on on GitHub. I have an idea about the improvement, but I'd like to share with you. How can we, we improve that the existing the wind nation. I don't know if the question is clear. I hope you don't mind I'm just going to rephrase this question just to make sure we have it correctly. So, you, you want to. I didn't get it. Yeah, so basically, Jean Luca you want to. Yeah, I'm not sure what your question is. Could you rephrase it. If you want, I can share my screen and try to repeat the. Okay, okay, thank you. Okay, this is my screen. I don't know if you, if you see my screen. Yes. Okay, perfect. So this is one of that one. And the second one are the existing documentation about the maintainers. I already read that documentation is the link that you shared Bobby. And thank you. And I think I have some idea on how to improve the existing documentation. So when you say existing documentation you're talking about this documentation to teach maintainers how to set up their GitHub repositories. Right. Perfect. I was confused. I thought you were talking about again the other GitHub section with the read the docs and I'm like no no no. We need to make sure the maintainers have all the crap in there that's needed for the read the docs and that's this part so great job. And any suggestions again would be appreciated so I'm going to again. Just to sum up what this task force section committee is doing on is taking the existing materials that help maintainers create their GitHub repositories for their projects and making it so it's a little bit more standardized for the community and to make sure everything's in there. I do have a question for both Jean Luca and or if we wanted to automate this with screenshots with the screenshots have to be part of their GitHub repository. I guess it would have to be. Yeah, it have to be like that will also help the people who like stumble upon the GitHub repository. So they will also be like able to set up whatever they are doing and get like making it more visualize will make like the user or the person who is leading it more interested in what like results are showing. So yeah you will be able to read it. Okay. If I run this thing this will happen. Okay. If I if I do this this will happen. So yeah. Then we can add a link like go to this link you will be able to see what will happen if you run this code that we can also do that. Uh huh. And like in add a Google Drive image something like share of that. So yeah we can do that. And the question is, we have two pages. One is the first one is the existing guidelines about maintainers and the second one is an example that each maintainer can can use to as a template. Okay, can copy that one in the own repo. The question is, it, how can we improve the existing money, the existing pages. My idea could be adding some, for example, documentation about GitHub comments, and also using screenshot. Other one could be extended the existing documentation. If you have other idea about that. So I'm going to jump in again. My idea for this. Again if I'm a maintainer. So I like to take it from the beginning so if we go back and think about a project that's in a mentorship project project that's going to be its own lab eventually. That's basically the starting point for all of this. So if I'm a company and I'm going to put my project into the hyper ledger open source community. The first step is to create a GitHub repository for a lab, and there should be a step for that somewhere. So the first one what each that copy that. And then once that that GitHub repository is set up in a lab, that's when people can start adding maintainers and doing whatever and, and, and working towards getting the lab to incubation. I don't know yet, I haven't, we haven't done the work yet, but might be the same as the GitHub repository for the lab entry into lab might be the same GitHub structure as entry into incubation, I don't know I haven't compared them. When that projects in incubation, and it's going to be moved into a graduated status that GitHub repository I'm sure needs more information in it than it did when it started as a lab. So that's kind of the user guides we need. So we need a user guides for maintainer maintainers. This is your lab information here's the link to get the sample maintainers GitHub repository working and yeah we need to make sure that that is correct. And the next step is alright you're done with your lab you want to get your lab into incubation. Here's the next step for maintainers this is what you have to do with your GitHub repository to get the roles and get everything ready for incubation. And then the next step is graduation and here's what you have so it's kind of like a user guide for GitHub management through the life cycle. Does that make sense. Okay, so I tried to repeat to understand if I am right understood. What do you say. So it's important to differentiate the GitHub guideline for different stages. Okay, okay labs incubation and also the graduated. So, everyone, could you click governing documents on the page because I can show him the life cycle real quick. Who's ever showing this right the governing documents is the second file. Who's screen sharing. I think can look at is sharing this. So maybe you can just click on can look up. Okay. Everything was an Italian that was so cool. No worries. We just wanted you to go back to sharing your screen I just wanted you to hit something. My screen. Okay, okay. Okay, thank you. Okay, so click up on governing documents in the left hand side. Menu here. Down in the, no, not there over. Get rid of that above maintainers guidelines you'll see governing documents. Up one. Up. Oh, okay. Project life cycle. Okay, first. Project. That one. Or do the one we can read. Yeah, that one. And scroll down a little bit. There you go. So that's the project life cycle. Okay. So a GitHub repository. There's ones needed at the proposal. That's when you go into labs. That's what a lab proposal is. And then when you go out of proposal to incubation, your GitHub repository should have some more things according to best practices that should be included. Same thing when it goes to graduate. Proposal incubation and graduated. That their GitHub repositories change as they move through those cycles. Okay, okay. So the first, the first goal is to determine the difference between GitHub in different steps. Exactly. Like, what's the difference between a lab GitHub repository and an incubated projects get a repository. Okay, what. Okay. That would more be what the main team. And again, this is the, this is where they go right now for this information. And this is not user friendly. I wouldn't have to. Right now I wouldn't know to go to maintainers guideline and copy that GitHub repository. No one's telling me to do that. And I found through the times that that's a lot of that's the most question I get when new companies are coming into the community. And they want to set up, they're like, how do I do this? How do I set up a, you know, like that. They need guidance in those three, three project statuses, what they need. Okay, so, so with the first step could be, could be right to study for the next two or three weeks would be right to study a background of GitHub and also about this life cycle, diving in. Yes. Okay. So I think because once you set up your lab, GitHub repository, if you set it up correctly, there might not be, I don't know, there might not be anything you have to do for incubation. You know, you just might have a more robust GitHub repository because of your work. I don't know if you have to add a category or take a, I don't have no idea. I've, you know, so that's what we have to figure out. Okay. Now it's clear. Okay, and after, after that we can, for example, we can propose a first goal, a first goal, also design a new, a new version of GitHub repository, according to what we can, we can learn during these two or three weeks. Exactly. Okay. Okay, so about that line we can, we can talk about that in two weeks. And after one, another weeks, we can talk about a first design, a first version of design of the improved, improved documentation. And, and also I will have Tracy, who has probably set most of this up initially, come to our call in two weeks so that we can ask her questions of if there's anything that she expects from us that we're not covering. Oh, that's great. That's great. Our feedback also from him is, is very, very good. Thank you. Yeah, that would be wonderful. Yeah, so I'll make sure that I invite Tracy. Okay, perfect. So the first two steps, in my opinion, could be first one to study and learn about background give GitHub and also the existing documentation on that graph that I see. And now that these two three-step proposal, it should be a lab incubation and graduated and difference between the three steps. And second, second one, we can propose a first design of the improvement and share with Tracy about according to a feedback about that. Correct. Okay, perfect. Now the question, you answered my question so I'm happy. No, good. So I don't know if you want to go ahead or you have a question to me. There are other questions because you asked me to write a short list about the next steps. Yeah, just so that, you know, we can have regular discussions and stay updated with whatever is going on in the various communities. It was just for that purpose. So yeah, I don't have any questions. I just like send a message to everyone regarding that regarding framing the timeline so that we all can stay updated about what is going on and if required we can help each other also. So that's it. And I think, yeah, yeah. Next we have Agnes. Agnes, you can go ahead and introduce yourself. All right. Hi everyone. I think it's very impressive to hear what everyone has been trying to do over the last couple of weeks. So I think I'll start. Oh, yeah, let me introduce myself. My name is Agnes. The backend developer and technical writer. And I'm supposed to help out with user days. Yeah, so I think I'll begin with what I'm not sure who shared about checking the solar and dogs and noticing days in screenshots and all. My, my observation has been for the good little project for some reason I've just been looking at those. They seem to have a sort of structure. So I looked at Indie I'm currently looking at sort of they seem to have a structure where they have a general introduction to the projects and then the features of the project. And then they have now the getting started guides how to install and all I'm yet to install so to then see whether I'll have any problems in the event that I do update us. So I don't know whether that's something that should be across all the projects and would be telling us about the whole flow. I don't know that that's something that can help in us guiding the other projects that are not graduated. In terms of user guide, I got a bit stuck because the more I think about it the more realize that every aspects of the project has a user guide component to it. So I'm not very sure exactly how to help in terms of user guide. Since the onboarding team has a user guide components, just like Jan Luca was sharing, sounds like they've been to the user guide components. So I'm not very sure what the exact tasks and activities would be in terms of user guides and also keeping in mind, I think there's a whole discussion about personas and all. So I haven't found a clear way among all the scenes in terms of exactly what to do in terms of user guide. So maybe someone or maybe both the or someone else might have a better idea. Bobby you want to see anything regarding that. Well, do you think it's time to go into our next section and tell everybody the good news. Yeah, actually. Okay, I'm wonderful. So, I'm going to probably share my screen again. I don't even know what's on it. No, I'm not going to share my screen yet. So we were talking with last week in this group a little bit about AI and chat GBT and a few other software programs that assist in creating presentations and creating videos that would be automated. So again, there's like Agnes just said the idea of creating user guides for this community is overwhelming. There is no way that it can be done, like by a group of people unless you are paid full time and it's what you do full time. It is impossible. Every little nuance needs a user guide. Last week I took a little risk when I brought up the subject of AI and using AI and our user guides, but I wanted to see what we would come up with. So I showed you guys a little workflow and I'm going to now I'm going to share my screen to see if I can find that over here. Put this over here. Okay, so the you the workflow that I suggested was something that I picked up from a class I took two weeks ago and I've been taking classes on AI trying to find a good way to teach this stuff and a good way to organize this AI curriculum. So this group nailed it. You want to take the class I took the company is called Mission Impact Academy MIA and it's it's just, it looks like a women's group but men can join. So again they they have the really as far as I get some some really first rate curriculum on AI. So from what I took from their session is. I call it a workflow. So if you're going to be using AI productively in your job you need to create workflows which start the prompts. So what we did for an example last week was we took a prompt and the prompt I put was create instructions for a maintainers guide to set up a GitHub repository for a lab, which is kind of Jen look at what you're kind of looking at doing. And that's all I put in chat GBT. As an educator in a curriculum developer, I don't like to leave it up to chat GBT so in my workflows when I'm doing creating curriculum. I like to give it the outline to, because I like to really kind of direct where stuff is going to be what what's going to be filled in, rather than just come up with whatever chat GBT decides. So but for our example last week I just put in instructions to set up a maintainers guide for a lab. And it came up with this. So I took this information that that chat GBT gave me, which I'm going to call the result. And I put that in a program called Pictionary, and I got a presentation with graphics music. You get the idea. So it created an entire presentation from the prompt results from chat GBT. Then I took the same results and put it in a program called gamma, and it created a presentation. So that one was a video and this one is a presentation. And you can edit these and whatever. I don't want to download that I already had it on my computer. It created a nice little presentation it took kind of the same information from the other presentation. No I'm going back and forth between the pictures sorry. So it created a presentation and then it created a video. So that is a workflow. So it took it from all the way from an idea, all the way through to a presentation in under 10 minutes. So basically, I thought that that was pretty cool and I thought everybody should try and play with that. And I don't know if anybody did on their own do that. But coincidentally, after our meeting last week. We're on the head of the mentorship program, and David Boswell, the director of hyper ledger, one of the directors at hyper ledger, and Robert Reeves, who is the head of strategic development of the Linux foundation. We're on an email that I was included on talking about how the Linux foundation and all of its community projects might want to start the discussion on how to use a I in their work. And you know me I'm a little, you know, I have no modesty or inhibitions. I reached out directly to the head of the Linux foundation strategic development and said, This group is doing it now. He was so impressed he set up a meeting with me, which I had last week, and I told him about what we did. And he wants to incorporate a workflow like this to all of the Linux foundations documentation he wants to be the leader in the Linux foundation of using AI for user documentation, and I was very excited about that. So I told him that I would bring it back to this group which we're doing right now. And I have another meeting with him directly on Thursday I don't know if I'm still going to have that meeting on Thursday because men David and Robert and I are and and hopefully a runima and anyone else who wants to come. Have a meeting and it's on the public calendar right after this in 15 minutes. I will discuss his ideas with the hyper ledger people they don't not know if they even know that I met with him already. And I have another meeting with him on Thursday to show some results of what the hyper ledger documentation task force is doing with AI. I'm encouraging everyone on this call to try to do something so that we can say to Robert Reeves and the people over at the Linux foundation and then he wants us to bring if we have a good system he wants us to deliver this in presentations to the Linux foundation to the open source people to the member summit I mean there's opportunities for us to go. Again I don't really travel much off the east coast but I mean there's travel opportunities all over the world for this one so this is this is exciting, and this is an opportunity like I've never had in my life either so I'm very, very stoked about this. And the meeting after this meeting. So, Agnes this kind of is not really falling on you but kind of falling on you for your opinion on, what do you think all about AI and this kind of workflow and the user guides, like because you've been looking into it, what do you think it's possible that we could do something. Yeah, of course it's possible. So, I think I like the idea of the workflow since we can't really write user guides for all the project. For a start I think just top of my head I think what you can do for a fast phase just to test it out is identify the different user guide areas that we already have at this point. For example, I would think Jean Luca has one and maybe the Solan team as well. And then we sort of create the templates because I don't think we'll create the full guides or maybe even the guides for like you're saying for the projects to move from labs to the next stage and then we can see how we are able to come up with that then that can be part of what you can really tell the rest of the HEPA ledger teams or management if I may call them. Yeah, I think that's a good place to start. Yeah, that sounds good. What do you think Arunaman what are your overall thoughts on this new opportunity. I am just you know loving it because I have been using AI I don't know for so long for organizing my code for getting you know debugging my code and anything you say use AI tools a lot be chat GPT for or some other tools to make presentations and even for you organizing my tasks. I use a lot of AI tool so I'm very very excited about it because I know how easy it makes our lives. So, yeah I am very excited about it and let's see what we can do with that but I would love love if we can present something in Thursday or whenever you know we have the presentation so I'm very excited. Here's one of the things that I just remembered he said in our meeting that as the Linux Foundation goes, they are interested in like for instance, an easier example to explain is zoom. The Linux Foundation paid for zoom on a regular plan that everybody had so that all the resume rooms for the calendar of public meetings were available and they were, you know, done all, you know, whatever you had to do to them. After using zoom for so long, it became cost ineffective to do it that way so now we stepped up our subscription to zoom so now, if you go to the calendar of public meetings and open a meeting it's automatically recorded it's automatic all this stuff is automatically done because we've stepped up our subscription. So Robert Reeves from the Linux Foundation is like, I know the Linux Foundation is going to have to get in relationships with some of these tools for AI and incorporate them in our systems. And he's like I don't know what those tools would look like, or what they are. So I just mentioned the tools that I learned in my, you know, seminar last week was picture every chat GBT and gamma. I'd like to see what tools you guys use so if you want to take this same exercise with this prompt and see with your tools what you can come up with so we can compare them. And in the meeting Thursday will we'll have a, we have the meeting in a few minutes. First, we can say, this is what we're doing, we are comparing we're taking the same prompt instructions for our maintainers to set up a GitHub repository. We're taking that same prompt and we're running it through different tools to see which one has the better outcome. That's, that's something that they'd be very interested in so everybody here want to try that or. That will be perfect Bobby. I have the perfect AI tool to share with all of you. It's for like, if you are a technical writer and you want to mention the references of the people you're using the work and everything in chat. And this is one thing that it does not give you the links of the website, the cop with the content it copies from. So yeah, I have one very perfect tool to share with you all so should I share it now or should I share it in the meeting itself. I'll share now that would be great because I don't know again, we're not running the next meeting they're running it so you know I'm not presenting anything for that, but I just want to finish this and then I'll let you share your screen because I want to make sure we're on the same. So idea for user guides for prop. What's today's date today is seven 24. There's a lot of degrees that they'll give that a world and there's the prompt right there instructions for maintainers guide. Okay, so that's there for everybody if they need to reference what we're trying to do this week with the AI so I used chat GBT, pictory and gamma, go out there and try something else you don't have to just do presentations or that I just this is the only things that I knew. So that's their update and now I will stop sharing. Can you just. Yeah, go ahead. Yeah, can we just share the link of the meeting that we had that you have after this meet because I would love to join that meeting and know about. I'll show everybody where it is so that they can get it. So, yes, Bobby. Here. Oh, it's not in the calendar of publicity. It's my calendar. Is that correct. Let me see. I know it's not on the public calendar. Let me grab the link hold on. Okay, I'm putting it in the chat right now. And again that meeting starts in five minutes. So does anybody have any more questions on today's meeting. No Bobby, but thank you for the opportunity Bobby this is really great. Um, and what's the, what's I'm going to leave it up to Arunama if we want to meet if we do get some time with Robert Reeves and the Linux foundation on Thursday. I had mentioned that maybe we should meet Wednesday. So I'll let Arunama set that up if in fact we are presenting to him on Thursday which I think we are but let's make sure in the next meeting. Yeah, sure. Just let me know that I can get the links for all these meetings. Yep. Okay, perfect. Alright, so I'll see either you next week or in a few minutes. Just in a few minutes I will be joining the next next call. I will be there. Okay, and everybody great work. Thank you for doing this. We're going to have so much fun when we present these low over the world and I can't wait to meet you guys on these stages and I'm looking forward to it. That's great. Thank you so much Bobby and I think the next meet we have a Wednesday or Thursday. Well it depends on what happens in the next meeting. If they if we are presenting Thursday, we should regroup on Wednesday. Okay, okay. We can figure out when. Yeah, that's perfect. I'm leaving the meeting and joining the next one. Okay, I just have to put this out there. I might be counting on you a lot in the next two weeks because my daughter's about to have a baby on August 1. I will be going to Boston to help her with that. So I might not be able to run the meeting next week or the week after, depending on when she has the baby. No problem Bobby, I will take care of that. As much as I can. I will let you know. Okay, and congratulations to her. Oh, thank you. Thank you. I know it's fantastic. It's my first grandson. I'm so nervous. Congratulations, Bobby. Yeah, very uncomfortable right now. Anyway, so I'll see you in a few minutes. Yeah, sure.