 Hi everybody. Hey Bobby, hey everyone. Hi. Bobby, I apologize. I have to drop off in just 15 minutes. I'll set you as host before I go. Oh, that's great. No, no worries. No worries. Busy day. It's a Monday. Yeah, Monday's right there. It's some kind of a holiday. I think it's probably the easiest holiday to celebrate anymore. It's May day who can have a problem with the first day. Oh, that's right. Yeah. It wasn't realizing. Celebrate May day from now on. Nice. Yeah. It's used to, yeah. Nice neutral. We'll see. So it looks like we have a lot of mentees on. So we'll focus a little bit more on the mentorship program. And go over what the task force is doing. We'll just give it like another minute to see if John hops on because he usually likes to run the onboarding task force section of this call. But we can start with documentation. So I'm going to share my screen. Actually wait before I do that. I just want to grab another screen. So again, welcome to the hyper ledger task force. Call for Monday morning. We cover the documentation task force and the onboarding task force, each of which have a mentorship project, looking for mentees at this particular moment. And some of them might be on the call. So we're going to give you a chance to introduce yourself. This is a hyper ledger call. So there's a code of conduct. And a antitrust policy. If you haven't seen them before, let me know, and I can send you a copy. They're not. They're right on, on the website. Excuse me for just a second. I need to shut my door. So one moment. Sorry about that. Okay. So again. If you need the antitrust policy or the code of conduct, let me know. And they're on the wiki page. You can just hit the search bar up in the right and you can find them. So today. This is the, we'll start with the documentation task force. I am on the TOC and I am the mentor for this particular task force. So before we get started with the details on that, why don't we have everyone here. Introduce themselves. We'll start with David real quick. Just going off mute. Hey everybody. Nice to meet you. If I haven't met you before, I'm looking forward to working with you here in the task force. So my name is David. I'm one of the Linux foundation employees supporting the hyperledger community. So I'm here just to hear what the group is doing and to see where I can help out with anything around documentation or onboarding. Thank you, David. How about I'm going to try to pronounce this correctly. Anna Suya. Hi Bobby. Good day. I suppose this is morning for you, right? Yes it is. It's my 9 30 PM for us. I'm from India Bangalore. Actually, I attended last week's call and my name is already in the documentation task force. So I'm founder of the new world innovations private limited and like. Company is basically into I work with blockchain and like I'm happy to be part of the community. Yes, I listened to the call last week and thank you for contributing so much. We'll have specific stuff to go forward to work on. So I'm looking forward to that. Devesh. Hey Bobby. Hey everyone. I'm a computer science student. My name is David and I'm from India. And I have been joining the hyperledger meet for a couple of times. And I'm also contributing to the hyperledger. Docs like this. And I recently started learning blockchain and I'm looking forward to contribute more. Thank you. And I just wanted to say, if you're interested, you might want to look at joining as a co mentor with me. Because I know you have some awesome skills that you could share with the mentee for the program. If you're interested in that. Isha. Oh good. Isha and you want to introduce yourself. Yeah, hi everyone. Hello. Yeah, we can hear you. All right. Hey Bobby David. Hey everyone. I am Sean. I'm from India. And I'm currently in my second year. I'm a computer science undergrad. And this is my first school as well as my initial stages of participating in the hyperledger community. They are looking forward to get along with everyone. Well, we're glad you're here. And I hope that this call entices you to keep moving forward with your mentor application. And so I'm sure I didn't say that correctly, but I hoped it was close enough. Yeah, so hello everyone. I'm a pre-finished student. I'm interested in working on documentation project. I was also selected as the second people candidate to work on the documentation as part of G sort of last year. I just wanted to ask you that is there any tasks necessary to perform to get selected as an intern. Yes. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. You would, I will drop a link into just give me a moment. Here is a link to the page that. Has all the information that you would need. And it's in the chat in just a moment. Thank you. Thank you. Thank you. Thank you. Thank you. And there's also, if you're interested as well as the documentation task force, there is onboarding task force was closely related to. The documentation task force has more to do with how the community walks into the door. And how we can make that like a few clicks to get them where they need to be. And that we'll talk about in the second part of the call today. So, and then finally, Tracy. Thank you. Thank you. Thank you very much. Thank you. Thank you. And I'm happy to be here. I'm happy to be here. Because we're doing a lot of research and technical oversight committee. And I have put together a template on the documentation. That we can use moving forward and happy to be here. Awesome. Thank you. Okay. So we're going to move on. Hopefully. You can, everyone can still see my screen. So what we've been doing to catch everyone up. for people to, and not just the maintainers and project coders, but everyone. So the project has multiple levels. The first level, again, is definitely the readme docs that come from GitHub. There's some, again, we have some tooling support for that and, yeah, paid tooling support. And what we need is a way to communicate that to the rest of the community that these tools are available. Let me start with the beginning of the actual tasks for the documentation. So right now, we're further, as a task force, further defining how the mentor Menti is going to do his tasks in a certain time, him or her tasks in a certain timeline. So we want to sit down and kind of look at the deliverables and spread them out over the timeline of the mentorship program. And that's something we'll be working on, I guess, this week. There's still two weeks open for the mentorship program applicants. So that, again, is a great time for you to just read through these wiki pages that we have and see if this is the flavor that you really want to work on. And then the one of the first things that that Menti for the documentation task force is going to have to do is, again, if we scroll down, I don't want to scroll too fast to make anyone dizzy. But here are the projects that I pulled out of the mentorship accepted projects this year out of the 33 that specifically had documentation needs. And I want to work closely with these mentees with our mentee for documentation to support their needs so that whatever we've got at this point from the task force, we can communicate to these mentees and say, here, we're here to help you when it comes time for you to do your piece for documentation. Let us know and we'll help you. And I know a lot of the projects, especially Cactus, has been calling for help for documentation for a really long time. So this is a great time to really get in there and say, here, here's what we have. And again, we have places that have repository, which Tracy was referring to. We can show you that's already set up. It just needs to be propagated with the information. But the first thing that that mentee is going to have to kind of of all the mentees hit the ground running because they're going to have to right away contact or, you know, there is that welcome mentee presentation that men puts on, we're going to get a couple of minutes for our mentee to talk to the other mentees at that initial meeting. And I think David and I had talked about that and that, you know, men was OK with that. So that's something that we have to like make sure that we have the tools ready for the mentee right away, like saying, here's our suggestions for you to, you know, use or what have you. So again, these were the deliverables, these five points for the deliverables that we put into the documentation mentee application. So if the mentees are applying for it, these are the deliverables that they're getting their head around being able to accomplish. And I dropped in here, just some actually, let me get Tracy's. In here, too, so it's all in one spot. Give me just a moment. OK, so now we have the. Template for the GitHub repository, where we're going to put our suggestions. Again, we have that paid tooling policy. So that's a recommendation that, again, the mentee will have to like look at and figure out how best to communicate, you know, what's available. We're not really ever going to tell the community what they have to use. But most of the community in a survey has has suggested that they want this information. So again, that would be the GitHub part of it. And then the marketing part, again, this is just the style guide for documentation. People want to just see where our logos are. They want to do a meetup. They want that slide that David supplies for all the meetups to advertise their meetup to put on your meetup homepage and then, you know, to use your presentation color scheme from. So, you know, that stuff has to be out there. So that's another interesting avenue to go down for people who want to create information like that. And again, there's another piece in here. I'm not going to put it in there just yet. But there is the Archive Learning Materials Working Group Documentation Templates where there's a template for a white paper. There's a template for a use case. There's a template for a course. So if there's things that you additional resources and suggestions that you need instead of going out of the community, we want that to be available to the community, too. So that's all in there, too. And again. Yeah, this should be down here. I'm sorry. Oh, it is. It's their choice. So that's like some of the things that we want to be able to recommend to the community. And then we want a way to put these new guidelines or suggestions, offer them to the people who already have documentation for when they update it. So not just new documentation, but suggestions for information that should be available to the community in a standardized way, not forcing you to use a template. But certain things have to be in certain readme docs. And we can go into that in too much time we have for this year. We can go into that in a few minutes. And then finally, well, the mentee also would be doing announcing this stuff, kind of marketing the new, you know, available documentation, guidelines, templates and suggestions. And then finally, there is the other task force for best practices and a huge, not a huge section, but a section of that has to do with what documentation should be available to the community for a project to get this best practice badge. We need to work closely with that section. So again, the mentee might have a little part in that. I'm not really sure how that's going to play out. Again, we have to decide that as the community. So does anybody have any questions about like kind of where this task force mentee program is going? Well, OK, then I'm just going to keep moving on again. And I know, Anice, you saw this last week. That was in the onboarding. Yeah, that was the onboarding. We'll get there. But so some of these also I left out here, which I really do need to add is user guides for people coming into the community. Again, that's a little bit onboarding, but we're working with the onboarding task force for those things. So each project should, you know, everybody should be able to use the project through the documentation. And we should be able to supply the users in the community. This works. Oh, it's going to I got a little fancy and I put the users that I took out of what I gleam from Ben's presentation last week in here. So there are the maintainers, which are again the most important people we're trying to help, because if they don't have the documentation, right, no one else can use the use their tools and their projects. So the maintainers have to they're like almost like the code managers. And then there's the coders. So those are new code contributors, people coming into the community. How do they know which project they need to go to? How do they know how to do their first best pull request and all that other fun stuff? So there needs to be documentation for that as well. And then if you're a new TOC member, again, this is a little ancillary, but there's policies and procedures as TOC members we need to follow. That it's nice to have them somewhere. Again, they are somewhere there in the TOC, but you have to dig for them and find them and we're trying to make everything a one or two click find. And then there's the SIG chairs and task force leaders who are not TOC members, you know, they need to know how to set up their meetings, how to control their calendars, how to do that. And they should be able to find that information pretty quickly, whether we create videos for that or, you know, again, that would be up to the mentee and the information that we can, you know, pull out of the needs from the surveys and then community contributors. People who are just interested, business owners, business people, you know, I'm an employee of a telecom company that's been going to a hype that my boss has been talking about a hyper ledger meeting. I don't know what that is. I want to research it. I want to see what he's talking about. How do I get into the community? I mean, there's really no easy way, except for the Wiki page and the website, which, again, is something that the onboarding committee is taking on. But again, these users, these personas, they all kind of need to have help getting and creating once they're in the community. We also want them to use the templates and create new materials. So again, one of the things that if anybody wants to tackle, so whether you're the mentee applying, you can help out the task force right now and just get a flavor for it. Or again, anyone who wants to jump in and just help. All you need is your Linux Foundation ID, and then you'll get this toolbar here to edit if you want to add what right now, what documentation you think each one of these personas should have would be great. Again, we do have that GitHub. For the maintainers or number one clients, as I call them, which we need to fill out to make this easy to add content and someone to control that. And again, Tracy in this task force is the one really who's been spearheading that. And I know she could want some input from other people as well. So let's go back. So if anybody wants to start tackling any of these projects, that's great. We'd appreciate the help. And then as I did this, I was so proud of myself. I found out from the onboarding task force in the YouTube video from last week that there's a new logo like I just got so crazy. So we're having I'll talk about that in the next part of this call, which is onboarding. But does anybody have any questions about how to help out this week? Or again, if you just want any of these things to be expanded on would be awesome. Any questions before we move to onboarding? Hi, can you explain the personal part and what do we have to do that? Actually, sure, I'm going to more get into that with the onboarding. But hold on, let me just refresh my screen so I can get rid of the blue in the call and presentation. And I'll show you how to access that from the onboarding call last week. Ben, who works for Hyperledger, they're all coming out with a new look and feel for the website, trying to make it easier to get places and they're looking for the task force's input. And so he gave a presentation as to where the website is getting a whole read, redo soon, so everybody's waiting. And when he did that presentation, I just grabbed kind of what I thought personas for documentation would look like. And that's what I came up with. If anyone thinks there should be more people on here, less people on here, please add a button, stick a dot in there, write a note next to it for, you know, jump on a call with me and we can figure it out. But those are the people. And now my next step or our next step is to figure out what each one of those six groups needs, you know, and how to best present that information to them when they are onboarding. So again, documentation is going to be working really closely with three groups, the mentorship project group to offer documentation assistance, the onboarding group to offer the documentation backup for people coming into the community and the best practices program to find out what each project needs to get that best practice badge and a documentation lens. So again, those are just the personas that I thought needed documentation support. And I'm not really sure what each one needs. So that again is where kind of the task forces is discussing what each one of those groups would need in a best practices avenue and in an onboarding avenue and any other avenue we can think of. Did that answer your question? Yeah, definitely. Thank you. OK, great. So again, if anybody wants to, this is our wiki page. Anyone can edit it. Just put the date you're working on something and just start at the top so that it's the next thing we see when we come to our meeting next week. And any help is greatly appreciated. So if there's no more questions for documentation, I'll open it for just another few seconds. No. OK, then I'm going to move to the onboarding task force. Now, again, you'll see the same little graph that I put on both. So today for onboarding, let me recap what the onboarding task force is. Again, we were looking at the wiki page and the web. Actually, we have a few places where people come in. One is the website and we had looked at use and learn and participate. And we had our opinions on that. But you have to watch Ben's video, which is up here. I'll show you the YouTube link because the website's getting completely redone. Menus are all being done. And again, he went through it and asked for opinion. So he's they're interested in what we feel is an easy way to onboard people from the website. The next thing we were talking about is the wiki page and the get started and the initial get started page. All it has is a 12 minute or not a 12 minute, but a six minute presentation. It's a great presentation, but we decided that it's probably best on that page to have some quick links to other things, not just the presentation. And maybe have some of the information from the presentation tabbed so you can go right to what you're looking for. So we were discussing that and that's something that the mentee will be working on as well as this task force is to what that onboarding wiki page homepage needs to look like. We're also looking for assistance from other task forces that have to do with the start here and the best first issue information too, because that's part of the onboarding process for those new coders. And then the other place was the GitHub and Elena was going to give us a report on that this week, but she's not here. So that her report was going to be what happened for her recommendation here was going to be what happens when you hit hyper ledger from the GitHub repository, as opposed to anywhere else. Is it easy to maneuver? Is it two clicks, one click, 10 clicks, that kind of information? And Divesh, did you do the discord channel? Yeah, I noticed some points and I do have them written. OK, do you want to edit this page and share your screen? Do I need to write the points, which I think should be no, no, no, no. If you want to add them later, that would be helpful so that we have them. But if you just want to discuss them, that would be great too. Sure, I would like to discuss them. Should I share my screen? Oh, yes, let me share. Sorry, I knew there was something I was missing. Well, just for some having a problem with that. There we go. Yeah, so is my screen visible? Yes. OK, so. So the first thing I noticed was the welcome screen. No one really interacts in the welcome. So I think there should be a new welcome channel for the newcomers only. And before that, I would also like to discuss there should be some rules written for the newcomers only. Now, these rules are basically on code of conduct, but I think there should be rules for the newcomers so like they can it can contain some links regarding the documentation on how to get started, what is hyper ledger and some like calendar links, etc. On meetups, the next thing I would I think should be included is newcomers meet or which can be done frequently, weekly or monthly. In that, the newcomers can introduce themselves and and I think we can tell them what a hyper ledger is and what is the goal of hyper ledger and how they can contribute in it. So I and I think there should be a welcome channel after that. And in the in that channel, they can introduce themselves themselves basically and ask doubts. Like as of now, like when I came to came in this group, I asked my question in the general because everyone was asking their questions in it and no one was asking in the welcome section. The next thing I think should be we should have a good first issues channel which can like have the good first issues which are there in the GitHub projects so that the newcomers can know of it and contribute in it. The next thing I think can be a FAQs channel. So like common questions, how they can contribute resources and many other things which I cannot think of right now. I'm sorry. So I think these are some points which I noticed can be improved upon. Yeah, thank you. That's great. I didn't even consider that like what was or wasn't on the welcome channel. So thank you. That's wonderful. Yeah, thank you. And again, when we're doing as part of the task force. Trying to redo the discord, that's something hopefully you'll work with the mentee with with your suggestions. Let me just fix this. Update. OK, go back to this. OK, so I put. Basically, real quick, what you had said for the welcome screen, there should be like the calendar, meetup information, information about when the local meetups are information on how to get started. And I do love the idea of a welcome channel where frequently asked questions could be or common community questions and a good first issue channel. So really, thank you for that work. That's that's wonderful. Again, I know Tracy had been talking about those frequently asked questions, and that is a great task for one of the mentees to work on. You know, so that's something that when we're working up here on. The deliverables and the timeline for the mentee. That's definitely I should just put it up here now before we. The technical term redo. Perfect, my technical terms. OK, so to recap, OK, so we'll go over Ben's presentation a little bit. He had. And the link is again right on that wiki page. And I'll show you where on the wiki page. But he had talked a little bit about it or so slow. I just put it in such a long. I will be out of the show as well. So if you go back, let me see if I can get to. He has definite insights from the website. I think we had it over here. We're going the wrong way. The. Right of being on the onboarding side. Households. Getting people right to the content quickly that. In this project, I'm sorry about that. I don't know where. But if you want to watch this video, it introduces what the. New logo looks like, which is this. If that's what they decide on. So it's nice, it's clean, it's sharp. There's a new look and feel for the website. And this is the information divest that they had supplied for the person. Personas for the different. People coming into the website and how we can assist them. So I thought that was interesting. And again, I kind of use that a little bit for our personas for the documentation part. Here's a link to that YouTube video that was very informative. One of the things that I need to do now is for other reasons for for other things that I'm working on, I don't want to publish new things that have the old website, if it's going to change within a week. So I'm going to try to get access to maybe some Google Drive or some Wiki page that might have early access to some of those that we can use in development, not for publication until obviously the announcement of the new website. But to get started working on that, I think that would be good. And again, for onboarding, I still think that these are the same personas. These are the people, community members are going to be a lot of those people such as academia, such as the media, such as different avenues. They're going to come in as community members. They're not going to come in as new code contributors or any of these leadership positions, maybe a sick chair. But first, they have to be a community member to be a sick chair because it's hard to know what you're leading if you haven't been involved. So again, those are the onboarding people. I think that we're going to hit. We're going to see new logos. We're going to see a new website. And Ben would like suggestions on the website. So if you do have time, watch that YouTube video and again, edit the page with the date you're editing and just say suggestions for Ben. And, you know, after watching the video, hear what he needs suggestions on and put your thoughts down. We'd love to go over them and get some new ideas. So that would be something that if you want to look at anyone on the call can jump in on that task. Again, we do have to we do have two weeks before we have to do like a timeline for the deliverables for the mentee project. But we have to see if I have a link to that. This is it. I think this is the. Oh, nobody is it. Should go to mentorship projects at the bottom. And again, the expected outcome. Is this documentation on word? OK. Would be to complete some of these tasks. And again, we've also added some tasks for the start here and for the website, the home page. So that's worth looking into and figuring out for us how we're going to timeline that out for a mentee to accomplish the tasks. But again, I like the Discord Channel as a way to get started for a mentee in the timeline. So I think that's a really good way to begin. Let me go see if there's any other points for today. Yeah, and just discussion on the personas like where these six people, where would they come into the community? We do still have. The start here are recent issues, I think I called it, and suggestions for that. But we really need to talk to and figure out who's in charge of those pages right now and how we can help with that. So that's another task for this task force. No, I mean, to use tests go up, but they're deliverable for this task force is to figure out what's going on with the start here, how can we enhance it? And I know that that's more just for the one persona. And does anybody want to take a crack with David at this wiki page getting started? So when you get getting started, getting involved with Hyperledger, you go right to the link to the PowerPoint. Again, we want that to be more marketable. We want it to be a way for all the personas because everybody you see the homepage of the wiki get started that you're that's where you're going to go, no matter who you are. And if you see your quick link, and again, that's something we need to work on, what those quick links will look like to get you one click away from where you need to be to get involved in the community. What else do we have down here? Just our analysis of the different places and the presentation that this slide was taken from. These would be the people that, again, are coming into the community. There's the link for Ben's YouTube video. Anybody have any comments? OK. Well, I hope everybody jumps on a task. I'm going to start putting out a page, a subpage on the onboarding and the documentation task forces for Timeline, and I'll start working on the exact deliverables and go look at the mentorship program and see how many weeks. And again, if there's more people from India on the call, I think it we could go a couple hours earlier rather than keep you so late in the evening. We can start it not. I know Tracy's out in Arizona, so maybe start 10 or 11 instead of noon, something to discuss at the next meeting. Again, does anybody have any comments, thoughts? Yeah, probably if you started an hour earlier, it would be better. I'm sorry, I didn't hear you. My computer is coming in and out. OK, probably if you can start an hour earlier, it would be better. So the timeline earlier, yes, I will do that. I will. But check your timings also. It shouldn't be very early morning for you. All on the East Coast, so I could go three or four hours back. It's just the people on the West Coast that it's the middle of the morning. It's like 5 a.m. or 4 a.m. Oh, but dropping it back like an hour or two is not a problem. So that's something I'll ask David about next time I have him on a call and see if we can maybe start at 11 or 10 if it doesn't conflict with any other calls in the community, we'll see if, you know, that's something we can do. OK, no worries. And hopefully maybe they'll you'll see a calendar change during the week for that. Yeah, actually, if you make it one hour earlier, there won't be any conflict. But if you make it two hours earlier, there is a conflict with Hyperledger, a special interest group. Yeah, OK, well, thank you for making me aware of that. And I'll put that in my email to David that I'll ask for the time change. Yeah. Thank you so much and thank you so much for your help. Anybody have any more questions? All right, I'm going to close the call. Thank you all for coming. I really appreciate your time. Thank you. Have a great day. Thank you. Bob, is just before we close the call. Yes. I sent you an application to the link. Can you please check that out? Yeah, I saw that you linked in me. That was great. Thank you. Yeah, cool. That's I'm trying to get to 10,000 followers at nine thousand. No, I actually sent you an application for review and you still to check it out. So. Yeah, I don't think we start until the application process closes. So we really don't have access to the mentee's information. Well, you know, there's no reason that we, you know, you and I, you know, can't continue to work together, but we don't look at the applications until the program closes for accepting. Oh, I see, I see. I was not aware of that. Thank you for that. So we have two more weeks. That's why it's great that you're on the call. Get an idea if this is where you want to be. I appreciate it. Yeah, yeah, yeah, that's good. Hey, thank you, everybody. I'll see you next week, maybe an hour earlier. Bye. Bye bye. Bye, everyone.