 All right, welcome everybody to the May 25th hyperledger technical oversight committee call. As you are probably all aware, two things that we must abide by on this call. The first is the anti trust policy, which basically says don't do any activities that would be prohibited under any trust and competition laws. And then the second is our code of conduct, which is linked in the agenda. For announcements today we have the standard hyperledger dev weekly developer newsletter that goes out each Friday. If you have something that you would like to include in that newsletter, please do leave a comment on the link for the newsletter. I did start the newsletter already I added the best practices and the GitHub guide that we had put together that they've had so nicely put together with our help. So, that has been started so feel free to add anything else to that newsletter that you would like to go out to the developers. The second announcement right, I think you added this one. Yeah. So, this is just an alert that in the coming weeks. This call will be moving to PCC. So this particular zoom link will go away, and there will be a new zoom link. And this is just a heads up that the zoom link is going to change and that's it. It's going to change. Okay, right. With moves to PCC I do have a question. Obviously, the folks that you send it to obviously the TOC members will get that link. Others who would like to join can still join is that correct. Right. For a public meeting there will be a link actually we will all use the same link to join. Okay. There's just an additional click through. So it is a it is a public link. So it'll be the same thing. Okay, great. Thanks, right. The reminders here, I guess are now old reminders because those have been merged in. So thank you all for reviewing those and getting that merged in. For the quarterly reports, we did get everybody to approve both the bevel and the soul line report I could merge those this morning. So there were no questions or anything like that we did have everybody approve them so unless there's any questions there. I'll give a pause and see if there are. Okay, we can move on to the past to report so with the hyperledger saw to the report it was do basically almost a month ago now. We did have a room sent out a reminder after our last call and then right you spoke to the sauteed community yesterday. Yeah, I was on the sauteed community call, and I mentioned it, and James was very sorry that you know he hadn't gotten around to it. So he said he was going to do it soon. Okay. So I know we've talked about, you know, what do we do with these past two reports. How do we want to handle those. Do we want to move the status of projects or anything like that. I'm curious as to what people are thinking at this point with the sauteed report. So I don't think we should do anything. I mean, in this case, there is clearly a community behind it still. It's not like, you know, a zombie project. It's bad behavior from their part but you know, oh well. Thanks for anybody else. Yeah, Peter. I think it goes a long way that they actually responded on the community call and said that they rectify it. It's very different from as if there was no community call and they not respond. Alright, thanks Peter. Okay, so then we will keep this on the agenda for next week. Hopefully we will see that come in. It's a holiday in the US on Monday, so we'll see what might happen. The transact report is coming up again on the calendar. It is a project that we moved to dormant probably what a few weeks ago. But we will actually see any sort of report come in. But I made sure to keep this on here because I would like to continue to check in with transact and see where they're at and what they're doing to ensure that they want to remain dormant or if they're ready to move to end of life. We will continue that for for the next quarter I'll probably reach out to them just to make sure that they're still in the right state but I feel like given that we just did this they probably are in the state that they want to be in at this point so that's the transact report that is upcoming. I think the next report is in June and that's cello so we'll get that one on the agenda for next week as far as just being a reminder to the cello group. So the question today we have David who's going to walk us through kind of an OKR review of what the community architects have been up to, and then we have the task force discussion that Bobby is going to take us through. So with that, I think unless there's any other comments at this point we'll hand it off to David. Thanks Tracy. Let me show my screen. Are you all able to see my screen. So I think there's two things that I'd like to do today one is just keep you in the loop on what's going on because a lot of the things that we're doing around community development goals and staff are obviously relevant for people in the community. But I think maybe even more importantly than that you know that now that we're about halfway through the year I'd love to get feedback if you think that we should rethink anything on here or add new things or kind of change anything we're doing now is the perfect time to do that right we'd like to see if there's any thing we need to do in the second half of the year that's not already on our radar so to speak so if you have any feedback comments suggestions ideas at any point feel free to stop me and we're happy to talk about things. And just for context the staff has a number of different goals for the year I'm only going to talk about the community growth goals if there is interest in learning more about the details of any of these other objectives in terms of what the staff is working on, you know let us know and we can always report back on that at another time but just for context today specifically what our community development community growth goals are. I think the bucket the bucketed them into a few different topics, and we can go through these and again if you have comments or questions about any of this please stop me. The first, I think all the goals are important but I think for me it really starts with this first set of goals which is supporting maintainers. You know, obviously, if we wouldn't have a community if we didn't have maintainers and we, you know we need those retainers who show up to be successful so really supporting maintainers is where I think all of this starts. There's a number of different things that we're doing here. And to get into the details what I've done is kind of for each of the set of goals had two slides so this is just a high level overview to show some of the things, some of the examples but then, you know this is where I think maybe the, you know the details will be interesting for the group you know we bucket the, you know we've taken each of these buckets and shown what's been done so far what's in progress and what's coming so I do. I think the moment's kind of going into the details on this because I think again this is. Of all the goals we're doing this year this was very important and obviously relevant for everybody here on the call so just to share a little bit about what's been done so far. We have updated our project services document if you haven't seen that recently please do take a look we had a blog post about this earlier in the year where we talked about exactly what went on in here if you want to see the details but just to be, make sure everybody's aware of this if you're ever wondering what services are available to you as somebody who's involved in the project that the project services doc is a good place to go it talks about what are the tools. You know how to staff help so just just be aware that that's there if you want to take a, excuse me, if you want to take a look. You can click through I'll share these the link to this after the call and the to see channel so you can go through and click on it. You can also just go to the wiki and search for project services but just be aware that that's there. In terms of things that have been done so far that I think are worth highlighting, you know, that I think shows one of our focuses here is, we really want to again understand what maintainers are trying to do and then help them be successful at that so I think one example of that is facilitating the development of the hl operator lab into pebble. As people here probably remember the hl operator lab came to the to see a few months ago and said they wanted to start a project. And we really helped understand what they're trying to achieve and understood what other projects in the community are trying to achieve and saw that there was some overlap. And that it was probably best to bring these two things together versus starting up a whole separate project and I'm glad to say that has happened. But this recently to about the integration of hl operator lab into bevel and there's actually going to be in about a month in late June, a workshop where the bevel maintainers and the person involved with that lab originally are going to do an in depth workshop about the work they've done. Another example of kind of understanding what's going on in the community what people's needs are is we helped restart the development of the eol explorer and burrow code and restarted those as labs, because the code was still of interest for people in the community and so we understood who the stakeholders understood what they were trying to achieve and then figured out the right way to support them and then that was taking that code and helping them restart it in labs so just be aware that those are some of the things that have been done. In terms of what's in progress, I think we've all known that there's been some bottleneck issues with github. No, I think that's, I kept that still in progress because I think there's still some things to do there but I think much of the kind of biggest parts of the bottleneck have been addressed now but you know we're still this is an ongoing conversation we have with github. In terms of having that conversation, we did, we did get some invites to a github maintainer summit that they just recently had. And that was a great way to have some dialogue so they can understand more about what we're trying to achieve what how we're using their tools what we need to know what they need to know about what we're, what we're doing so I think there'll be some good things that came out of that. And again if anybody went to that maintainer summit and wants to debrief and share their experiences with that I think that could be an interesting discussion. We're also doing some ongoing recruiting for new maintainers for basing fabric, and we're happy to do that for any project that's interested in looking for additional maintainers. And this goes out this is involved, what's involved here is going out looking at the group of stakeholders in the community understanding who is interested in which project going out having those conversations trying to get people to, you know, not just be users of a project but contributors and maintainers to. And I'm not going to go into this level of detail on all of these things we can just read through the slides here but I didn't want to highlight some of the things that's going on. And then in terms of what's coming and rya alluded to this to with his mention of PCC we are also working with the internal LFX team to help them better understand our development process what we need out of the tools that they're working on and to get that into the roadmap so that's an ongoing process and you know hopefully we'll see some things that they roll out later in the year that we can make more use of as well so unless there's questions comments on this I will move on to the next set of goals. David it looks like Victor has a stand up. Oh great I can't really see that so thank you guys. Yes. David is just a way to return to yesterday's question. So just. I'm not sure it's the best time but let's return to this in the time for questions. If it's here. If you have a question sure. Well the question is yesterday is about the mentorship program. Sadly we were quite confused with the LFX interface and many of us did not have access to the list of mentees until recently. This is fixed but at the same time you set a deadline for us checking which mentees should apply and the deadline is this month 30th. I believe if in any way possible this limit should be extended to the next to the first week of the next month because we don't have much time to actually check everyone and we want to be very honest about this. Yeah so that's a good question I do think it's relevant right here because it does talk about how we're talking to the internal development team at the Linux Foundation to help them improve their tools that work better for our community. So I think there's two issues one is yeah thank you for providing that feedback if you want to write up your experience and maybe you've already done this and send it to men but if you want to write up your experience but the details about what specifically in the interface was not intuitive or could be improved we're happy to help get that feedback back to the development team. I am continually a male in everyone but there is a place where I could actually detail all the parts of the LFX interface which were confusing and hindered our progress. This would be very nice so please show me any and I would like to record our experience. I think in that case giving it to men. If you if people on the call haven't met men before men is the person on staff who's running our mentorship program. And she interfaces with the team running the mentorship tool so I think giving her the feedback is probably the best in this case the best, the best thing to do and again maybe you've already done that. Well, I have tried and I've sent some tickets but it seems she has limited links to the team so if there are any one who can actually add more contacts and make it recorded or maybe we can record it on Hippology wiki this would be very nice. Sure. Because I feel like our experience could repeat for other teams and this would not be good. And I know and I've seen other people ask questions I don't know if they're running into the same issues that you've run into but I've seen other people have issues and say that sort of thing like I can't see the list of mentees for example. And we can talk about this more offline but yeah getting your feedback on what would be prove would be great and then the second point about extending the deadline I can't speak on behalf of men and men is actually out of the office this week so I don't. I don't know for sure if that's going to be something that works with her but I'm happy to talk to her about that when she gets back. I wish she actually put some people who were responsible for this because at the same time she is out of office and nobody she added to the list actually response. So this is confusing for me. If I can I just added a link in discord to community dot LFX dot dev. Where the developers are supposed to be more engaged. So there is if you. There is a link which I will provide in discord to the mentorship questions. And that is probably a better more public place to ask, and I feel your pain on filing tickets and not getting responses because it's no better for me as an employee than it is for you as a community member. Thank you. But again, if you share that information you're writing another wiki is great and giving that information to us the community architect team we're happy to help advocate on your behalf. And again I can't speak on behalf of men but I imagine that we'll be able to do something on the deadline I just, I don't want to give you a definite yes because I'm not the one running the program but actually the key idea here as I see at least is that they have a very confusing set of rights. There is a mentor and mentor has access, but there are two requirements for the mentor to actually have access somebody has to file the mentor, and the mentor has to be filed twice. Because you need to fill the description, unless you do, you don't see everything, and the system doesn't guide you to the right direction to actually do that. It doesn't show the requirements, and this is where I'm convenient. Yeah, that doesn't sound intuitive at all and I again I've seen other people say they've had a hard time accessing the mentees and so maybe they're running into that same issue so thank you for reporting that I apologize for that issue but yeah we're happy to help support. And then Min's back next week and I will talk to her when she's back. Any other comments questions on this or if not I'll move on. Okay, I will move on. Another set of tasks or another set of goals we do I really in my mind this is still related to the first one about supporting maintainers this is really creating a pipeline to bring new you know my, and my observation is it's very rare to have a new maintainer to show up fully formed you know somebody needs to show up and learn about a project learn about you know all the details about it nobody's going to have all that knowledge. As soon as they show up right so I think they're, there are a set of goals where we help empower people with the information they need to be successful at both using a project or a lab but also contributing and becoming a project or a lab so I think this is critical to bring in new maintainers so there's a set of things we're doing here both creating certifications creating workshops doing doing a number of things so just to go into some of the details on here. One is speaking of the mentorship project program I am glad to see that this year we explicitly added documentation as something that people can do in the mentorship program and I think this has had a really nice pickup. You can see here 14 of the approved mentorship projects this year have a documentation component. And I think that's important, I think it's pretty much a truism and open source that you know documentation is something that you know we probably could always do more of so this is a nice way to encourage more of that to happen. Another thing that's in product that's done is we did recruit a number of fabric experts in the community to develop a new fabric certification exam people probably aware that we had fabric certifications in the past but those are based on earlier versions of fabric so we're creating a new one based on the latest version of fabric. So the recruitment of that is done and they're doing that work right now, and the new certification should be available soon I don't have an exact date yet from our training team but that that is in the recruitment is done and now they're doing the work. We've also organized a number of workshops across a number of projects, and I think I skipped that on here but just one thing to flag. One thing to flag that I think is really relevant for everybody here. If you're ever thinking about hey how do I get information about my project out to a bigger audience I just want to flag that the online technical workshops that we do are the most popular online events that we run at hyper ledger. A lot of things we do webinars we do meetups we do a number of things but all of all those things that we do. People seem to be very very interested in the technical workshops which makes sense, we're developer community people are really going to respond when we give interesting developer content. So just for an example, the recent CBDC workshop that we did had over 800 people sign up so again if you're ever interested in reaching an audience to help bring more users in more contributors in an online workshop is a, you know, a way to do that and we've done that again for a number of projects so far this year happy to organize more later in the year that's going to be, you know, in our what's coming. So I think this will be something we'll do in an ongoing basis but we need the experts in a project who can share that expertise, you know to work with us in order to organize a workshop so that's of interest feel free to reach out. Again I'm not going to go into all these details I know we have limited amount of time but just to flag that there's a number of things that's going on. Another thing to flag around working with our training team. We're looking at not just doing work on the certification side but also updating and improving the hybrid your courses that we have you know this is an ongoing effort, because things change right you do of course a year or a year and a half ago that content has changed to the project has changed so that's an ongoing thing that we're doing. If there's any comments or questions please let me know if you see something like that we don't don't have on our list that we should again let me know but if there's no comments I will move on. Okay, and I'm not keeping an eye on the chat or the list of anybody raises their hand or put something in chat please let me know. One of the things I would really want some feedback on and this is a new set of goals for us this year I think what we've done around supporting maintainers and doing learning content is something that probably is not a surprise to you we've been doing that every year. You know some of the details may change but having that as a top level, you know set of goals you know is certainly something we've done in the past but I think this year. And explaining why to contribute is something that is new new for us and we're really trying to explore the best way to do this and I would really be interested in feedback here. Because my observation I've been here over five years now my observation is, we often assume that people kind of understand why to contribute, but I don't think that matches reality we have had a lot of examples of people using Macs or labs and hyper ledger and not contributing back and so we see situations like when we end of life to explore a lot of people showed up and said hey I was using that. But they never contributed back so I don't think they had understood why right and that's a great. Why right there if you're relying on a piece of open source code. Make sure that that code evolves and stays healthy and is there for you you really need to contribute because if nobody contributes there's obviously nobody to make sure that project keeps going on so I don't think we've done enough to explain to our users to our members, you know, to our community members to our member organizations why to contribute so this has been a new focus for us this year. A new set of goals here and again, since this is new I don't know if we've really figured out what's going to work yet because we haven't done this much as much in the past as I think we should so I would be really interested in feedback and thoughts and suggestions here. One thing that we have done. And again this is more of a, you know experiment to see if this is going to be an effective medium but we've started a new podcast series specifically focused on talking to people about why they contribute. And we've done two so far one with Tracy one with Sophia, and thank you for for the people who worked with us on that. I think it's still too early to see what kind of you know results will see on that but we're going to the plan is to continue to do more of those this year. And we're also developing presentations that more clearly explain the value organizations and individuals get from contributing. Again, I think we've always kind of assumed that this has been, you know, known, you know, maybe not in all cases I think obviously we have talked about why to contribute but I think maybe not enough so I think just being more clear getting some of this down on paper and in a way that's easy to present I think is important so we're doing that. I don't know if we'll have time for that today but I would be happy to come back and present. You know some of our articulation of why to contribute again to get your feedback but that's something that I think it's useful for us to get down as clear as possible in a way that's easy to present. And reaching out to people. Yeah. Yeah David this is on I just wanted to interject here to ask I mean, is that aimed at like individuals like developers or more their companies. Well I think we can aim at both because I think you know, both of those audiences are important. There are some individuals that may maybe with an organization or may not be with an organization that we could you know reach to and then I think there are individuals at an organization that may, maybe bought into that but their you know their management may not be so I think there's a lot of different levels here where we need to pitch this it's not just one presentation even necessarily or one reasons. And this is what I was getting at that is that you know my experience, the feedback I get when you ask people developers offer any situation where their employers don't doesn't support them contributing back. They may even maintain some fork and make patches, you say why don't you contribute that and they say well, really, you know, my company doesn't really want me to. And it's terrible to hear but that's, I think more real more often the case then the individual himself or herself deciding that just don't care. 100% and thank you for that and yeah I didn't get into all the details on this slide but yeah I mean I think the right way to approach this is thinking about the different personas in the community. And then figuring out, you know, there's going to be a different argument that resonates with different people right I mean an argument to, or, or, you know, or information for a developer is probably going to need to be different from an information for you know, you know, a non developer, maybe in management so absolutely. Other comments questions suggestions. Peter has a stand up. Peter. I think podcasts are great idea because those seem to be the easy slows barrier way to have long form content nowadays that people are going to listen to all the other in something else. That's a good idea to get into an audience that may not have been that interested in reading the entire amount of content as a blog post. So it's, it's great. And I wanted to ask, where are the podcasts hosted on one of these platforms or do we just put it on the hyperledger.org domain somewhere. They're definitely on our YouTube channel. Ben is probably sharing them in other formats, but if you go to our YouTube channel they're there. And if you're interested in that Peter, I think Ben may have reached out to you recently about you know if you want to be in it. And this goes for everybody on the call if you're interested in being a part of our podcast series. We'd love to have you. And so if that's something that's of interest certainly reach out as well. And you're right it's not actually that heavy a lift I mean I, I did not know what was involved with making a podcast and I've done one of these and it's really just a recorded conversation that you do a little prep for an advance so it's not a huge production and it was takes like a minute conversation that you record. So it's not a huge lift so if that's of interest certainly let us know and we're happy to do that with you and again the focus. I think we do a lot of content about what projects are doing so that I think the set of questions wouldn't be what you are doing necessarily but it's more like why, why do you do the things that you do in the open right. So that's of interest certainly let us know. So Peter and anybody else if you'd want to take part in a podcast. Happy to work with you. It's been good timing. Hey Peter, I literally just emailed you about it so thanks. Good timing. Any other comments suggestions again I really would. I mean, I think to going back to our nose point you know I think you, you know what your needs are inside your organization more than we do is is there. Any content or material or anything that we can provide that would be helpful for you in your discussions internally about why to do things in the open like our nose said maybe there's some internal fork and that you've had a conversation with people about why that might not be a good idea is there anything we can do to support you in those internal conversations. I don't have to answer now but if that is something that you say hey I'm going to have this internal conversation it would really be great if I had X just let us know maybe we already have that and we can just give it to you or maybe we can develop it with you. If there's no comments or questions here I'll move on one. I don't think this is going to be new to you all. This is something we've talked about many times before but again I think there are a set of goals around community health. Again we've done this in the past so this unlike the last set of goals I think we this will seem more familiar to you and this is something we've worked really closely with to see on so again I think everything on here you'll probably be aware of but just again to flag it. And we've shared this information with other people so this may be new for for example the governing board but I think you're going to be familiar obviously that we moved, you know some projects to well status recently. We are also internally just keeping an eye on projects and some of that not necessarily all the labs at least active labs just to see how things are going again if we feel like a project needs support we want to be aware of that so we need to keep an eye on things and review things so we know where, where our time could be useful. I think one other thing to flag and this just changed and Tracy I actually haven't had a chance to share it with you either but we have been talking about not just monitoring the health of projects but monitoring the health of all the activities in the community and we're a big community and a lot of stuff is going on. And I think we need to monitor all of it and so one set of things that we've done as we've recognized that the working groups haven't been as successful a way to drive contribution and collaboration as we had originally hoped back when Hyperledger was started and organically most of the working groups on their own have winded down and asked to be archived but there had been a few things that we've seen and so there had been some discussion over the last year or so about what does it look like to kind of wind down all the working groups and either archive that work or evolve them into a format that's going to be a better fit that we've seen would be a better way to drive collaboration so for example I think task force in practice are a lot more effective than working groups so some of the, there were about three remaining working groups at the beginning of the year and some of the things that we've done to move them off of being a working group we have evolved some of those into task force of learning materials development working group for example turned into two of the task forces we're doing now. So we have now archived all the working groups as of last week the last one that was remaining was the performance and scale working group I had been checking in with that group on and off for, for, you know, over a year now to figure out how we can kind of support them. Harris the chair of the group has said that they haven't been meeting recently so we have archived the group but he is interested in doing things. We have a couple of different performance related mentorship projects this year. So I think there are clearly performance and scale related activities happening in the community there's also some labs related to this right I think the, the trick is what do we do with it so just a flag we've archived the performance and scale working group, but they still want to do something the conversations I've had with Harris and until and others they've talked about creating some sort of sort of performance center, which I think makes sense because right now if you were interested in performance there was just stuff that's scattered all over the place it wasn't clear do I go to the performance and scale working group do I go to Caliper do I do. Do I go to this lab right so I think trying to pull all that stuff together in some way is a good next step I don't know exactly what that looks like maybe it's a task force maybe it's revitalizing Caliper just like cacti is kind of the home for interoperability in the community maybe Caliper is the home for performance and scale in the community. So anyway, just a flag. I wanted to spend a little bit of time on the working groups so there are none of the working groups are active anymore they have all been either archived or evolved so just the flag that and there is something I think in the performance and scale space that people in the community are wanting to do and we may need to be able to support them to figure out what the right way of that is maybe that's a future to see call discussion but just the flag and then the last of the three working groups that had been at the beginning of the year. The identity working group that has been evolved into the identity special interest group which I think it's going to get them better support we're able to support a special interest groups and promote what they're doing and and I think that's a better fit, and I think it's effectively has been a special interest group along it's talking about what are people doing to adopt and deploy these technologies in the identity space which is exactly what our special interest groups are it's bringing people together to look at how these technologies are adopted and deployed in a given space like telecom like healthcare so I think it fits better as a special interest group anyway so. Anyway, long story short, we have removed the working group as a community activity, it's not featured on the wiki anymore. The archive the information is there as an archive format but we're not featuring it in terms of on the homepage or in the navigation. The same as on the website so just a flag that all just happened very recently the performance and skill group. And the other things on here again I think you all are familiar with we did the Community Health Task Force last year. But there's still some work to be done there so you know we can we're happy to support the TOC with restarting and wrapping that up. We recently had the governing board reach out to us and say hey that, you know, to see where we encouraging you to conduct project reviews are happy to support you with that. And then lastly, what I was saying earlier about Community Health Assessment is really not just something that we only do for projects I think we want to do that for everything so working groups special interest groups, anything we do in the community. Anything comments questions suggestions on this. Okay, if not, I will move on. So one more bucket and then after this, there was a set of questions I wanted to have for the group but just the flag. One other thing that I think is very important in terms of what we're doing is try to improve the accessibility and diversity in the community, we say, all are welcome but I think to actually mean that we have to do things to make that happen. So what are the things we're doing to make that happen, just a flag on here. This one I think is really important, something I think is really important. You know, we're a global community and if we say all are welcome here, not everybody necessarily speaks English. So I think the more we can do to provide content and languages all around the world, the better. So here we have done some content in different languages. I think we can always do more here if this is something that's of interest to you. Let me know I'm happy to support you there's I think this could look like a lot of different things we can always run a meet up about your project or lab and in a different language we can help you connect with people in the community that want to translate your material we've had a very successful translation effort in the past around fabric documentation if you would like your documentation in a different language. I think we've proven and other open source projects have proven that this is something that people in the community are more than happy to do. I think it's really meaningful for people to have content in their own language so people will step up to make that happen if you support them with that. I would be aware if if that translating content in some format into another language is something that's important to you. We're happy to support you with that. We've also sponsored this year the international women a blockchain event and sponsoring events that you know get us in front of people who aren't, you know, fully represented in our community. That's something we will do on an ongoing basis but just a flag that's happened this year. We've also worked with Morgan State and other HBCUs. They have a very active blockchain program across the network of HBCUs so we're working with them. And it would be great to see them be more actively involved in the community. Another thing I really want to flag that I think is important is we're in the process of conducting an accessibility audit of our site and our tools. For example, I don't, I don't know how well our wiki works on screen readers right for example if you are a community member and maybe you need to work with a screen reader. I don't, I don't know how well we've supported that right because we've never really audited it so I suspect there's probably a lot of things that we will find in this audit that hey we can improve. We've probably looked at closely at it before so I don't know what to expect out of that audit but I think this is an important thing to be doing this year. Again, we want to make sure that everybody in the community is who wants to get involved can get involved and some people may not be well served currently by our sites and tools so you know we're going to do the audit, we can report back what we have found and then if we need to make some improvements, we'll look at how to do that. Any comments, questions about this. On the last part about accessibility. I have a tool that I use that is completely automatic and free it's called Veeve. You can use it either online or you can use it as a browser extension and what it does. It just scans the HTML of any website that you pointed to. The baseline issues if there's any, for example, if the font size is too small, if the colors are not contrasted enough so that it will blur together for someone who has an impairment regarding to seeing different colors. And a double checks for you if there are labels on the HTML elements for screen readers. Oh, that's great. I wasn't familiar with that. Okay, I'm happy to send a link in the chat after the meeting if you want the direct link. Yeah, please, please, that'd be great. So you've run, you have run that that's great to hear so you have you found so you have you run that on any of the hyper ledger infrastructure. I have ran it on the website that I have for DC Island. Because that's fair. That's when I started thinking about this. Because DC Island was about inclusion. And then I had this website for it and then I realized that it was actually badly contrasted and it was missing some of the screen reader labels. So I have. Oh, that's great. Okay, that's cool. Yeah, please. If you have the link, I'll check it out. I mean I imagine the people doing on our audit may be familiar with that but I'll double check and make sure they are and we can use it as well. Okay. Any other comments questions. If not there was one more slide and sorry if I'm taking up a lot of time, but I think this is something again. I want to get some feedback on if you have thoughts but I think again what staff is doing. I don't think we should be working in a bubble and we are happy to work with you and we want to work with you and I think we're going to be successful only if we do work with other people in the community so where we really need help around these goals. I wanted to flag a few of these things so. And some of this may not be relevant for the people on the to see to see obviously you're very engaged in the community so some you already are, you know, doing some of these but again this the point of the set of slides we put together is really to share this across the community. So one of the things is we really want to talk to people. If you're using a hyperledger project but aren't engaged in the community I kind of references earlier around Explorer there are people using Explorer but not engaged with Explorer, and the project moved to you well right so we don't want that to happen if there's, if there's a community around. If there's a community of users around a project we really want to speak to those people and really understand what is it that we could talk to them about to help them. Explain the why of getting involved and to help them get involved, maybe they do want to get involved and they just run into barriers right so if we understand what those barriers are maybe we can help remove them so. And I think the thing I would say here obviously you are engaged in the community everybody on this call but if you have users, if you know there are people using your projects who aren't engaged. So let us know and we're happy to talk to them right if you flag people who like hey I know x y and z are using my project but they want it. I've really wanted them to get involved but they haven't we're happy to go out and talk to them right. So feel free to empower us and let us know who those you know more about your users then you know we do in many cases so you feel free, we're happy to have those conversations if you let us know about that. I kind of touched on the second bullet I already touched on but if you are trying to get involved in the community yourself and you're running into blockers let us know I think we talked about this earlier with the mentorship thing. You, you are users of the infrastructure that hyper ledger has set up and the Linux foundation has set up if some of it doesn't work as well as you would like it to let us know and we can try to improve that right so if you're running into blockers certainly we want to hear about that. If you in your organization have internal resources focused on documentation or training or translation. Please let us know and we'd be happy to talk to them and work, you know with them as well. You know I think documentation training and translation is some, you know, something that we could always do more of I think it's good to do more of, you know, I think we are obviously a developer community but just do development right we have to also go out and talk about what we're doing explain what we're doing train people and what we're doing right. So, if you have people on your organization doing those sorts of things and they may not yet be engaged in community let us know we're happy to talk to them. The same goes for the accessibility experts and thank you Peter for that feedback but if you have people on your on your team and internally who are accessibility experts. You know we're going to I assume get a number of issues back from our audit and we're going to have to tackle those so if there are people who know how to tackle these issues we would love to work with them. It's a special. I've worked with other communities have had accessibility, you know, efforts and you know it's a specialized skill and I know anybody has that skill would be happy to work with them. So I don't know if this resident if any of this stuff resonates with people or you have comments questions on this. But if so happy to have a discussion about this or answer any questions. If you have questions about anything that we covered certainly let me know. If there aren't questions I would just say, and again probably I'm keeping an eye on the time I don't think we have time on it today but if you are curious to see the information we put together about the kind of the why to get involved I would love to present that it goes back to our nose point maybe you can say hey this is good information but it's not pitched at the right audience right we think you really need to pitch this at a different audience right that that's going to be really valuable feedback for us so if you have space and the agenda I'm sure to kind of go into the why to get involved stuff I'm happy to, you know, come back and not worry about that. The fact that we're all quiet means you did a really good job explaining all this so thank you. Oh, great thanks. That looks like Jim has a question. I still agree with with what David just said. Yeah, very nice work. I just want to comment quick comment on the continued focus on helping to find maintainers. The far flight community can definitely the far flight team can definitely use continue to use your help on that on that effort. I'm happy to do that I don't know if you want to have I know we've been talking but if you want to have additional we can get another call or talk on discord but yeah that'd be great. Happy to do that. All right. Thank you for David and we'll definitely ask you back to do the other presentation that you've got out there about why to contribute I think that would be good to get some feedback from this group. Yeah, that sounds great whenever whenever works just let me know. All right, Bobby eight minutes can you do it or would you like to move to next meeting. I can do it in eight minutes. Okay, go for it. Share my screen real quick. I'm having trouble with zoom share screen there we go. Okay so the task force again meets every Monday it's the onboarding in the documentation task force. We did have an application into the mentorship program. And I will show you. So I saw that I had these wonderful seven mentees, and I decided that I would interview all of them that finished all their tasks. And that was my criteria for myself for the interview process. I didn't realize when I made that decision that that was only page one of 10. I had 65 applicants. So, with that said, the documentation task forces kind of been eaten up with the mentorship program for the time being until we can get that piece in place and move forward. I am in the process of interviewing and like the gentleman said before me this is an overwhelming task. I have 24 interviews to do I've done for it. I have them set up everybody green here has an interview coming. And he said I feel it is one of the most important thing in the community to get new people in, and it is a personal pet peeve of mine when you apply for a job and bother to write the cover letter, not to hear back. So that's why I'm granting all these interviews because these people reached out to us we should reach back at least with a 10 minute interview. That's my opinion on this though. So I'm doing that this week getting that done so I hardly have time to work on the task force material. But where we left off with the mentorship program. If my computer will go back. We want to conclude the task force and this is something that I want to bring up at this meeting we kind of want to conclude the task force because this task force can go on forever you're always going to have documentation needs you're always going to have. You know, again the working groups are gone but somehow this piece needs to continue to live on once the task forces is done. I have a lot of the mentees, even though I can only select one. Most of them have agreed to stay on the mentorship project as unpaid mentees. So they've already started signing up for things and one of the things they signed up for is again we would like to present the findings of the task force and kind of ended to move forward to, I'm going to call it meetings task force. And the mentees want to do the presentation. So in the next few weeks I'm going to be working with them, again and the person who is the mentee select will be managing this. So we want to give to the TOC in three weeks maybe four weeks whenever our next session is a presentation on the conclusion of the task force and kind of moving forward to task force maintenance. And these people have already signed up to do parts of the presentation. So I think that that's great get them involved. They're like terrified of the TOC they're like are you sure we can do this you know so it's really cute. I love watching them learning stuff it's great when they figure out things in the community like I told one gentleman. He wanted to prepare some items in advance for us for next week, and I told him he can just go under mentorship and create his own wiki page and put the information there. And I thought that was like mind blowing. I can, I can use the hyper ledger wiki page I'm like yeah of course it's your page. You can do whatever you want you're part of the task force, you know make a page put your name on it put your stuff there and next meeting present. So that's basically where we're standing now again the task force is going to be working on supporting maintainers in their GitHub to documentation efforts. So we're going to be supporting been in the hyper ledger community when they come out with a new branding, getting PowerPoint templates to the community with the right color schemes and logos on them so they don't have to worry about that they just have to worry about the content. So we want to work with the best practices, and so far as the documentation needs how to get that set up, as well as the onboarding task which is looking at the five or six locations people come into the hyper ledger community whether it's the GitHub whether it's the LinkedIn page the web page the wiki page the, however you're get discord however you're getting in. We want that onboarding task to be able to define what type of user you are right away and give you a one click to get where you're going, because right now everybody's coming in the same spot and they have to figure out where they need to go. What the documentation task force wants to do with the onboarding task force is to get those user personas in places where they need to be, and then the documentation to support their learning of whatever workflow they need. So, that's basically it for what we're working on again you should see a big presentation from us on a TOC call in a few weeks. If that's okay with tracing and everyone else. Okay. Looks like Arunama has a question. Yeah, I do have a question regarding so I have scheduled an interview tomorrow with Bobby, and I wanted to know like, get some insights on how to prepare for it and what are the areas that that I should be focusing on for the interview. Don't worry about a thing it's just a 10 minute interview where we're just going to get to know each other there's really nothing. It's just a sit down with me and we're just going to have a nice 10 minute chat there's no preparing. It's just talk about your resume we're going to talk about, you know what you, what your passions are that kind of thing. Oh, that sounds cool. Thank you so much. I look forward to it. Yeah, yeah, me too. Any other questions. Nothing I'll turn it back over to Tracy. Okay, thank you so much Bobby. So I think then for next week, just a reminder, I did re listened to the meeting that I missed it looks like Peter you had volunteered to lead the automated pipeline task force. I'm thinking it's time for us to add that to the agenda sport next week so just telling you this week so that you're prepared ready for that. And then, David I'll work with you to find when the next best time is for you to come in and present. If it's next week or the following week or whenever it happens to me. All right. Great. Anything else that anybody would like to bring up in the last 50 seconds. Nope. Okay, so thank you all for attending thanks David for the presentation Bobby for talking history the task force, and we will see you again next week for those of you in the US. Have a great long weekend.