 Can you hear me? Hello? Hey, some deep. Can you hear me? Hi, Peter. Hi, some deep. Can you hear me? Yeah, I can hear you. Oh, nice. Yeah, through struggling with audio, because I was talking to him this whole time and I thought I had audio issues, but I don't. Can you hear us now? Oh, yeah, I can hear you. Nice. Okay, today I have to leave 10 minutes earlier. So I want to very quickly show you the things that I have. Just give me one second. So the big thing is to see things, the GRPC legacy versions. There is a pull request about it, but it's broken at the moment because I just upgraded all the fabric versions to the new one, but then that broke the compiler, of course, in some places. So what I was going to ask everyone is to give some sort of guess on how fast or if at all, can you update the packages that you have that use the old fabric? Because of the GRPC dependencies being end of life and also the fabric one being end of life. I'm not actually sure if fabric one is end of life, but I think it is. So it was being end of life and not receiving security updates. We just cannot have them in the code base anymore as dependencies and we cannot release the 2.0 as long as we have these dependencies, so it's pretty important. Okay, I'll check for the Viva components. Yeah, I'll also check our Contribute code. Okay, if you want to see which packages are affected then you can just take a look at the link that I put in the agenda document and also in the chat in Zoom because I found all of the outdated versions in this pull request. You can see it here. You can see a few, if you were on two point anything, then you have nothing to worry about, but if you were on 1.4 something. Yeah, like the example discounted asset trade and then that needs some attention. Yeah, okay. So I try to make it as easy as possible. So here's the list of files in this pull request and then you have time. Please take a look. So I was seeing that you have removed Fabric CA client. Is it now embedded in the fabric network? That was my impression because there's no new version. Fabric CA client now. Okay. Yeah. Okay. I'm going to double check that right now. No, I was wrong. I have no idea. Oh, there we go. This API is deprecated. You should use the, yeah, but with that said, we could still use Fabric CA client if we want to. It's just that it is deprecated, but that means we can still click again down the road. Yeah. Yeah, I was saying even all these three, I think deprecated fabric network, fabric common. If we go there, they also, I mean, they are saying this for a long time since they released Fabric 2.5. Now they have something fabric gateway. Yeah. Yeah, but that's just a deprecation. So in my opinion, we are not in such a rush to migrate to this gateway API, but we are in a rush to migrate away from fabric one because it's not getting security updates anymore. Okay. The GRPC at least. Okay. So yeah, then we can keep 2.2.1. Yeah, I'm totally fine with that. And then the other thing I had very quick was asking for reviews on a specific pull request such as this one that I'm showing on the screen and I'm putting on the chat as well. But then also I wanted to give a little nudge everybody because everyone has quite a long queue of pull requests to review. I'm just trying to look through my notes. Sorry. Because I have. Oh, there we go. So I to make it easier. I created a list of links for everyone so that you can just click on the links. If you want to see the pull requests where your review was requested. I'm just formatting it in the chat window. There you go. So if you click on Sandeep's link, then you see there's a bunch and a lot of these came in a while ago. And if you feel like you just don't know enough about a certain part of the code to actually review a pull request, that's totally fine. If you want to pass your vote to me or something, because you just feel more comfortable with me taking a deeper look at the review. That's totally fine too. It's just the one thing that I want to avoid is that we have something open for months and no one is actually looking at it. Okay, I look into it. Thank you. And I'm not singling you out. There's a link for everyone in the chat. So this is free for you. Yeah. And if you want to just defer to me or somebody else, that's also totally fine by me. Honestly, we just have to keep it going. Maybe share these links on the discord so that others also know. Oh, yeah, absolutely. That is a good idea. One second. Yeah, so the links are there. Okay, so that's enough of that. To the agenda again, just to remember. Yeah, and then FII everybody will try to apply for the graduated status. We talked about this. The TSE was very receptive. So we're thinking we're doing great. And I will work on the paperwork to make it happen. I don't yet know exactly what that entails, but I'm assuming there's some sort of form or document or proposal that we need to write. So I'll work on draft for that. And then I'll just let you know how it goes. So that's all I had. Anyone else has any questions, topics, anything to bring up. I think from me. Okay. Actually, I have one topic. It's not very urgent one, but we, we submitted or we have a poor request about graphic user interface that let you see let your let your activity like tokens and so on. And we talked to talk to with Hyperledger Foundation's people last week and they and including Fujimoto, they mentioned about the explore project, which is not actively updating. Actually, they are updating, but they are very slow. So they, Fujimoto especially mentioned about taking their code. Somehow, he didn't mention how we, whether we should incorporate their code or contribute code. Our code to their project. We, there's no specific way to do that. Do you have any opinion or suggestion about that? I'm totally fine with it. I have a little bit of bandwidth to help with it. Well, it seems that their project, explore project don't have enough resources. So that's the problem. But yeah, I understand your point. Yeah, anyway, I think either way, we have to talk about talk with their explore project team. But I just wanted to tell you about Hyperledger project management people's their view. So maybe, maybe I can come up with a better strategy or something soon, hopefully. Yeah, thank you. Just starting about that. Okay. Yeah, thanks for having those conversations. We should try to do something to help. Cool. If nothing else, then thanks everyone for joining and I'll talk to you next time. Just one thing, Peter, can you quickly review the what the province PR? So he's an Hyperledger intern, if you might know. He had some DCO issue, the last issue he has resolved it. So just check it and we can quickly merge it. Yeah. But sorry, which PR is it? 2564. 2564. Yeah. Oh, this one. Yeah. Oh, two minutes. Okay. Yeah, I didn't see it in my queue. Right. DCO fix. Okay. Is it just one commit? Yeah. Okay. Okay. Yeah, thank you. We have to I'm trying desperately to get our pending poor request count down because there's just too many of them open. Yeah. Okay. Okay. Thanks, everyone. Okay, thanks. Yeah.