 All right, welcome everybody to the April 13th hyperledger technical oversight committee call as we are all aware. We have the attendance here. Yep, everybody's aware at the trust policy that we must abide by and our code of conduct, which is linked in the agenda. So for announcements today we have the deaf weekly developer newsletter that goes out each Friday. If you do have something that you would like to include in there, like Stephen maybe this new documentation site. Please do leave a comment on the wiki page there in the that is linked in the agenda. Other announcements that anybody would like to make today. No, okay. So for quarterly reports, we have the basic reports. I looked at it this morning I think there's two people were waiting for reviews on so that we can merge that we have the attack that report that has come in as well. It was due today. So, for those of you who haven't had a chance to look at that please do. I didn't see any questions or comments on either of these that we do need to talk about in this meeting but if anybody has anything they'd like to bring up. Now is your time. Okay. So for the past reports. We do have the transact report that was due February 23. The issue and the pull request that Peter open last week. I did not see any updates as of two days ago when I created this agenda. So no comments. Nothing has happened there for those pull request or those issues. They're still waiting for any of the transact main hitters to respond to. So I don't know what that specifically means but it is pending or lending towards. Maybe that this is a project that has gone. I don't know if it's going to be valid. So, I think I will potentially give that another week and then maybe if we don't hear anything from that, maybe I'll open that end of life ticket like I did for grid and we'll see if we can get any responses coming from that. Any thoughts on that. Steven. So should the TOC have the right to merge a pull request or the authorization to merge a pull request. So we haven't in the past that right. We have left that up to maintainers. I think it's something like this, right? That is an update to documentation typically like when we do the end of life or we do a dormant, we will push a pull request to the repo to make sure that the Remy states kind of the status of it. But typically we don't force those pull requests to be merged. Do you think we should, or does anybody think that we should have that right as the TOC? I kind of think that, you know, reading through the security document that Heart Road and then this that there are times when it seems like it should be a good idea but I'm not sure. I would say non maintainer and non TOC member and a person who frequently uses force mature to merge pull request. I would counsel against doing it. They are the maintainers for a reason. I'm willing to take the heat. I don't know. I mean, I don't think it's a good idea to say, and by the way, TOC members have a merge bit on every project. Yeah, okay. I certainly see members and certainly not acting alone but that I get you. Yeah, fair enough. Yeah, I also have the feeling that I mean this brings, I mean, if we get the right to merge things on a project where we're not the maintainer I mean this gives us mighty powers a little bit and contradicts a little bit of the advisory role we should actually play. So I'm also against it. Okay. So I agree to the extent that the maintainers are to responsive. There's a limit right if they don't respond at some point to well was going to do it. Sure. That's why I meant by doing it. You know, force mature right where. Yeah. So if the TOC were to vote to EL transact today, which I think would be great. I would encourage the pull request that Peter put in to say here's where the code lives. And then I would also have a PR that change the, in the settings. YAML file to make it archived for all the transact repose. So, that's what I would do. That's the mechanics of. So that's essentially what I was saying I guess the only thing would be whether it has to be combined with an end of life or not I guess it doesn't really matter because if it's not an end of life then they're actually responding and the maintainers are doing what they should do so. Yeah, probably irrelevant. I think we didn't we have discussed this in the past where maintainers are not responsive. And we have been vocal about it like how long we should wait to take an action. I see it's been waiting for 90 and probably we will give that period of time grace period before we take an action. But in this case, let's see if we can remind them one more time to do that on the discord. Okay, Arun, I think that's your responsibility as vice chair to remind people of past year report. So, feel free to do that. I agree. Peter. Peter, we can't hear you. I can't hear you. Here you are muted. Can you hear me now. Yes. Yes. Okay. Sorry, too many microphones. I agree that the TSE should not merge pull requests left and right on active projects. But I also say that special cases like when it's being end of life or it's being redirected because it's been low key abandoned. I feel like that is a special case. Maybe if not the TSE, but the staff should definitely have some sort of legitimate claim to merge pull requests that there's nothing but updates documentation to point people to the new code repository. So I would, if we were going to define what is allowed and what is not, I agree, generically, any pull request should not be merged, but this would be definitely one of the edge cases there. I think it's beneficial to allow it. All right. Thanks, Peter. I sort of agree with right here that maybe it's not so good to have lots of people with PR privileges on a project where they aren't maintainers. You know, I think that the TOC has plenty of tools to deal with projects where, you know, pull requests need to be done. So, you know, maybe those tools would be more useful instead. So from what I hear status quo for the way that we've been doing things where TOC does not have any sort of special privileges on the different repos across the Hyperledger organization. And if we do obviously vote for something at the TOC level to that would require some sort of read me update or some sort of archive update, then that ends up falling to most likely Rye or somebody else on the staff. Did I get that correct? Yeah, that's the status quo and I think it should remain. Okay. Sounds good. And then the second overdue report that we have is URSA. I didn't see any reminders going out since the last time that Steven sent one out. A route it might be worth sending a message out to the URSA folks as well to see if anybody might respond to that. All right, as far as upcoming reports, we do have the fabric one that is due today. So hopefully we'll be seeing that one show up here in GitHub shortly. There are no reports due next week. So, we'll just make sure that we get the ones that we do have in GitHub reviewed and merged. All right. So then for discussion items today, we do have just a short update. I think maybe on the GitHub actions and where we're at. And then also task force discussions. Any other topics that anybody would like to make sure we cover today? No. Okay. So, right. Can I ask you to give a short update on GitHub actions and where we're at there? Sure. So we had a great meeting with GitHub and a lot, we learned a lot. One thing that they did is they gave us a gratis pro account, which bumps the number of concurrent runners to the concurrent free runners up to 60 from 20. So that's good. And another thing that they gave us access to was the a beta program for large runners. And I set up two large runners. And the interesting thing about these two large runners is, I don't know what they are. But they can build up to 50 jobs at once. I've turned this on for five specific repos as I'm testing it out to see how it goes. Turns out they're much faster than the old ones. So I'm looking for, I guess, volunteers of projects. I just right now we have just a few repos. And I want to test this slowly. So if anyone wants to volunteer a repo. To try this out. Please reach out directly. Peter. I was going to say I volunteer cacti, but then you said directly. Okay. Well, let's let's talk offline. Okay. And that's all I got David. I'll also add that they invited, they gave us a few invitations to an upcoming maintainer summit and they were very excited and interested in having people from Hyperledric come and join that. It's going to, I think they said, right, correct me if I'm wrong around 100 maintainers from other open source projects that use GitHub and they were hoping that, you know, some people would from Hyperledric would come and share their opinions and experience and engage in discussion. So we just have a few invitations. I did email a few people about that. So if you're interested, let me know. If you haven't gotten an email from me and you're interested, let me know too. But they were wanting to get a total from us or the names from us within the next week or so. So just be aware that there is that event next month. And if you're interested, let me know. David, that's a virtual summit, right? Yeah, thanks for clarifying. Exactly. Yes, yes, yes, virtual. Is Rai going to be going? Because that would be really good. Yeah, Rai is going, but we had a few other invitations. So I reached out to some other maintainers as well. Yeah, they gave us five invites and we've reached out. All right. Thank you for the update, Rai and David. Looks like we're making some progress here. We might not have to have the GitHub actions update on the meeting every week. I guess let us let us know how that's going. If we are seeing improvements across the board. That's great. We'll keep up to date if we need to on other future changes. All right. David, I just lowered your hand. So I'm hoping that's good. Thank you. The, the task force discussions that we do have today are both Bobby's. Bobby, if we don't get to both of these today, it's fine because typically we only do one, but I know that you're in charge of both of these. So I did put them both on the calendar or on the agenda for today. So feel free to start with the one that you want. I'm going to share my screen. I'm going to start off with a little background. So the task force have come out of the new TOC. Moving like the learning materials, working group out of a working group and into more of a community accessible resource. With that said, the task force has certain things that need to be done. And we both tasks forces, the onboarding and documentation applied for the mentorship program, and both got accepted. So now there's both mentees coming on to these projects. So there's a lot of activity going on. People are getting ready to interview the mentees. It's getting very exciting. So right now, our main goal for both of these task forces is to kind of define what we try and I apologize. I have dogs here. I can't get rid of. So they're snoring. If that's what you hear in the background. So these task forces. Goals now are trying to define what the task forces are going to be doing as opposed to including what the mentees. Portion of that is because now they're coming to be kind of intertwined. So the, the mentees are trying to define what the task forces are going to be doing. So now they're coming to be kind of intertwined. So the mentees will meet with us every Monday when we meet for both of these task forces. They'll be more deliverables set out on a weekly basis as per the mentorship program. So right now. I'm not going to say confusion, but both of these task forces are redefining their deliverables to try to figure out exactly what we need from both of them. So this is a good time for me to do this with the TOC, because I'm looking for as much input as possible. This is a wiki page. I'll put it in the chat in a minute. What this is the answer will start with the onboarding task force. So the onboarding task force goal is to make people who come to either the website or the wiki page. Get where they need to be within a click or two. We don't want that because it takes even me forever to find things. I don't want to put them there. So it's, it's hard to really navigate through some of these screens. So we started with. The website with use and learn and the participate, because if you go to the main page, they're going to analyze that. So we have. I'll start at the beginning. Actually, we have tasks set up. The deliverables that we actually want. We want to identify where we are. We want to identify where we are. We want to identify where we are. And the first one was again, identify where people come on to our community. And that was the wiki page and the website. And then the next task was identify areas for improvement. So that's kind of where we are now. We. John had a. Document for. Let me find it for a second. I think we've analyzed both of those onboarding. And they had going to put their recommendations here for our next meeting. Again, the next section was the wiki page and they get started. And there is a PowerPoint there that we're going to get some recommendations on how to update that with David. He was in the meeting. So it's something that he agrees that needs to be spiced up a little bit. Maybe incorporate the new marketing. And then the next section was the initiative that's going on. That kind of thing. And then the next was the frequently asked questions. And again, those need to be updated as well. So we're looking for the mentee to maybe help with that. And get. The onboarding mentee get that situated. And we'll go look at the onboarding mentees. Application in a second. Not our mentorship application in a second. But we're going to be looking at, we're going to be talking about maybe doing a different look. This is a website. That was introduced in the meeting. And again, the meetings are all recorded. If you need to listen to him, this is a really fascinating one where we're trying to get a website up that maybe helps out with the documentation and helps out with everything that's going on. In the community. And again, all these links are here. And what we're more looking for is. Like, what do you want to see? How would you be able to jump into this community? Where were the buttons that you want? I mean, if you want people to get involved in your project. Do any of these, these use and learn and participate. Go look at them and see, do they help you out? If not, you can go right to this wiki page again, and just put a recommend that you jot your name in here and say, I think this needs to look better. I think this, or right now we can open it up for discussion. And talk about how onboarding can be easier. Again, we didn't even get to the. Section on the wiki page where it's just the tasks that are being done in the community. So right now I'm going to pause. And ask anybody if they have any questions. Go ahead, Tracy. Yeah, so Bobby, I guess the question that I have is really around. If we look at kind of what these current processes are that are being reviewed. My thinking is that this is more for somebody new to the community who's just starting. And I know when we started this task force, we were discussing the different personas if you would. And so I want to, I'm curious if this is. Only that persona that we're looking at right now, or do we think that we should be adding the other personas at this point too. Well, that's what we're trying to determine like who you are and where do you hit. So the first step is to figure out what we have and what, what we think should be updated about it. So again, like with the frequently asked questions, they need to be categorized because again, I have different questions than someone who. You know, is a developer who wants to become a maintainer for, you know, it's all different. Again, personas or, or users of this documentation. So we strongly recommend categories for a lot of the different places, but everybody's coming in in the same place. No matter who you are, you're going to go to the website, or you're going to go to the wiki page to get information. Or the discord channel, which again, we did not include this, which will be included next week. So we're just trying to understand where the points are, people are coming in. And again, like for the developers, I'm going to just see. When you come into the wiki page, which is, you know, where the web page will direct you if you're a developer. Where do you, where do you go? If you want to get involved in, you know, a project, obviously you would go right here to fabric. If you wanted to do something for fabric. I don't know if you would know from here. How to get involved. So like to me, that's an extra clip because now I have to go back and see, oh, where is that like actually, and then maybe it's here, maybe it's the recent issues or, you know, and that's where you go to these buttons, which we started to analyze. So again, we're looking for recommendations on how to get people to be able to go to the wiki page and know where they need to go. And then obviously give them the information to onboard them. But first we have to figure out how they're getting there and where they need to go. And I, and any suggestions come to the meetings Monday at noon Eastern daylight time. Or raise your hand right now and we'll jot some notes down or. Yeah, I wonder how many people show up at. In GitHub first. If that's an entry point for people. It's hard to say, right? Like, I guess what I'm thinking is that each of the potential entry points that we have should be. Should allow for some sort of redirection to where people might actually end up going. I'm thinking it's been a while since I've actually looked at the. GitHub. Hyperledger page, right? Like, but I'm wondering if there is something specific there that. You know, takes you or makes you helps you understand all of the different repos because we've got a ton of different repos there. And I'm guessing probably not. And so maybe that's something that we should take a look at as well. Trying to computers very slow. I was trying to get to, to, to GitHub, but I'm trying to move it over, but. We'll have to work on that another time. So, yeah. So I put these two in here too. So for Monday, when the task force meets, we'll talk about what the GitHub, and if anybody wants to, again, to be a part of that, go ahead and just leave your recommendations here. If, you know, what they think of entering in GitHub again, you know, that they want to probably show or you know, they want to be on the northern side of GitHub, but are there guides to, to, you know, make you get to where you need to be in a click or two? Nobody wants to be going back and forth. And same thing with discord, you know, I know discord has done really well. Kudos. I mean, you get there, you know, exactly what community you're in, you know, the categories are clearly defined on the left. Everybody knows. You know, who's online. It's, it's very well done. Again, that's the onboarding task force and we meet Mondays. Here is a one more thing I wanted to go to. Where is it? It's the mentorship. I don't know if I have the mentorship program here. Oh, there it is. So again, now we're having people who are gonna apply for this and then we're gonna interview them and make sure that we get someone with the best qualifications but we'd have to answer the question and what are we looking for them to do? So what qualifications do they need? So we're looking for them to gain this information which again is in line with what we're talking about. We just now have more places that we need to research for onboarding. So again, we're really in line with task two of the task force goals, which is analyzing the onboarding spots that people come on and making recommendations. So again, if anybody, I know there was talk about documentation at the beginning of the call, we'd love to any suggestions, websites, anything to help us get people two clicks to where they wanna go or three clicks, whatever. So again, that's the onboarding task force. Leave it open for questions again. Now the documentation task force is kind of in the same place as the onboarding. We have a mentee coming on, we're defining their tasks. This is a little easier to define because it's documentation, it's pretty much straightforward. So what the task force deliverables are, we've gone over these before in past meetings. One of the things we definitely want the mentee to work on is last year, the lab progress or a few years ago mentee mentorship project was for the documentation template and it's still here. It needs to be more robust, it needs to have updated instructions, which is what we're gonna work on for that. And that's clearly defined in, and again, any suggestions for that, that's one of the thing that the documentation task force or in the learning materials working group, we had done a lot of research on what everybody's using. We still have all that information, all those graphs, it's still there for the mentee to analyze and research and to definitely get some of these style guides going and help people with the tools and templates they need to keep choices for them, but still keep it in the hyperledger look and feel and also to categorize a lot of the information in the community that is really hard to find. So there needs to be a way, like if you wanna figure out where to go, easier pathways to get there with the onboarding. And the one big thing, which is again, more of a task force than I guess a mentee job is, at the end of the task force, we have to have recommendations back to the best practices task force. So when we wanna finish this, we want our task force to save that task force, we feel best practices for documentation are this. And I'm pretty sure a mentee is going to help out with that, but that's more the end result for the task force. So those are the two places we are right now. One of the other things that I think a mentee should assist with, and I've talked to him and David about this is some of the projects that got accepted in the mentorship have documentation needs saying they wanna document what they're doing and they wanna do it right, they don't wanna reinvent the wheel. So we were suggesting maybe the task force or the mentee, if they're up to speed enough, can do and give those recommendations to each one, either reach out through the initial mentee meeting or in some way get in touch with them to know that there's resources available in the community. And what a great way to test them out, have the mentees test out the templates. So that's basically where the documentation task force is. Again, we do have definite audiences that need a specific documentation guidelines on how to get to where they're supposed to be going. And then the, let me see if I have the mentorship for this. I have all the other mentorships, but I don't have this one. No, I don't have a link. But again, here are the task force deliverables if you wanna check them out, they're all right there. Up, I think I do. Yep, so this is the mentorship application. So if you know if anybody's interested in doing this, please send them to the program, the mentorship program. It would be wonderful for them to apply for the mentorship. All the information is in the Hyperledger Mentorship Program on the Wiki page. So I'm gonna ask if anybody has any questions or ideas on the documentation task force. Nope, then well, if anybody wants to get, oh, Arun, go right ahead. Not for the documentation staff force, but the other one, the onboarding task force. I know previous conversations, so at least until the last year's mentorship program was that like we come up with expected deliveries, like for instance, we come up with items that we want as part of the task force. And I know David wanted to connect with the Linux Foundation styling team or the UX team to work getting those contents onto the website. So it would be nice if that's part of the task force effort. It is actually, I'm drawing a blank on the gentleman's name who is on the call, but he had designed this for us as a way to introduce that and we're going to talk about it more on Monday. Perfect, thanks. And again, we really wanna work on the start here and we're hoping more people who have ideas about that will show up on meeting on Mondays. Okay, well, thank you for letting me present and I'll turn the meeting back over to Tracy. All right, thanks, Bobby. So any other topics that anybody would like to cover today? That was actually the end of our agenda. So all right, no other topics. So I guess the ask then for the folks who still need to review the outstanding reports, project reports, please do so. And I guess, I'm trying to think, I think best practices is the one that's up next. So Dave, you're up next week for task force discussion. Okay. All right, so then we will see you all again next week. Thanks, Tracy. Okay, thank you. Bye. All right, thank you, bye.