 Hi, John. Hello. Hey, Bobby. Hey, David. How are you doing? You're good. How are you? Great for a Monday and a tax day. It's a big one. Yeah, those things double up your pain, right? Yeah, it'd be nice to be done with it. I hear you. Okay, looks like we've got Nico joining. Great. Layen is joining. Hi, Evan. Hello. Hey, Nico. Thanks for joining this morning. Appreciate it. Hello. Hey, Elena. How are you doing? It's my first time here. Well, that's great. Thanks for joining. Welcome. Thank you. Thank you so much. Yeah, we could do an introduction so you can get a chance to meet everyone. It'd be good to learn more about your interest. All right. I don't know. Yeah, John, feel free to kick it. We can wait another minute or two, or we kick it off, whatever you think is best. No, I think we're good to go. I think let's go ahead and kick it off, David, because usually I think we can get wrapped up here in a half an hour if we're lucky. So thanks, everyone, for joining the onboarding and documentation task force this morning. And I'm John Carpenter, and I do a lot of work with meetups and work with David and Bobby around the onboarding and documentation task force. And we've got Elena joining us today as well, but Bobby, maybe you want to do a quick intro as well. Sure. Hi, Elena. Bobby Mascara. I've been working with the Learning Materials Working Group, and I'm kind of the liaison between the Technical Oversight Committee and these task forces. So I'm organizing and trying to get them on task and to complete what we're supposed to do in time. So that's kind of like the task master. All right, thank you so much. And Nikhu, you want to go ahead and just give a little overview? Really confident. Yeah, yeah, sure. So hi, Elena. I'm Nikhu Singh. I'm currently a pre-final year student from Anatic Children of India, and I have previously been an LFX mentee for one of the projects. So this year I'm kind of mentoring the organization as well. Yeah, thank you. Perfect. David, maybe you want to give an overview and then we'll go through the current members and then Elena can give an overview. Sure. Well, nice to meet you. My name is David Boswell. I'm on staff. I'm the Senior Director of Community Architecture. My role is basically just to support what community members are doing. So I'm here in this call, and you'll probably see me on other calls if you go to other calls in the community or in meetups. And just if I want to hear what y'all are trying to do, and if there's a way I can support you, I'm happy to do that. So that's me. Perfect. And then Tracy, thank you very much for joining again this morning. You want to just give a quick overview of your background? Yeah, hello, Tracy Kurt. I am the Chair of the Hyperledger Technical Oversight Committee. Been involved in hyperledgers since, I don't know, probably in 2015. Yeah, that's about me. Okay, great. All right, Elena. So you kind of get a feel for the group that's joined here, and this is your first time. So why don't you tell us a little bit about your background and what you're most interested in with this particular task force? All right. First of all, thanks a lot for everyone for making such a profound introduction for me. So that's really nice, and thanks so much for this warm welcome. So my name is Elena Trishov, and I'm a Program Manager at ExactDraw. You probably heard of ExactDraw because we tried out the Hyperledger membership back in 2019, I believe. And David, I have worked with you when we organized the Hyperledger Community Group in Tbilisi. I was among the organizers. Yes, and we also hold a beautiful event there in Tbilisi. So I still do remember this one. Unfortunately, we weren't able to proceed with our membership. So the group is kind of... So we weren't able to come up with further events there, but I can see that you guys came up with this exciting opportunity for the groups like to involve everyone through the online events. And I can see that the group is still alive and they can see new members joining like three months or so. So it's nice that the community supports it even when we are not able to. So about myself a little bit. So software testing is the focus of the company that they work for. And quite recently we started the documentation practice and I lead the group. So we're exploring our ways for documentation and we're adopting the approach of documentation as a code. So I've seen your overview of the technologies behind it and found it very exciting. So basically what I'm looking for in this group, I want to understand how you guys try to to tackle the challenges around open source documentation. What are your approaches? What technologies do you use? So for me it's more on the learning side. And if I just in case if I can help with anything, I also will be open to that. Thank you. Great. Elena, thanks for giving us that overview and welcome to the group. And however you'd like to get engaged with the group, just let us know and we can make sure that you're part of either the onboarding side or the documentation side or both if you're interested. And we'd love to have you be a part of the group. Thank you. Okay. So I think to kick this off, we had a great meetup and David, thanks for all your wonderful help. And also thanks to Min and it really turned out to be a nice meetup around the mentorship program. And so David, what do you think we had? About 70 people that joined the mentorship live meetup event? Yeah, about that. Yeah, I can see if I pulled the numbers yet for those. But yeah, it was a good audience and there's a lot of views on YouTube too at the time. And then after so yeah, it seemed like it was something people were interested in. Looks like it was 87 people joined the YouTube. 87 people was at the top. Okay, yeah, great. I was kind of just watching it as it went along and it seemed like it was generally in the 60 to 70 group, but you know how it always varies over the time. So that's good. And I really want to say Min did an excellent job of going over and giving an overview of the program and the background of the program and the opportunity. And also it was really nice to have Daniela join the call and kind of give a, you know, kind of a wrap up to the call as well. So I thought it went really well, David, and I can see that there was good community engagement. So any other thoughts around that? Bobby, what did you think about the meetup that we just held there? Yeah, I thought it went really, really well. And I think that hopefully a lot of people apply from, you know, take the chance and fill out the application. We kind of made it so easy and, you know, here is the application filling out. So hopefully it will yield some results. You agree. Thank you, John and Bobby, for doing that. And I do think beyond just the, that particular meetup, I think there's a general takeaway we can have here that applies both to the documentation task force and the onboarding task force. I think it really shows that when we have something such as new documentation, for example, or information about how to get involved or, you know, I think people are really interested in it and we can make that available and have a lot of people check it out, right? I think this goes to maybe what we said in the past that there's interesting content out there, but it's just how do we make people aware of it? So I think, you know, the meetups are a good channel. When there's new, if, for example, we do the task force does or the mentors do a new documentation for a project, you know, we can, instead of having to just sit somewhere where people can't find it, you know, we can really get that out into channels where people do want to learn about it and find out about it. So just, yeah, I think the meetups are one way to really, you know, let people know what's going on in whatever we're doing. So I think I thought it went really well. Great. And I'll also say Niko's on here and Niko, you saw that we've got an application for the Start Here mentorship program that we're running this year. And so, you know, we've already had some interest. And Bobby, I don't know if you've seen any other applicants come through for your particular mentorship this year. I have not checked yet. I did receive a few emails, but I wasn't sure if they actually finished the application. Okay, yeah. And that's what I saw too, Bobby, was, you know, more of an interest versus a, you know, complete the whole application process. So, you know, I'm sure we'll give it another, you know, couple of weeks here to get those coming in. And David, if you have any thoughts around, you know, additional promotion for people to apply to those mentorships, you know, let me know. And, you know, if we need to even write up a blog posting or anything like that, you know, I'm glad to work with you on that. I think Men has a, thanks for that offer. I think Men has been talking to Emily about a blog post. I think Men's got kind of a marketing plan. But yeah, I'll let her know that this group is willing to help if she's needing anybody, you know, to help support further. Okay, great. And then Niku, did you see anything additional come through under then the one inquiry that we got on the mentorship program there? Yeah, I saw quite a lot of people have applied. Kind of like the number is quite promising. And one more thing is that I do have a proposal. Could you just conduct a session in my college regarding this happiness of mentorship? Specifically for my college students. Is that possible? Is it possible? Sure, of course. I mean, if you want to take some of the content from that meetup and, you know, share it, or share it, absolutely. That's any help you can to spread the word. Sure, that's great. Sure, I'll just confirm the dates and we'll let you know. Yeah, and if it's a convenient time, I can always hop on and do it. And I'm sure Min would be interested too to get the word out. Yeah, that's great, Niku. You know, we always want to do all promotion possible and get, you know, people engaged in the community. And I'm glad to help you as well. So, you know, you got a whole bunch of help here if you want it for your college there. Thanks, thanks. Thanks for that. Okay, I see that we've also got Devesh on the call. And Devesh, you joined a little bit later. So maybe you want to just give a quick intro as to your background and what you have an interest in this group. Yeah, I'm sorry for joining late. So I'm Devesh Meena and I'm from India. I'm currently pursuing computer science from NIT Jalandhar. So and I have been exploring hyperledger ecosystem for a while. And I have done a few contributions also. And I'm looking forward to contributing more. Thank you. And what hyperledger projects have you been contributing to? What is kind of your focus for that? I'm a business. So I have been contributing to the BESU documentation. Good. I have made two PAs up till now. Nice. Okay, well, thanks for joining, Devesh. And, you know, any way that you want to get involved here either with, you know, helping with the onboarding process or helping with documentation. You know, don't hesitate. Yes, definitely. Yeah, I'll be very interested in it. Okay, great. I'll just post my email in here if you want to reach out and I can give you, you know, point you to resources if that'll help as well. Sure, I'll look into it. Okay. Next thing is we should just talk about, Bobby, you want to talk a little bit about any updates on the documentation side of the coin here? Sure. I was wondering which one we were going to start with because I have them both ready. So let me share my screen. And we're starting with documentation, you said. Hold on just a second. If it's more convenient for you, Bobby, we can start with onboarding. Let's start with onboarding since you're... I know, I'm all about whatever is easiest for you. How does that sound? I think onboarding might be easier. So I'm going to go back to onboarding. Let's do that. That's a great idea. Because documentation is the one I'm still having some need for clarity in my own perspective of it. So, again, this is the onboarding task force, the onboarding task force. And, Don, when you were referring in your conversation before about the start here, you were talking about the onboarding, correct? Yeah, start here is really what... I think that Arun last year did a wonderful job on the mentorship to get that kind of put together in the framework. And I think that's really a great place to consolidate the onboarding going forward. And that's really what the mentorship that I'm working with Niku and Peter on, trying to drive that to greater fruition in 2023. Okay, so as it stands right now, I just wanted to add that in there, so don't forget. Where we really are on the task force is we're still trying to come up with recommendations for the different points of onboarding. And we now have a few more points to go through. So I'm going to recap real quick the entry points. So as a new user, you're going to come in on the website, the Wiki page, the Get It! Hub Discord, or recent issues, I'm not sure where that, I think this is up with the website. But I'm not sure, this is a, Niku, this is your stuff that's fabulous that we have to incorporate everywhere we possibly can, because it was wonderful. But so I think Peter was going to go look at the website and go through the different links for use and learn. And I'm not sure if he's just busy during this time so maybe we can also assign that to someone else. And what that basically is, is you go to the website, you go to the button that says use, you go through all the links and come up with recommendations as to how we can improve it for people who come to the first time to the website. And then John, you had gone through your participate and you said everything, I'm not really sure what your final recommendation was, I think you were going to add to that. Yeah, I'll add it in there, Bobby. There's just a few tweaks that need to be done. And as we talked about on a call, a couple of calls ago, it was for the web developer at Hyperledger to make a few changes and kind of do that integration deal. And again, that's probably something that we should talk about after we go through this link. And I think that's something that we should talk about after we go through this list is how do we get changes to the website and not step on anyone's toes or do they want our input, like how is that going to work? But that's probably more for the end. So then the next thing was the Wiki page. And we had looked at this piece here and then David said that he was going to look into maybe updating that presentation that was there. And the only recommendation we had was for some quick links on that page where the presentation is depending on who you are. So not everybody needs the same presentation. So maybe have quick links for developers as opposed to sitting chairs, whatever, however that's going to look. And then the GitHub, that was new, so no one's done GitHub or Discord yet. So if anyone wants to go over as a new user, hitting those two locations, what you see and how easy it is to navigate, we'd appreciate that. If you want to just raise your hand in the chat or write in the chat that you can do that, that's great. And we'll add your names in here. And I think next was the frequently asked questions and that was from the Wiki page button here. And Tracy was going to, I think, look at those a little bit. And our recommendations were that they should have categories and they should be updated. And then the last piece to the getting start and butting on the button on the Wiki page was getting an ID and that's just pretty much self-explanatory and should be there. The recent issues that and what Niku brought up with this wireframe, again, this is where I need some guidance. Like if this group comes up with recommendations for the webpage and say Niku works with the mentee on what that looks like, how does that work, David? Are we going to be able to get that through? You know where I'm confused, I guess? Well, yeah, I mean, so that's a good point. And I think this is why it's helpful to do this audit. And so there's multiple entry points, right? And different people are involved with changing those. So like the Wiki is straightforward, right? Like I think, you know, if we want to make changes to the Wiki main page, that's more straightforward than making changes to the website, for example. But for the website specifically, that's, yeah, something we'll want to have a conversation with Ben about. I think the timing works out well. I think I may have covered this in the past. He is working with an agency right now to redesign the website to fit with the new brand that he presented a few weeks ago. I have not seen that yet. I think one thing we can do is when there are some mockups or when there's a staging site where it's under development, if we could get access to that and share it, you know, I think we could have, hopefully have some feedback with him back and forth. We can review it, send some ideas, thoughts. That's what I'm hoping. But that's not to say, you know, I think at any point, you know, I think even after the new website goes live, I think, you know, we should always be able to give him feedback, right? But I think the time is particularly good right now since they are in the process of developing a new site. You know, so that's what I would say. Like let's get our recommendations together when there is something that he has to share, I'll share it and then we can, you know, give him feedback on it. Is there any way that you could maybe see if he can come next week to the call and show us where he's at? I can ask. I mean, I did ask him last week and he hasn't, he doesn't, there's nothing to share yet. I think it would probably be best to invite him when there is something he has to share. What about the reverse if we showed him some of the stuff that Niki was working on? We certainly can. Yeah, I mean, we can invite him. Yeah, I mean, absolutely. Yeah, I guess that would, you know, because again, we don't know how much work we can do on the website until we hear it from him. Sure. And the website is going to change substantially. So like what, you know, what we may be looking at, you know, we might be recommending changes to a page that doesn't exist anymore, right? Yeah, exactly, that's kind of want to spin our wheels on this one too much without getting some clearance. Well, yeah, that's why I was thinking the next step would be let's see what it is that he's doing and then provide feedback on it, certainly. I think I'd shared, he's told me his general approach to the new website. And so that could help us with our thinking and just to share again what I have heard. He's trying to radically cut down on the amount of content on the website. He's analyzed the user flow when people come to the website and they, as you might imagine, is basically just scanning. Like people don't spend a lot of time on a page. Like what he's hoping for is to provide a very scannable website. And then when people find the thing they want to dive into, link off to it so they can then do a deeper dive. So like have, I think his view of the website is very like bullet points, right? And headings and that sort of a thing. So there's not going to be a lot of content as it were. I mean, he really wants to see that deeper dive content in other places like on the wiki or on GitHub or wherever it may be, right? Yeah, no, that makes complete sense. One question I'd have for you, David, is has the agency provided Ben with a heat map of the Hyperledger website? And based on the user experience there, that might tell you, you know- Of the current one? Yeah, the current website. I imagine, yeah, I'm not fully in the loop on the website stuff. So I don't know the answers to that question. I would suppose so, but I don't know for sure. Okay, yeah, no problem. I think where we're coming from, David, is we want to be collaborative with Ben and make sure that he knows we're here as a resource, but he's driving the new design and knows what he wants to accomplish. And we want to be collaborative and let him know that we're here to help not hinder his design. No, that's great. And I think we definitely need to have a conversation with him or want to have a conversation with him. It's I'll defer to you about when, if you want to do it sooner rather than later or wait, we could wait until he has something to share or talk to him before. I mean, whatever y'all would prefer, I can reach out and invite him. Yeah, I think where Bobby's coming from is great. Kind of like, hey, Ben, if you want to join the call for five or 10 minutes, just have a quick intro that you know we're here to collaborate with you and follow your design lead and just provide additional content that's going to be helpful to the user experience. Let me invite him. I'll ping him and see what he says. Okay, and if it's not convenient for him, David, no problem. He's not a part of this group, but he's kind of critical to what we're doing here that we want to be efficient about what we're designing and providing to him and not, you know, impede any of his... Sure. I will ping him and I'll let you know if he can join and we can put it on the agenda then. Great. Thank you very much. That's awesome. Sure. Okay, Bobby, great job on that. What I'll do is I'll also ping Peter because I know he wasn't able to join today and find out about the use and learn tabs. And if he's not able to complete that, I'll work on that between now and the next call. Perfect. And I will ask Elena and Divesh if they want to put their names here on the GitHub and the Discord. And all you'd have to do over the course of the week is pretend you're a new user and go to those two locations and maneuver around and come back and report back to us how easy, hard, and what you think should be changed. So, Elena, if you're interested in jumping on, would you like to do the Discord or the GitHub? Let me start with GitHub. Perfect. So, as a new user, you go to the Hyperledger GitHub, maneuver around, and then next week come back and let us know where you think as a new user it would be confusing and how we could probably make that better. That's wonderful. Yeah, it's helpful. Thank you. All right. I can do that. And Divesh, can I put your name on Discord? Yeah, sure. I can do that. Great. Thank you. That would be very helpful. And the thing left is, David, do you have any idea on a new presentation to a welcome community kind of thing or do you want the mentee to work on that? Oh, an update to the how to get involved presentation? Yeah, because we kind of need weekly tasks for the mentee to do on onboarding. And until we know what the redesign of the Wiki page for new users is going to look like, I'm thinking that might be something he can work on too. He or she could work on. Well, to step back a little bit, I do like having a clear task list. Maybe we do need to start developing that. Yeah. I would say, again, my thought on the task for the mentee is more of a workflow diagram. Like we've got all these different web properties. We've kind of been viewing them individually. Like Ben is looking at the website, for example. But I don't think there's any really flow about how these things all fit together into a larger universe. Like how does somebody go from the website to the Wiki to GitHub to this, to that, the other? Like I would, I personally would think it would be helpful for if they've got the UX skills for somebody to start putting the workflow or web flows together. Yep. Yeah. You know, isn't that Niki, what you were working on? Yeah. I had a few things. So regarding that. Well, I think, yeah. I think we said that go to Wiki patients so there's some things such where we can improve those things. So let me just present something that is working well. And I have to drop in a minute. So I'll just share my thoughts real quick. I mean, I think what Niki did last year was great. And I think it's my understanding and maybe I'm wrong, but those were updates to or recommended updates to some existing pages. But it's still, I think my main thing is how do we get people there? Like if, for example, this page, like how do you, what is the flow? How do you go from the entry point to get here? Right? Like I think that's what we don't have yet. Right? Like we have again, we have good content out there. We have useful resources out there. It's just like, I think we need to have an understanding of how people get there, right? And I'm sorry, I do have to drop at 930, but ping me if that can help. Yeah, that makes perfect sense, David. And I agree with you 100%. So, you know, the UX design will have to show a flow, you know, an optimal way to get people to their destination as quickly as possible with not going so many layers deep into the breadcrumb trail. Yeah, because I think there are situations where you just can't get there from here to use that expression, right? Like start here is helpful, but you don't really find it from the website, right? Like that's what I'm saying. We need to connect these things together and feel how do you get from one to the other, right? But I do have to drop, so I'm sorry. I'll join next week. And hope that we can- Okay, thank you very much, David. Have a wonderful day. Okay, bye-bye. Yep. Okay, Bobby, great job on that piece. Anything else we want to cover on the onboarding side at this time? Well, so far this week's tests again was to prioritize of these, which is going to be really the most important. And I guess right now, it would be the Wiki page since we really can't touch the website yet until we find out what we can and cannot do. So again, some of these things on the Wiki page like the frequently asked questions and that intro getting started goes right to the presentation. Maybe again, if somebody wants to work on mocking up that page. So when you're on the Wiki and you go to getting involved in Hyperledger, yes, we should have that presentation there, but there should be more there so that people can make other choices than to watch the 10-minute video. So if anybody wants to jump on that one, you can either volunteer right now or just put your name here during the week. And then next week, give us your report on what you think that getting involved with Hyperledger Wiki page should look like. And then again, we all have- we all have to keep in mind that there are different users for all of these entry points as well. So these are some of the users that would be there. So again, quick links and categories are really important when you have multiple users. So that's also something to keep in mind like if I'm onboarding and I'm very technical or I'm onboarding and I'm a business owner wondering if Hyperledger Blockchain is going to work for me, they're two different ways. Those are two completely different ways to go. So let's see how that works when we're working on these recommendations for next week. Does anybody have any questions or insights on onboarding before we move to documentation? Those users that you highlight above, Bobby, are great. And I agree with you 100%. That was the thing I was referring to as kind of the- in the web world, the persona. So we should kind of flag those as, you know, here's our six personas that we need to look at for as far as- And out of these six people navigate the online presence. That would be quite a matrix to figure out, but maybe something to work on. Yeah, I think it's a great thing to work on and I think it really will affect the flow because, you know, what a maintainer is going to want is going to be entirely different than what a business person is going to want out of hyperledger when they're onboarding. Yep. Okay. So now I'm going to move to documentation. And this one is where I'm getting a little need for- I need some clarity because I'm not really sure what the deliverables exactly are for the task force and the mentee. So for me, I'm thinking just initially for the mentee and I want our mentee to work with the other mentees and I've talked to Dave a little bit about this because down here I listed all of the mentee applications that had documentation needs and I'm not sure if they all got accepted, but if they didn't, they still need the documentation needs and it's something that this task force should address. So that's one of the ways. So they're all looking for templates and guidelines. A lot of them are coming from Git Hub to read the docs and they would like guidance on that process. A lot of them are just, you know, what needs to be on our Wiki page and so far as best practices for documentation. That's another dilip. So there's a lot of nuances to the different ways the mentee can be used. So I do think this is important, but it's really hard for me to get my head around the mentee doing this when the purpose of the documentation task force is to create those things. So I don't know like how you put the chicken before the egg or the egg before the chicken. I don't know how he's going to give suggestions for these people who during their mentorship have to document when his mentorship is figuring out what they have to document. Sure. So that's my confusion, I guess. Yeah, and I agree with you on that, Bobby. It's a little bit confusing as to which comes first, right? You know, or I think maybe we do have some things together and maybe as a task force, we need to organize those quickly quickly before the mentees come on board. So here basically in task two is like what are down here is what are our deliverables? So that common style guide goes back to that's on board and let's say this. So as Tracy had mentioned previously, there was a mentorship program a few years ago that tried to tackle this documentation for the developers and maintainers when they're creating the documentation for the community, which is vital. I mean, you can't use the product if you can't read about it and understand it. Correct. Actually, Bobby, this template is just new. So I just created this thing not too long ago. Okay. Is there anywhere I should be pointing from the work from that first mentorship program? That I don't know where that information is. Okay, I'll go back and look for it. Yeah, I'll find it if it's and see if it's relevant. Yeah, this is awesome. Maybe Tracy, you want to talk a little bit about since this is new, what we have here and how that might apply to the mentorship. Sure. So this is a template repo that other people can use when they create their documentation. So for new projects or projects that are looking to revamp their documentation. I know Stephen Karan used this template when he created his AcroPy documentation site just last week. So this basically uses material for MakeDocs, which you can find a link to. And we also within Hyperledger have access to the insider capabilities within that. I'm not sure that this template specifically uses any of the insider capabilities, but obviously people want to for their documentation they can. What this basically does is provide a template of suggested, like a suggested table of contents, if you will, for what should be included in documentation for new projects. If you, that's okay. I was going to say if you click on, if you go back and click on at the top right, there is a link. Yeah. If you click on that, I'll show you what this actually converts to with basically the different, at the top you can see there's a menu, introduction concepts getting started. So these are basically the recommendation of what we would want to include in any sort of project documentation. Obviously people can change that if they think there's something else that they need to improve specifically for their project. This particular page here just gives an introduction on what this repo is and what changes somebody would need to make in order to make this reflect their particular project. So like for example, this site name HyperledgerBevel right now, it's set for Hyperledger underscore project and you can see that at the very top of the screen where that's basically the title for it. You can also then specify the repo, so which repo you would go to if you click on at the upper right right now for this particular template except for HyperledgerLab slash documentation template. So basically these are the instructions that you would, exactly Bobby, these are the instructions you would go through to make sure that this gets updated to reflect whatever your project is. And so yeah, and then it really is just creating the documentation to fill in each of these different concepts and the getting started pages for how you install it, how you run it, different tutorials that you might want to provide for the people who are going to be using your project, different sorts of guides, be them architecture guides, command line guides, roadmaps, anything that you think might be useful for people to be able to reference related to a particular project. This next section is on contributing and how you contribute to the project, how you report a bug or request a change or ask a question. Then there's an FAQ page that you can obviously write your frequently asked questions and a glossary page for making sure that people who are new to this might need to understand particular terms they can go in and look at those. So basically all of these pieces of information are then filled in in the document. So if you go back, Bobby, just to the GitHub repo, we can take a look at what that looks like. So basically what we've got is the make docs.yaml file that's listed here. This file is the one that basically needs to be updated to reflect all those different changes to reference basically the project name, the project icon, things like that. It's also the place where you create your table of content. So if you need to add any new things to the table of contents, that's where you would add it to point to the respective markdown file. And then in the docs directory, that's where all the markdown files go. And so in here, you'll see index.md. That's basically that introduction page that we were looking at. The glossary.md obviously FAQs and then separate directories for the ones that are going to have basically multiple sorts of pages. So multiple tutorials. There'll be a tutorials directory that people can go ahead and create their markdown files for that. And so basically it's a matter of copying this repo to your own GitHub repo and filling in the details, adding any sort of information that makes sense to that. And once you do that, you'll have GitHub pages that will be created. And you're off to the races basically. Nice. Yeah, that's a wonderful run through Tracy and really a nice resource for sure. And then how did Steven think about implementing that for his project? He thought it was... Yeah, he didn't have one pull request that he put into the readme itself just to provide some information. We'll see if he does any additional pull request to make things any different or better. But he definitely thought it was a useful thing. And I did take a look at his particular documentation that he created. It's really interesting. So I'll see if I can find the links here and put those in the chat just so you can see exactly how this turned out. So here's the rendered version that I just put in the chat. And then let me go find the GitHub repo for this. Nice. Okay, look at that, Link. Yeah, super clean, super easy to flow through on the deal. And then this is the GitHub repo that generates that site. So it's actually not the one that's linked. Oh, maybe he changed that. But yeah, that's the one. So anyway, this is basically what he did and he took this template and created this particular website from it. So that you can now get information on the different Ecopy and how to use the Ecopy. So I think it worked fairly well. He did obviously expand some stuff in his readme and we might want to take a look at exactly what he has here and maybe potentially update the template to include a bit more. But yeah, I think it seems like it must have worked fairly well because it was what, two weeks maybe after we mentioned this in the TOC meeting and then we've got this website set up. So I'm fairly happy to see that somebody's using it. Yeah, no, that's a quick update for sure, Tracey. And beyond Aries, does it look like any of the other projects would want to use the same framework or how does that seem from the rest of the community? Yeah, I haven't specifically heard of anybody doing it. At this point. But you know, there are a number of different, as Bobby pointed out, mentorship projects that are out there. It's very possible that somebody might decide that they want to revamp the way that all of their documentation is done and move towards this. We'll see. Yeah, to me that would be wonderful. Yeah, go ahead, Bobby. But I know in the beginning of some of these meetings about this, especially with the people from Basu, they still wanted to be able to have some choices on what their documentation looked like but still have it in hyperledger. Is this just one theme or are there other themes that people in the community can choose from that have been basically hyperledger approved or winked at? You know what I mean? Yeah, so makebacks is obviously can have can support multiple themes, right? So material for makebacks is one of those themes. So it's very possible that other people could choose makebacks but not use material for makebacks. I think the reason that I created this with material for makebacks is because we had the insiders piece, right? Capabilities that hyperledger is specifically paying for. And so that's why I base the template off of that. Now, obviously, if you look at makedocs.org, there's a number of different themes that are specified there that could potentially be used. And I think it just really depends on what it is. The other piece of this is the coloring. There's a lot of customization you can do to the material for makedocs that obviously I just basically chose something that was fairly plain. But, you know, there's options to change the coloring theme if people wanted like maybe, you know, the areas one, maybe they wanted to make it green instead of blue as the top, right? Like, I think that's probably something that they could do very easily. But you know, I do have recommendations on two color schemes and stuff like, like he'll hear picked from one of these three hyperledger color schemes or do you think that that's something they want complete autonomy over? I mean, I think we should set a default probably and then if people want to do something different, they could. I think the recommendation that I would have is let's use the default hyperledger color scheme. So I know, right, hyperledger is very branding right now. I think my recommendation would be that instead of using the blue right at the top for the thing, maybe we pick the default branding color that exists for hyperledger, right? And then, you know, maybe as an alternative, if somebody wants to use an alternative color scheme, I would recommend that they use the color of their logo, right? So everyone has a green logo, they would use the green of that logo, you know, bevel has, what is it? Something like purple, bevel would use the purple for their color scheme. But to me, I think it's one or the other, right? Like use the default for hyperledger or use the color scheme for your logo. Yeah, I think brand consistency is critical, Tracy, and I agree with you that, you know, people don't want to come to the hyperledger website and say, well, what website am I on? They want to feel comfortable that this hyperledger, you know, foundation content, and that's good. Okay, perfect. Tracy, you did a wonderful job on that, and I think if we can get more projects to adopt that framework, I think... And I want to correct the beginning of my conversation, I want to say, and now we have something for the mentee to show the other mentees how to do their documentation. Yes, there you go, there you go. So now I have a clear thing for the first training for the mentee is going to be learning this process so he can show it to these folks when Min gets them together for an introduction... Sorry, an introduction on the mentee-ship program. Yeah, no, I totally agree with that, and I think the timing couldn't have been better for Tracy to have completed that right before the mentorship program kicks off. So I think we're in great shape on that. Yep. Okay, so what are our next steps for this task force? We have time before, I think we should start at a list of mentee tasks so that we can have those clear and concise by the time he or she gets here. Yep. I'm not sure, what do you think, John, for these other style guides and stuff? Do we want to do a Wiki page for documentation with, again, the categories so that if you're looking for this, you click here, click here, or what do you think that the task force... How should the task force hand this to the TOC? Yeah, well, I'm a big fan of brand consistency, Bobby, and I feel like when you've got a structure like what Tracy's put together here that works, I'd rather have more work put into working with each one of the hyperledger projects and having a consistent documentation look and feel that's complete across the project. So I guess that's where I look at the work product being best suited to the community. Does that make sense? Absolutely, perfect. Got it. Okay, so for next week, I will work on the two sets of deliverables to get them in a clearly defined list. So this is what the mentee will do and this is what we're going to do, although a lot of it's done already, thanks to Tracy. But I think there is, again, the need for a place to look for documentation because I think that's a problem for the communities when they want to read something, unless it's specifically tied to a project, it's hard to find the YouTube videos or the... And even when you get to the projects, there's been some great videos and great sessions and meetups and stuff, but it's really hard to locate those. And that was always something without the Learning Materials Working Group wiki page, I thought that needed to be addressed, but again, that's something that we need to discuss as a task force to figure out how we best serve the community when they're looking to read something or looking to learn something. Yep, exactly, Bobby. I couldn't agree with you more. So anybody have any comments on this or want to volunteer to do any other tasks? Let's just do one thing, Bobby. And it looks like, you know, Akash, if you want to do a quick intro of yourself and your background and why you're interested in the group, I know you joined just a little bit later. That'd be wonderful. And maybe you may be interested in collaborating on what Bobby's outlined here. And Akash, I don't know if you want to come off mute or if you're on the call, maybe not. Anybody else interested in providing additional feedback to Bobby around this? Well, yes. I wanted to comment on the documentation template. So I liked it very much. And that's kind of a job that my team at X-Actress currently trying to do for internal documentation. So we are also working on the template. So I really feel what you've done here. And that's great. And speaking of that, when we came up with this problem, we decided to make a template for our internal teams to use for documenting their own projects, sub-projects. So there is no adoption yet, but because we are still working on the template. But when we started to think about it, we started also to think about the problem. So for example, we have finished our template. Then some of the teams adopted that. Then we received some feedback and decided to change the template. What happens to those who already implemented the template and their documentation? So and that's why one of my specialists came up with the idea of publishing some parts of the template into a package. And we have published it on NPM registry so that those who adopt the template, so the changes are automatically applied as well to those who are already using it even after we changed the template itself. Just something to think about. Sure. If you're interested in that, I can ask the specialist like what is the applicability and whether it can be done with this template as well. If so, I can update you on that. Yeah, that sounds great. Bobby, what are your thoughts around that collaboration? I think that's great. And if you have any thoughts, we'll give you some time next Monday and you can show us how it works and what it looks like. All right. Okay. Thank you. Awesome. Yeah. Thank you so much. That's wonderful. All right. So if anybody has anything else to say, raise your hand now. Hi. I had one question. So as you mentioned this term mentee, can you give me more info about it? I'd like to know more. Sure. So the documentation task force started a while ago through the learning materials working group. These are the recent tasks that we're trying to cover. But if you go down on this wiki page, which I'll just drop the link in the chat for everybody to make it easy to find, everybody should have it. These are some of the things that we completed before, before it became a task force for the TOC, when it was just a task force under the learning materials working group. So we wanted to try to get these four items and we did a survey initially, and these were the results of the survey of what the community wanted to see out of the documentation. And you can go through that. It's all up here. And then we did where was the documentation, what each project is using. So that's this grid here. So you'll see all the projects down this side and exactly what they're using and links to those documentations for the comparison that we did. Where's the comparison? Oh, I don't know where the comparison is. Let me see. I'll have to get a link for that. Ben did a great comparison of them. And I'm not sure where the link is, but I'll find that and put it on this page. It could be the survey. I'm not sure where it is. I'll have to find the link. But that's basically where this came out of. And then again, Tracy showed us that great result of kind of making because the results of the survey was everybody wanted guidance. They really wanted a little, they wanted more guidance on what to do with their documentation than flexibility to make it look like their own. So that's basically what Tracy kind of summed up there for that. But there's also other documentation needs other than just, I'm sorry, I'm scrolling so fast. Other than just that style guide for your Github repository, there's people making, want to make YouTube videos. There's people who want to make presentations. We want to offer them templates as well, as well as collect that information that they're gathering so that people who want to read and learn can easily access the documentation. So maybe a guide on how to access or use the Hyperledger library. We don't know what that looks like yet. That's where we're trying to determine. So I guess the first steps was with the Github repositories and make the docs, which is very helpful for the mentee program coming up because most of those projects, in some way shape or form, wanted to document what they were doing. So that's basically where it came from. Does that answer your question? Actually, I wanted to know about this mentorship program like what it is and is it available for everyone? Yes, it is. We would encourage you to apply for it. Each one, and I'm going to show you that right now. I'll drop that link in here too. So these are, let me go through this very quickly. And again, spread this information we're giving you right now to everyone you can. So I just dropped this link in here. This is this year's mentorship program dates. So you still have all this time to read over the projects and decide which one you want to apply for. We encourage you not to apply for a whole lot. We encourage you to do your research and maybe find two that you really like. Three if you can't decide, but no more than that because we really want you to be vested in it. And again, these are the information on the stipends where it depends on what country you live in. And then mentorship projects for 2023. I find this very helpful because it lists the projects and their focus. So here's the project and here's the focus. So if you go to our documentation, it's going to take me a second to find it in this list. Right here, you'll see what that particular mentee is, what we're requesting of that mentee. So each one of the programs has the information about what it wants you to do for that program. And then you would apply and then you would hear if you got accepted as the paid mentee. We do encourage people who are interested in a certain project and may not have gotten that one particular mentee position to join the project anyway. And I know that in the project that I did two years ago, and Hardik just jumped on the call so coincidentally, there was a girl, Madhu, who wanted to be a part of it and joined us and made every meeting and she actually won an award for her involvement in it from the Government Blockchain Association and she had a great experience. So there's so many ways to get involved. So don't let anything hold you back from applying. Did that answer your question this time? Yeah, definitely. That did answer my question. Thank you. Okay, so if anybody has any more questions, I guess, John, are we ready to end? Yep, we're ready to end. Great call, everyone. I really appreciate you joining today and look forward to reconvening. See everybody next week. Have a great one. Thank you.