 Hi. Good evening. Yeah. Hi. Good evening. Hi. I hope I'm pronouncing it right. Yeah. Where are you from? I'm basically from Bangalore, India. And what about you? I'm currently a student in 3rd year from Anayati Jalanda. Anayati Jalanda. Oh, nice. So is this is mainly focusing on students or like anyone? Are you asking regarding this meet? Yeah. So this meet is like we have a weekly meeting going on. So this is regarding the onboarding taskforce which we are, which we are kind of like really forming, which focuses mainly on improving documentation and other stuff about hyper leisure and other things. So it's open for everyone actually. Okay. Okay. Now that I read it. So I just wanted to check whether it is for experienced people or only for freshers. That's that's what I wanted to ask. Yeah. It's open for everyone. So are you currently using hyper leisure? Maybe you are working somewhere? Yeah, actually I am founder of the New World Innovations Private Limited. So like we are working with just starting to work with hyper leisure fabric. Actually like in fabric, we have the raft consensus right now. So like we are working on the board. So that is what we are mainly focusing on, Bini BFT. That is the BFT that we are working on. That's very nice. So I didn't get that name. It was Bini World Innovations also. Bini World Innovations Private Limited. I was in my LinkedIn ID in the chat. Yeah. I hope you got it. Yes, I did get it. Yeah. So hi David. Hey, how are you? I'm fine. How are you? Good, good, good. Yeah, Bobby said she can't make it today but I always got to say John should be here and I see John's here now. So not set up on audio yet. Hey John. Hey David, how are you doing this morning? Good, how are you? Oh, doing great. Good to catch up with everyone. I'm just going to say I see that Ben accepted our invite. If he doesn't show up in a minute or two I'll ping him. Okay, yeah. It would be wonderful to catch up with Ben. And what I really want to do is make sure we're coordinating with Ben on any recommendations that we give, especially with onboarding work we're going to be doing. For sure. For sure. Mentorship. So let me go ahead and just pull up some of this here. And I see we have a good group joining us today. So thanks for everyone. And if you want to add your name to either the onboarding task force or the documentation standards, let me know. Let me just go ahead and get into that and then I can put it up on the screen here. Let's give David a couple of minutes here to see if Ben will join us. Hey, it looks like he just joined. Hello, everyone. Good. Hey, Ben. Thanks for joining. My pleasure. Thank you. Hey, Ben. Thanks a lot for joining us this morning and we really appreciate it. And as I was explaining to the group here before he jumped on is, you know, for this task force where we have basically the onboarding and also the documentation task force, when we're going through with our mentorships, we definitely want to make sure that any recommendations that we, you know, create or content that we create is compatible with your web strategy for the hyperledger.org website. So that's why I thought it would be good to have you join us early on in the process and maybe talk a little bit about what you're doing with the redesign of the website so that what we're doing with mainly that start here URL that we can get it right and make sure that it's compatible with the new design. Sure. Thanks, John. This music to my ears. I just literally just finished listening to your previous session, I think on the 17th. Yes. Yeah, which is great. Great to hear that this is happening and it's especially for me personally, you know, I'm sometimes I feel like I'm swimming alone in this ocean of data. So I'm more than happy to get everyone involved here and some of the points that I can hopefully help touch on to shed some more light on a few things. Maybe it might be start. Would it be helpful if I just gave you a kind of quick overview on where I'm at with everything? Yeah, that'd be great. That'd be wonderful, Ben. So maybe I will share my screen here for a second. Perfect. I'll also just queue up to start here as well, Ben, and we can talk about that after you go through your presentation. Great. Thanks. So when I came aboard just every year ago, I think one of the first things I did, which I had mentioned in the previous meeting was persona development. And this had been done a little bit previously, but not really fleshed out in terms of the multiple personas that we're talking to. And so basically I put this document together. I'm happy to share it as well. And it's something that I would love to continue developing because it is quite comprehensive, as you all mentioned previously as well. So what I did before we just had two personas, one developer and one business executive. But now I've kind of broken it down. Here's the sector overview, and I've broken it down into the maintainer, the contributor, the new developer. And also one thing I would love to do is add a female persona. I'm not sure whether that's a new developer or a maintainer or contributor, but obviously when I started this document, I was looking at the analytics, obviously a benchmarked everything at the beginning of the year, all of the channels, all of the website. And the first thing that I noticed was the website was basically falling over. It's very, very low performing. I think there's a page load speed of over 12 seconds. There are multiple, I can't remember how many exactly, but there are multiple 404 pages which are getting spammed by bots. You name it, it's a nightmare. So that was part of the whole, the revamp and redoing the website. That was the reason for doing that is because it's really hampering the onboarding process for new users here in the site who are essentially bouncing. And as you can see here, this is the last year from today. The good news obviously is we've got 909,000 users here in the site, up at 18.9% from last year. 12% of those users are new sessions, new sessions and 13% are new users. But unfortunately our bounce rate is continuing to climb. 67% last year, 77% this year. So, and we really want to be in the, you know, for tech kind of content community benchmarks, we want to be in the 50 to 60% range is the goal. So these are the kind of data points I was looking at. And obviously the biggest point is that we need a high-speed, fast performing website with a low time of under three seconds, globally. And that's to ensure that we can onboard people properly and take advantage of the huge amount of traffic that are currently just hitting and dropping off here. And then the next step is obviously I looked at the first thing I did was turn on the demographics on the analytics, which weren't previously on. So happy that now that we actually have some decent demographic data to map to our developer personas. And interestingly, we've got 27.8% female, 72.2 male with the highest age ages between 25 and 34. And then dropping off by just almost 10% 35 to 44. And then the next thing I looked at lots of data to dive through here, but affinity interests and other such things. And then of course, I moved on to user flow and I'm not by any means a UX UI specialist, but I'm fairly up on analyzing a lot of the data here. Here we can see again, this is quite useful to know in terms of the personas. United States and China and India, Indonesia. I think a lot of the Indonesian traffic is a lot of spam bots hitting the site because they're hitting most of the 404 pages. And we can see things obviously like, you know, large majority of traffic is going to fabric. But, of course, we've got 78% of those sessions about so we're looking when we're looking at non bounce sessions, we gotta clear a picture. And then one quick question because I think this is I mean you you probably heard since thanks for listening to the earlier call but I to me the whole challenge here is yeah how do people flow not just on the website but throughout all our property so just to confirm this is just the www.hyperlegio.org data. Okay, great. And then I think just to preview what we're interested in is like how do we get people from like the website to the relevant place on the wiki or the relevant place on GitHub or you know whatever so yeah it'd be great to get your thoughts on how we get like the user flow mapped out on all of our websites not just the main one. Definitely. And I think this is, it's this data here that I'm most interested in that respect and also in the mobile traffic, which is 34% of these of total sessions. So that could be a lot higher because nowadays more than 50 to 60% of most sites on mobile traffic. So we want to make sure the site's optimized for all devices, especially mobile. Sure. So what we can what we can see here obviously is, you know, as as expected fabrics, driving a lot of the traffic. I think the Walmart case study was was one of the highest engaged pieces of content on the site for example. And then, then then we can kind of gauge the flow here. But I think what what I would need most help with is, you know, this is what people are doing with with the current site which is quite convoluted lots of way too much tech text text heavy. In general the average time on the site is two minutes, two minutes 40. So, David and I have rearranged the top level navigation and I think somebody else mentioned some heat mapping. That was what I mentioned. Yeah. Great. Yes, we don't we don't have a heat map installed but I have been looking at analytics and obviously from experience. Once you go below the fold you get a large, most people are above the fold you get a very large drop off once you once traffic goes below the fold of around 70% on average. So, the big question is, the big challenge was how can we essentially bring all the elements together get people to where they want to go. And that was decided. Well, the, I spoke with the web team and the LF design team and we decided to go with a mega menu. So, here is just to give you an overview. And these are all just basic designs in process here. But essentially what would happen now instead of having to go through these. Which is, again, not, not really that clear enough. We're going mega menu so you hover over about, and then you break, you can just broken down here into the whole fold, the top of the page. And this is great because it's a lot, it's a lot cleaner. You can also add featured content. This is the about page. The projects menu, for example, goes to the new projects page with the projects in order here. And for and the first question for the first section for example is question is, you know, historically fabrics been the number one journey point to touch point to do we want that to be the case or do you want at the moment we thought we want the new project page to be the main landing page. But do we want the projects in order do we want to give more, because obviously areas or you know the top projects here we're going to get more clicks than. Yeah, I think it's totally okay to have featured projects versus graduated projects but that's a detail but I mean just this. I love the mega menu because and again you probably heard this on the call you know one of the things we've been talking about. And the group is reducing the number of clicks people have to click, you know, to take to get to where they want to go this definitely removes a click. Yes, directly to fabric, for example. Yes, the two or three clicks to everything is the goal. And of course here we have in participate. Very clear links to all the external properties and groups regional chapters. I think this makes much more sense. A lot cleaner. Again, in terms of hierarchy here. I think that I think what David and I, as I think we've done quite a good job so far in terms of ranking this in terms of what's going to be most. And we also we looked at the flow on this page in particular to order this. So we have a kind of general we have a good idea in terms of what people are wanting to click on most obviously. The use menu again. Slightly reorganized. The learn menu slightly reorganized. The blog and the news. So yeah, that's that kind of gives you the general idea of the mega menu. Which I which hopefully I think solves the problem of the main navigation issue with the current website. Obviously the first issue is the performance. The second issue is the navigation to, to everything so. Yeah, that's basically where we're at at the moment with with the with the navigation but in terms of actual flow. And in doing a detailed kind of user journey flow past that point is definitely where I'd appreciate input and if anybody has any queries or suggestions would love all that because that's, this is basically where my, where my attention and capacity stops, because I'm essentially working through the website structure and providing the content and all that kind of stuff. The partnership with this group. Yeah, maybe this group is like how do we handle the handoff from the website into the other parts of the community and continue that flow in a reasonable way right. Yes, and I think one of the big questions for me is what's what's not what's maybe still not that clear is, and if I click on on your homepage, which again is just a markup to get an idea of things. Yeah, from the board is obviously we want to be one members front and center. This will be the scrolling member logos. Some photos of the members at events. Then we then we're featuring the projects, the graduated projects. Case studies. And then here is something. I definitely look at working on in terms of adding the end users, but also what's the, I think my big question is what's the, what's the big incentive for a new contributor. They're rather than just like hey, become a contributor to you know look at this look at that. You know what is it. Is it hey, here's, here's your first set of bugs to get into to get your teeth into right or hey here's a something to participate in immediately, so that they can be on boarded in the most efficient manner without having to get too lost in documentation stuff like that right. So that's where the start here stuff comes in and maybe I don't know Niki or others can like talk about what their goal was start here is and that's always been my concern to start here I think it's been great but I just don't know how people find it right like because it's not necessarily integrated or linked to from other places so maybe that's what you're talking about, like, what is the next step or how do people get into something specific right. And I'm aware that again, obviously the large majority of the community are maintainers and contributors. So, they're, and from what I've heard. They're not necessarily coming back to the site that often to look for stuff or do stuff in particular, but maybe they, but maybe they should. I'm not quite sure how that what the best way to do that is, and that is a good point I don't know if that's captured on your personas sorry you were sharing it earlier but maybe I just missed it but yeah that maybe that's a good thing like what Web property doesn't given persona go to because I suspect you're right a maintainer doesn't go to the website so much they go to GitHub right. You know they probably go to the wiki and GitHub far more than they go to the website and so different personas go to different properties right. And I don't see if that's captured or not but maybe it's worth doing. Definitely. I would love for this to be developed a bit more. I mean we've got kind of in a marketing communication stuff here which is great and helpful to make sure that our messaging is on point, but in terms of actual communication preferences. I actually did a quite a large map of all of our comms channels, which, which are, which is, again, quite, quite large. And I've seen other designers in UX specialists kind of draw you know pathways and arrows all over that you know to make sure that and and do for user journeys from throughout all the website properties. If, if I'm not saying we necessarily need to do that but certainly it would be if somebody's up for doing that. It would be really really useful because because we also have analytics tracking behind not only the website, but wiki as well. Obviously not to do anything nefarious but just to understand the traffic flow better. So that is that is one piece that we could certainly work on a bit more as well. And I don't think we know the traffic flow beyond the website that much I mean I've been I know I pinged you on Slack last week but we got a question from one of the sig chairs about influence traffic and we didn't really have a good answer for him. And so maybe what you're talking about just so you know this group is working had submitted a mentorship proposal for somebody who can come in and help with this project so maybe that's something you and the mentee can work on together maybe doing the integration on the, you know, the analytics back and to get the workflow across multiple websites. Great. So yeah john that would could be a good task for us on our mentee task list like figure out the Google analytics stuff with, you know, been. No, that's great. I think that would be something that I'd be more than glad to work with the mentee on to make sure it's all wired up correctly. And we can track, you know, flow through the entire both the wiki and the primary website. And then if they're going to link off to another repository and, you know, make sure that that's all tracking through. And probably just to end off as this is this is quite great. There's a milestone is the top level results from last year, just to give you an overview of the total community traffic. A lot of the social traffic is is going social media is driving a lot of traffic to the website. Obviously it's, it's up 70% 6% on last year. The YouTube channel again driving a large amount of traffic, the fastest growing channel, and in general, the website has over million users. So we really want to capture those and make sure that they're not dropping off immediately. One question I'd have on that Ben is do you have a breakdown of organic traffic and direct navigation traffic that are coming into the website. Yes. So yeah, you can see direct. The changing direct is up 160. Yeah, people are. Awareness is certainly up. And a lot of the work we've done with the PR analytics is that yeah, our general awareness for enterprise great blockchain tech is where we're pulled position. Organic traffic is down again that's probably because of the website performance again. But actually, our YouTube channel is driving most of the organic awareness and reach. So, and social is down is down a bit as well so these are these are the econometrics I really want to see the new website massively increase. Yeah, I'll just make a couple of comments on organic traffic. One of them is because you have so much content that's already indexed by Google. I would make sure that if your redesign gets rid of certain URLs that they have all have 301 redirects to relevant content when you launch the new website. Yes, that is a that is a task that we're aware of, as well as we've already got a massive spreadsheet although all the four or fours and the redirects necessary so yeah thanks. Okay, and the other thing I'll just bring up and I know Tracy has some wonderful questions is, are you familiar with Google's lighthouse. Do you know that project that they have and within that they have what's called page speed insights. Yes, that may be something to look at to because I was looking at that and look like the main thing was a lot of unused JavaScript is what that was flagging for the web. Yes. I have done an initial page speed insights report on that. I'm happy to show as well. And again, yeah, this is something we can definitely that will definitely improve with the new site. I mean I think the problem with the WordPress site is it's been added to for so many years and there's so many plugins and random. Sure. Yeah, a lot of plugins can slow it down for sure. Yeah, absolutely. And the new site is built on HubSpot tech so so that should be pretty, that should really help to improve performance too. Great. Okay, let's let's jump over and let's have Tracy talk about her two wonderful questions you posted in the chat. I think Tracy maybe if you just want to go through those with the group. We can address those with Ben here. When we were going through the menus and I noticed under use, we have training and certifications, which I think previously was under learn, and I personally would look for that under learn as a as an individual so if we expect people to also look forward under use maybe we can have it both places. Okay. And then my second comment I guess was on the Google analytics I'm wondering if, if we have a common key analytics key that exists for hyper ledger. The documentation template actually has a place for that and love to be able to specify our common hyper ledger one versus a specific one for different documentation that people might create. Yeah. Which I actually have been using look a studio. I'm not sure if you're familiar with but I'm pretty various dashboards. If that's, is that the same thing. Or do you just want to basic analytics. Well I guess that's that's really the question is how do we make sure that any sort of documentation that people create is analytics that you can get to for understanding kind of where the traffic flows to. Okay, sure. So for example, I've got like a block and case study dashboard that only shows you block and case study analytics. And we can create these dashboards for any pages or documents on the site. And do we use a common analytics key I mean what's the what's the mechanism. So, so what I'm thinking is that if we create documentation for say cacti or bevel or fabric or whatever right that we if we provide a common hyper ledger key then all of those analytics can be viewed by the folks in the hyper ledger staff to understand like, okay, people come to the fabric documentation from the website or they come to it from GitHub or they come to it from wherever right. But I say at the moment, I think only internal hyper ledger emails have will have access to the analytics but let me look into that because this may look at dashboards might be the solution for external view. I think that one thing like you're referring to the UA codes, the old ones, and I'm sure then you're moving over to GA for I don't know if you've already moved over to GA for at this point or you're still using away codes. But the main thing is yeah, you could do like you know dash one dash two dash three for any of the GA for codes to do exactly Tracy's looking for here. Okay. That's a great point, Tracy because you know, visibility and analytics tells us story, you know shows user engagement cells, you know how many people are visiting the pages and you know what's the length of engagement. So that's all great. So just just on clear who would be. Who would they who the codes before exactly. It sounds like you just want to drop it into the head of each project that Tracy has mentioned there. So just make sure that whatever individual hyper ledger project has, you know, the GA code on those pages so that they can get visibility into it. And especially for people who are, you know, the maintainers would need to know, you know, are they getting greater traffic over time. What are the most important pages of people are visiting and just, you know, given as much statistical data as they need to see what, you know, what people are doing on that particular project. Cool. I've noted that and we'll run that by Daniela. Perfect. All right, Ben, well that's wonderful. And if you want, I can just kind of pull up the page speed insights. If we want to look at that for a second or I don't know if you ran that recently. But we can just kind of look at something that we can look to improve as well as we help you out on this project. Yeah, I appreciate that. I'll just go ahead and just pull it up really quick here and then we can just take a quick spin through it. I'll launch it on mobile first and then we can look at desktop. Okay. Okay, does that come through for everyone. So I would say the main thing that I was looking at here as far as, you know, just things that are going to be in the red is really that page load speed. And I think if you address the page load speed with the new design, that's really going to help out your performance as far as Google's concerned. And I think it'll also help with the bounce rate because then people won't be wondering if the page is going to load and they'll go right into the content. But if you look down here, you know, these 4.2 seconds, 5.7 seconds, you know, that's, you know, pretty beefy page load times and whatever we can do to reduce that would be great. And then it's really about that unused JavaScript that's coming in from the WordPress plugins. And even if there's any plugins, I think that are active that maybe be able to be deactivated. That would definitely help as well. Yeah, there's those pesky plugins unfortunately most of the site or all of the kind of key elements like the block and the tables and stuff they won't plug in so currently that the only way to. Yeah. Yeah, no, I agree. And that's just maybe something to review with your web developer. Just to see if there's anything that they can do to maybe, you know, like this defer off screen images is always good. Just so you know, we're going to paint the page and then pull in these other images after the page is rendered for the user. And then some of that next gen image format. You know, like image formats that Google recommends and they have their next gen format that they push. So that's about it. Yeah, this is this is I've got a meeting actually set up consensus next week but the week after I'm meeting with the web team to go through all this time and thanks. Yeah, no problem. And I think you're doing a wonderful job and I think the new mega menu looks perfect and the new redesign is going to work great. And it's just, you know, we're here to jump in and help you and also work on, you know, getting people right to the content quickly to make sure that, you know, they're engaged and moving forward versus bouncing off the website. Awesome. Thank you. People helping out with the persona development. Would that be possible. I think that's that's one, one of the key pieces that I definitely appreciate the most help on. Yeah, I would say 100% that the onboarding mentorship can help with the persona development and give you, you know, several more personas that we want to look at that you've identified in that first slide that you showed. And then you just let us know, you know, which personas were developing for you and we'll make them look just like your other persona development, which you always did a great job on. So that's wonderful. Yeah, been for sure if there's anything this group and then the mentee when they start can help with I mean we're a resource for you so yeah there's specific other tasks to us now. Okay, great appreciate it. Okay, and then I think Tracy do you have anything else you want to add on what you put in for your environment key for Google Analytics here. Nope. Okay, perfect. Okay, well thanks Ben for joining us and you know it's always better to get ahead of this than it is for us to come in later and, you know, the ship's already left the station. The train already left the station. Yeah. Okay, good. All right, let's go ahead. Yeah, is this task force something that's ongoing on a on a regular basis or what's the. Yeah, it is weekly been I just added you to today because I didn't know if you wanted the weekly you're going to add you to the it's the same call in. You can just add this to your calendar. I can invite you to the series versus just today. That'd be great. Thanks. Yeah, glad you want to come. Okay, perfect. So let's just take a look here. See if I move that other tab I had open here. Okay, here's kind of the onboarding task force tab. And I guess it looks like we also have a new person join us. And a sui and Elena look like they're both new to the call. So, and a sui you want to go first as far as talking a little bit about your background and your interest in this group. Hi, John. I'm happy to be part of this group. And this is an issue. I'm a serious innocent. So I have given my moving idea. It is the first message on today's chat. So, basically, I'm the founder of a company that's a startup name. We have been involved innovations, so we are like, start up like just getting into the research space. So we are working in blockchain. So we'll be happy to be part of and collaborate with you. Okay, that's wonderful. Thanks for joining us. And I guess the task force kind of has two focuses right now. One is around the onboarding side of the hyper ledger community. And the other ones around the documentation side of the community is there one of those two project areas you find of interest the most or what would you like to do to really, you know, get involved and we're glad to bring in on either side of that, or both. I'm happy to be part of both because like I do some hands on experience with hyper ledger also like and it is always like I'm basically a hardcore academician like and entrepreneurship is kind of long term goal. Like, it's a dream to help out people and that's the reason I started the company. And of course it is like, I'm a PhD in computer science also published a lot of papers, so I'll be always happy to help others learn something. So both in documentation as well as the non voting I will be happy to. That's wonderful to hear and welcome to the group and what I'll do is after we're done introducing everyone we're going to go over and just take a look at some of the updates on the task force. So I'll add your name to that if you're interested and welcome to the group. Thank you, and I will wait. Okay, and Elena. Do you want to give a quick introduction. I've actually joined the last week's call already. Okay, just a couple of words on my background. I'm leading the documentation practice at the company that is called exec pro we are in software testing and we create software for testing purposes so we work in the financial sector. And we create some automated solutions for functional non functional testing. And my team has been working with documenting the platforms that we create. And maybe already from this description it is understandable that out of the two workforces that documentation was one is most interesting to me. My team is still in its inception stage so we're trying to understand the community, like practices, like best practices approach, and I'm really excited about what Tracy does with the third template presented and explained last week. And they will mention about it. So, at this point, I would like to be closely monitoring what you guys are doing. And if I identify any area where I can contribute, I also will be glad to thank you. Fantastic. Glad to have you join us again. And so I'm just John your audio is going in and out a little bit. Okay, is my audio good now or not seems right now. Okay, yeah, I think it was just I was doing this transition, everyone can see my screen. Yep. Okay, perfect. So, let's just go ahead and if you want to be added to this project so let's start. And do you have an email that you'd like to give us that we can add as part of being on the onboarding side of this? Yeah, just now I have a message that see I have a registered email ID with Hyperledger community is bini bfb at biniwall.com I just messaged In the chat. Yeah. Perfect. Is it bini bft at bini world. Yes. And any comment as far as your role that you want to put out there into being a part of this, what you're most interested in or some background component. Like, if you want me to develop some learning material or like some content like whatever is required for onboarding that I can front end content development is that what you're thinking. Yeah. Okay, we can always change that you know you can go in there with your Linux foundation ID and change it. And then let's also put on. Elena. Elena, you're not interested so much in the onboarding side as much as you want to just be on the documentation side is that correct. Yeah, yeah, that's correct. Okay, I'll pull that one up in a bit. Devesh. Do you want to add your name here on the onboarding side. Yeah, definitely. I would love to be a part of the onboarding numbers. Okay, great. I'm just going to put you down here and maybe can you give me your email or post in the chat. Yeah, I'll post it. Okay, perfect. I got that. Okay. And then what would you like to have as kind of a synopsis of what you want to be involved with in the onboarding side. Can I know the options that I can be involved like what are what are things are there in which I can contribute. I think that there's a lot of things like analytics that we talked about with Ben. There's definitely persona development. And I would say that there's also any type of UI UX feedback that we can give to Ben as well. The other thing that I think could be good would be flow. So basically, you know, look at the mapping of website and, you know, give recommendations around user flow. Okay, I'm comfortable with that. But also can I go for a front end developer which Mr. Nico is going for the UX development as I have the development skills. Perfect. Well, that's super valuable. Yeah. Okay, so UI UX. You have any interest in doing anything around the personas or the analytics side. Can you please elaborate on what persona is. It's developing a persona of, you know, somebody who uses the website who's a member of the hyper ledger community so they can be like person who's a developer person who's a contributor person who's a business. Driven person, you know, it's kind of who comes as a website and kind of just framework, give them a little bit about what their persona might look like. And it's just a generic persona says, you know, this type of person uses the hyper ledger website. That makes sense. Yeah, sure. I look into it. You can add me in that also. Okay, persona development and you okay with also looking at analytics Google analytics GA. I don't have any experience of that but I definitely would love to be part of that. I'll just put you down without that on there then if that's not of interest and you haven't used GA then help to say let's do that for now. Let's do one more quick thing here. So you're already on here. You want to add anything or change anything on your comment profile. Everything is fine. Okay. All right. Let's take a quick look over at the other item then I'm going to get out of here. I'm going to save this out. Go into the documentation side. And then let's just put who's going to be on that a little bit here real quick. So I'm going to start off here with Elena. Elena what's your email. Perfect. Thank you very much. Which one would you prefer would you would you want both in there or you want your Gmail or exactly both our K. Okay. Go ahead and both. And as far as documentation what would be the way that you would look to contribute here would you want to develop standards around and you know if you saw Tracy's wonderful run through on that framework that she developed. You know I think that's definitely going to be kind of the gold standard for adoption would you want to do anything as far as reviewing that or adding to that. Yes, I believe that reviewing and sharing my feedback is something that is realistic at this point. But going further. If I feel I'm more involvement. I believe it can be expanded. Okay. And let's see if we have anybody else here. That's pretty much it. Okay. I'm going to go. Yeah, Tracy can be Tracy can be on any list she wants at any level so Tracy do you want to be on the list I'm I'm I'm always figuring you're on every list where you want to participate. And I don't know if Tracy's still with us here she might have had to drop off. Nope she dropped off but I think it's fine Tracy can add herself to the list anytime she wants and she's welcome to be a part of everything. Hey John, you can add me also. I have given my current name and email ID again. Okay, let me just go ahead and see who was that that was letting me know that this is honestly. Okay, and you would like to be on here as well. Yeah. Perfect. Thanks for telling me that I mean just go ahead and add you quickly to this again and then you'll be all set to go. Full name and my lady. Okay, I'm going to just go back up here and pull your email. Same. Any world email is the one you want. Yeah, that's the one. And I have a message in the group again. And what would you like to have kind of your description of what you want to be involved with here. Okay, what are the options. I would say that reviewing the framework that Tracy developed and making sure that you have any feedback or comments around that core framework. Or if it's working with any of the individual projects to see if they need any needs for help with developing documentation. Or if it's working with the individual projects that are approved and running, or alternatively updating any of the existing content that is out of date on the documentation. Yeah, both are fine. I would be like, I can spend some time. Okay, so updating content. Yeah, you can update documentation. Yeah, I think we have given comments and connecting with the groups that also review. Reviewing documentation framework. Sure. Okay, great. We can take a look at anything else that we want to review here. And I just been feeling a lot of questions from people that are interested in applying to the mentorship. This is the last time we had our call. And that's really been what's, you know, driving forward what we've got going on with the onboarding process. And then also, I had a request from Bobby, who wasn't able to join us today due to a conflict where we might potentially be moving this call to Wednesday. I'll make sure that, you know, we keep up with everyone and please track the hyper ledger calendar. If you want to stay engaged with this group because it might be shifting to Wednesday in the upcoming week. So, David, do you have any thoughts around that time frame there I think that the time we kind of landed on was a half hour window. Yeah, I mean, I would just say, I would just say let's make sure it's not disruptive we have a, you know, we're building up a nice audience here on this time, you know, let's just, if it works for everybody that's great let's just, you know, confirm before we do it. Okay, yeah. And I guess that's that's what I'll say what the group is maybe I'll just ask the group here. Is this time work well for everyone. And is it something that we want to be more interested in sticking to this time frame versus shifting to Wednesday around a similar time frame. Both are good for me. Both are good for you. Okay. Nico, what's good for you. Monday is good for me. Monday is good. Okay, is a better day. Okay. Actually, for me also Monday is good because of my university. Okay, perfect. Yeah, good. Good to know because I think if we've got a good group here, like David said, we might want to just maintain our trajectory. Elena, what are your thoughts around Monday versus Wednesday. Doesn't matter. So, perfect. Okay. Okay, great. Whatever we do, we'll make sure that the group is well versed in what's happening and go from there. And I guess David, is there anything else that you think we should cover here we okay with wrapping up today based on the great presentation by Ben. For today. No, there's nothing yet. The been talking to Ben was the main thing that I thought was on our list but so nothing else for me. Okay, well I think that's pretty much it for me as well and I figure it'll give you back six minutes of your time today. Thank you. And I hope everyone has a wonderful week and reach out to me if you need anything. And we're glad to keep this rolling forward and we'll catch up next week. Yeah, thanks for running the call John and thanks everyone for joining. Yeah, thank you. Good day. Thank you. Bye.