 Hello. Hey, how are you? You're up early after a holiday. Must be torture. If I would have taken an extra day if that was. If it's just the three of us, I guess we could do this very fast. That is true. Yeah, well, yeah, speaking of, yeah, you probably saw John is not able to join today. Yes. But I do have like two agendas for each one of the different task force. If we want, we can go through them pretty quick. So let me get to my screen sharing option. Thank you. Thanks for joining. Yeah. Hi everybody else. Okay, so this is my screen. There. Okay, are you seeing the hyperledger calendar meeting thing. Okay. Let's start with the onboarding task force. So again, we've been asking the questions. The first part of the task force, the first task we were going to accomplish was where exactly the people come on and what onboarding content should be there when they get there. So we started to analyze the different places they come in. And I was hoping today, we would be able to wrap that up with Peter and John. We'll see I can send them an email and see if they have anything, but they were doing the website. So when you hit the first two buttons on the website for use and learn, Peter was researching that and he was going to have his recommendations. John did participate and he had his recommendations last week and he thought everything was like looking good. There was a one or two recommendations and I'll ask him to put them in the table when he gets a chance. And then the next part was the wiki page would be the next place that you come and the start getting started button on the right. And then the first thing in the getting started button was the your presentation, David, which is probably a little out of date at this point, but which this was the agenda for. I thought that the, it's great, but it's 10 minutes. And I thought maybe links in case somebody just wanted one of the four topics. Actually, I'll write that in there. So like if you're just going to figure out how to do like this, and you don't want to watch the whole 10 minute video. Can I get from, from that. Getting involved page. So let me just write that in there quick. Quick links, right? Okay. And then the next was the frequently asked questions and let's see if I can get a bigger open up for me. Yeah, and those are probably also fairly out of date. Can you see those better? It's a little small, but that's fine. Yeah, so there's like, in my opinion, there's like a lot of questions. My only thought would be to maybe categorize them for what, you know, what they might be asking about smart contracts. And there might be a couple of questions in this list that are about that. You know what I mean? So, so you get to the frequently asked questions and you can more whittle down. Yeah, categorizing is a good idea. Yeah, it's a lot to sort through. You're right. You know, so I was just going to say maybe, and again, since this project got accepted at the mentorship, these are things that I'm assuming the mentee's going to be working on. Yeah, that's a good question. Yeah. So, I think the other thing, I think the other thing there, Bobby is just to update them. They seem a bit out of date. Talk about Jura. We don't use Jura. Right. So yeah, I don't, I mean, obviously I didn't look at them all, but it just feels like they're maybe potentially a bit out of date. For sure. For sure. Yeah. I don't think anybody's taken a real pass at it for a while. Yeah, that would be great. And then the Linux foundation ID just brings you to the Linux foundation signup, which I think is great because then that's, you know, the first step. So that's what I was looking at. And I know there was a few other places like, I don't know if on the wiki page, you know, what else if we want to, as the task force slash mentee mentee mentorship. Do we want to tackle the layout of the wiki page to maybe make it more modern, more readable? I mean, this is a lot of information. Right. When you hit your eyes. No one's going to read all of these little things unless you're, like, again, I'm not looking to go to a repository and do something. If I did, I would be going to that project page to look. Yeah. Yeah, I agree. Yeah, I agree. And I think that's totally within scope. We had talked about hoping that somebody with some UX skills gets that mentorship positions if they have thoughts. Yeah, if they want to say, hey, the UX of the wiki page should be whatever. You know, I still think this is all the stuff is important, but I don't think right here it's really readable. Yeah, I agree. And that speaks to, oh, sorry, go ahead. So I was saying that this data can be presented in a much user-friendly manner. I think the work should be more design oriented for you. I think we need to improve this as well. Yeah, for sure, for sure. And I know that Niku, last year, the mentorship program that you were involved in, correct me if I'm wrong, but there was a lot of UX work there and mock-ups. And maybe there's some stuff we can borrow or repurpose from that or build on. So yeah, I think UX of any of these pages is certainly within scope. Yeah, yeah, I had made some mock-ups for the sites and as well as I had added, improved the start-up website. I can just paste the demo over here, just a second. Yeah, this is, yeah. And if we could maybe wireframe something up or do something like that, you know, have some options, I'm not sure what task that would be under, whether it would be something the task force would do or the group itself. So yeah, we're going to call that the recent issues, right? So I'm going to... And just for some historical stuff on there, that was always intended as just like a temporary thing just to prove the concept of how do we embed content, you know, on the Wiki that is maybe more dynamic. It was never intended to be like the final ultimate solution. What I thought was the Wiki right now is just very static. How do we bring some more relevant up-to-date stuff in it? Yeah, so I guess for wrapping up this week and until we actually get the mentee, we can just keep plugging away like this. And if, Niu, if you want to jump on this task here, recent issues and get some recommendations for the group, that would be great for next week. See you added something. Sorry, I didn't get it. Let's see what he added in the chat. Sorry, I didn't get you. I was volunteering you to analyze that part of the Wiki page and come back with your recommendations next week. Yeah, sure, I'll do that. Thank you so much. And then I just clicked the link you put in the chat. So we're waiting for my very slow computer to leave. So this was my last year of work and I had made some designs. Actually, I had a meet with David and he said that lots of design implicated, kind of like it was just the replication of the main hypothesis. I think we can make use of some of those markers from here. It's awesome. Yeah, for sure. I mean, yeah, so I think the question is where does this go? And this, I think speaks to the analyzing the traffic flow. Yeah, some of these maybe are things we want to implement on the website. Some of them are maybe things we want to implement on the Wiki. Some of them are maybe things for start here website. So I think this is great. Yeah, we definitely want to build on this. Just could you just quote with the third, the fourth one, the developers one, the section here, this one. So this is a page which I designed like if a new contributor wants to contribute to some of the projects, he can just filter, he or she can just filter upon the projects and they will be list of recent issues and just presented in a better manner. But I was saying that the Wiki page needs to be in a better manner. I think I have to log in first, I apologize. See if that worked. I don't want to do this. All right, well, I don't have access to get in. Do you want to share your screen instead? Yeah, sure. Is it visible? Yes, it's. Yeah, now. Uh-huh, yeah, I see. So it was this one, yeah. So I just created what I was talking about the Wiki page, right? So here whenever newcomer comes to site, yeah, he can just click on those tags and just have a list of recent issues. He can just filter based upon the X tag which he needs. For example, there would be some issues that require Python based upon the projects he can filter. So this was just a better way to represent that Wiki page which you were discussing about. So this is just a better way of representing that. I think that's great. And then, so this wasn't implemented on start here yet. These mock-ups would need to get built out. I just created a website for this. I deployed it as well, live deployed in here. But I guess the code is not that optimized. So it might take a lot of while. So it's taking too long. That's what I was telling about. That's it. So great. Yeah, well, and we don't have to solve this today, but yeah, this is a good example of how I think there are resources in the community. It's just a matter of helping people find them, right? So that's great. Yeah, I think we can pull all this stuff together and have a workflow of how we want people to go from the website or the Wiki or wherever and end up on these resources. Yeah. Great, great, great. Okay, thanks. And that leads to one bit of feedback I had, Bobby on your chart, maybe just one thing to consider adding. Uh-huh, I'm listening. Share my screen again. And again, we don't have to fill it out right now, but maybe some columns to add to it is maybe we want this would speak to the impact that these changes have. We may want to look at the metrics today to have a baseline of how many people are seeing a given resource to start here website. And then after we make these UX changes, see if there's been an increase in traffic, because if we want to improve the workflow and get people to these resources, it'd be nice to see a change. So we can have a column that says what is the traffic on these different resources like the FAQ page or whatever it may be. And then if we want to have more people see it, you know, what is the traffic after we make those workflow exchanges? Yep, that sounds great. Be a nice way for the mentee to see that they've done something tangible, right? Like before I started doing the work, it was this after I did the work, it was that. That would be awesome. So again, and then it's just, I guess the mentee ship, when did they just saw it? It's like another month, right? Or three weeks? I don't remember the exact date. I want to say I may be wrong, but yeah, it's a few more weeks. People have a while to apply. So I think now's the time, if you know anybody who's interested in, yeah, now's the time to apply. Yeah, and I think for the task force, getting our ducks in a row, so that when the mentor comes, we have specific things instead of, oh, we want to work on this, or we want to work on like, 100, but yeah, for sure. Yeah, we wouldn't want the person to sit around and like, okay, now what do we do? Exactly. So that would be good because this is forming into a nice list for that. So before we move to documentation, does anybody have anything for onboarding? Okay, and I put all those links in there. This is gorgeous. I really like this. This is really nice. Yeah, it's nice to have it. I'm going to go look at that all afternoon. Play with that. Thank you. Yeah. So that will move on to the documentation task force. Of course, my computer's slow to load. So the last time we were talking about the different how the mentorships are all tied together and how like initially we thought maybe we could group them together, but they're all separate and how now we're focusing on trying to get the mentee because this program got accepted too. How to get the mentee to be able to share what the documentation task force is developing with these mentees that need it. Did I get that right, David? So ask the question again. Maybe I didn't call it. Well, I think that what we should be focusing on now now that we got accepted and that we're getting a mentee instead of trying to combine documentation, mentee ships and all that other stuff is that the documentation candidate for the mentee needs to work on getting these projects that also got accepted in the mentorship program, the templates and the hyper ledger way to them before they start developing their documentation off of what they're working on. Yeah, to collaborate. Yeah, yeah. So yeah. So yeah, so we want the mentee for the documentation to possibly do a very early in the program presentation to all the mentees on these programs here. These are all the programs that we're pending. I think they all got accepted. I'd have to double check, but I think all of them did get accepted. And these are all working on documentation and they're all gonna be looking for some guidance from hyper ledger foundation. So if the mentee can be the person giving them that guy or maybe just task force does it, I'm not sure if the mentee would be ready for that. Exactly, yeah. That would be my concern. I wouldn't want to hold anybody up. So maybe it's more iterative. I mean, people, I think it's gonna be kind of an ongoing dialogue with the task force and these groups and we'll see what these groups do and we'll take what they're doing and try to, if it's a good idea, just trying to spread it more widely. Excuse me, so yeah, I don't think... I just wanted to put something else in here that I just thought of. So the task force will need reach out to the mentors. Yeah, I think both, yeah, ideally both... At a, so we would, oh, that's the wrong one. The task force will need to reach out to the mentors that have mentee and have their mentee show up at a meeting for documentation in the beginning that the task force will do. Yeah, hopefully there's an ongoing dialogue for all the mentors and mentees involved in a documentation project. Hopefully there's an ongoing dialogue between them and the documentation task force and the documentation task force can support what they're doing. They can report back what they're doing and then we can kind of package up at the end of all these projects. Like here are things that works well. Here's what we recommend, here are resources. Okay, so again, what I thought the, deliver the common goal of the documentation task force is to not, again, I think I wrote it up here, not try to find out what documentation needs to be created because there should be some community guidelines for how to document things just regular information for community members. Is that created already? Does it need to be like we said, updated as soon as we hit a webpage? It was like, oh, that's out of date. Like what is, and how is that system in place to do that in the future? You know, like when do we have any kind of way to, for outdated stuff to let us know it's outdated or do, you know, how do we, you know, like I don't wanna hit a video and have it be four years old. Oh, you know, technology's not there anymore. Most of it, there's changed so much. It looks so much different. So that's some of the questions. And again, I'm trying to get in my, this one is hard for me to scope out. Like onboarding is easy because you have certain landing points and it's very like, you know, you can pinpoint the tasks. Documentation, it's all over the place. There's so much documentation in the community and I'm trying to figure out what the focus is. And I know one of the focuses is to get that common user guide and that hub repository from the other lab, you know, working and alive again and have some people look at it and pay attention to it, you know, so that this looks, you know, it's perfect and everybody. We may have missed your audio man. I think you are on mute actually. You can't hear you. Bubba, I don't know if you're hearing us. Can you hear me now? Oh, yeah, no, I hear you. Oh, okay, sorry about that. So I was just saying that, you know, there's going to be several different deliverables from the documentation task force and I'm having a little trouble getting my head around like writing them out like one, two, three, four. So I know, again, we're doing the common guide, the common practices and user guides for the GitHub repositories to read me documents. That's definitely one of the deliverables. Another one I guess is, would you consider documentation, David, creating those PowerPoints for, like when we said get started or is that marketed? Yeah, I mean, I guess there's some gray area around some of the stuff, but, and I think for the documentation stuff, I have less of a, you know, an opinion than I do about the onboarding stuff. I mean, my thought on the documentation is, it's really more than maintainers to tell us what resources are needed, right? So maybe that's a good discussion to have with the TOC the next time you present to them, like what if you're saying you're having a little bit of a uncertainty around the deliverables, I mean, ideally that comes from the maintainers, like, hey, it would be helpful to have, you know, these three things or whatever it may be, right? I get it. So, so I was saying that from what I've understood is that do we need to come up with the proper template of what the documentation should be looking like? Is that what you're discussing? Well, I think it's, it's what the, we're making suggestions to take your GitHub repository and the readme docs and how to do that, as well as making suggestions for what documentation each project should have, and that's gonna fall into more of the best practices badges, but it's still gonna be like in the best practices, there's a documentation piece that we'll say like each project should have this, this and this. And I think that the documentation task force should determine what those points are and make those suggestions to the badging task force. And Tracy might be able to jump in on that one and tell me if that's the right synergy between those two groups. Yeah, and I think just to add to that, Niku, so we did create a documentation template lab that basically is a starting point for people to create and start their documents. I think the other piece of the documentation task force is really around, you know, what are the best practices? So, right, the template is kind of, I would say like it's there, but I don't know that it's correct if it's got everything in it that it should, if there's things that we could add to that to make it better. And then I think that, yeah, Bobby, I don't know what the right synergies are with the best practices and the badging. It feels like we're still trying to figure out exactly how all of these things are gonna fit together. But yeah, I would say, you know, let's give as much guidance as we can for people who are looking to create documentation on what should be in there, and where people are going to end up looking for that information. I think right now with the documentation, there's inconsistencies across our projects and those inconsistencies assuming that you're working on more than one project can tend to be an issue, right? Where some people have their contribution information under a developer section, right? Versus maybe that developer section and other projects is for users of the project and not contributors to the project. I think, you know, if we can just set up some guidelines and some best practices around where we, what kind of information is needed and where that information should end up, I think that would help a lot. Yeah, agreed. Okay, so we're forming around the deliverables, which is good. So I think I present all this. Actually, I don't think I know I present all this Thursday at the TFC meeting. So I'll start working on getting some points out to them and again, requesting, you know, maybe some guidance from them as to what the anticipatory deliverables are for that task force. Yeah, I think that's good, Bobby. I think if we can get some guidance from other people and what they're expecting beyond and above what's been done with the template, I think that'll help. Yeah, so this is what we have. We have a mentee, we want to move forward, you know, what are your needs? Yep. Get more information that way. Okay, anybody have anything else? I don't have anything else right now. Everybody good? Okay. Then I will do some kind of summary of this for the TFC meeting and we'll talk again on Monday. Okay. Hello, just one thing, just one thing. Sorry to interrupt. Oh, no worries. So regarding this project, which is based on like the onboarding mentor and mentee program. So is it just going to be documentation oriented or is it going to be kind of like UI UX or maybe some kind of development as well? Because the requirements is mentioned quite a number of skills like JavaScript, Coland and other stuffs. Well, there's two separate mentorship programs, one for documentation and one for onboarding. So I think the onboarding more needs the UX design. Definitely needs it. Suggestions on the website, suggestions on the Wiki page. So that's more where the onboarding comes in and let me just put a link. I have them both right here. Here is the, onboarding. Let me just make sure of course I'm waiting for it today. Yeah, here's the onboarding link. And that describes what's expected from the, what, it's considered a rough draft of what the actual day to day steps are in the mentors project. But this is what was accepted at the initial start. So it can be edited and it can be circulated to have, again, if you don't have a strong UX designer, it's not really going to focus on UX, but that would be great if there's a UX designer. So yes, absolutely. Where is the documentation test? And I don't mean to interrupt but I do need a drop in a minute. I'm going to make you host, Bobby. So you can please. No, I'm just putting this link in and I think we're all finished. There's the mentor for the documentation. And you can like, through that, see the difference between what each one is asking for. If that helps. Yeah, yeah, yeah, sure. Thank you. And then we'll look forward to your presentation next week. Yeah, yeah, I'll be there. Thank you. Goodbye, everybody. Have a good week. Yeah, thank you. Bye, everyone. Bye, bye.