 Hey around, can you hear me? Hey Peter, sorry for being here. Yeah, no problem. Can we get started? I think I'm not sure if anybody else. Yeah, I just don't know who else is joining, but I guess it's time. Can you see the screen share? I do. Okay. So hello and welcome everyone to the hyperlinked activity maintainers meeting. Please abide by the antitrust policy that I'm showing on the screen and also the hyperlegion court of conduct, which you can find linked to on the Vicki page with the agenda for today's meeting. And with that said, I want to skip discussion item one because I have not had the time to prepare for it, but I do have discussion item number two for which I wanted to share my screen real quick. Yes. So the interesting part here is the auto upgrade syntax. Hopefully you can see it. So if I search in VS code and I search for only package JSON files that have the auto upgrades symbol, then I still get 186 results. And so what I was thinking is that I was just going to do a replace or to remove all of these and then send a giant pull across with that. But before I do that, I wanted to run it by everybody. If that's okay. Because if it is going to remove the carrot or not, yeah, yeah. So that way it's just the exact version pinned down. Then the auto upgrade using till day. You can probably replace that also. I think even that. So what's the main difference between builder and carrot? The patch version and carrot is for the minor version. Yeah, I'm not able to define. There are no. But it doesn't matter. I would want the till this to go as well because yeah, it doesn't matter what patch or it doesn't matter if it's a patch or a minor because if someone is pushing malware with an update, then they can do that in a patch as well. They just won't care to respect semantic versioning standards. Anyway, so as long as any kind of auto upgrade is possible, it's basically a remote code execution flaw, in a sense, by way of supply chain attacks. And it also leads to those kind of bugs where Valentinian maintainers of dependencies mess up and they accidentally push breaking changes in as a patch, which also has happened. So yeah, it's more manual work to keep everything upstate manually, but it's safer. That's basically why case. Okay. See, you didn't find anything. No, I thought there would be some, but there's literally none. Okay, some fun to me. Yeah. Okay. Then I'll make the pull request and then assuming that the tests are actually still passing, we can merge it. But obviously, if, if somehow it just destroys everything, then then the approach will be to take a step back and try to do it piece by piece, you know, maybe one directory at a time or one package chase at a time and then figure out where and when it breaks. But hopefully that won't be the case. Yeah. Okay. So that was one thing. And then I had another agenda item. Oh yeah, cleaning up package lock files. So package lock files are not doing anything in the sense that it is the yarn.lock file in the root that holds all the dependency information at this point because we hooked up all the packages to the mono repo. But with that said, there are still package lock chasing files. Oh, actually, there's only one of them. Yeah. So there's still this one policy DSL. We can, we can get rid of this file. Yeah. I mean, this, this was experimental code, which got the input we added. I mean, the important to we were right in the beginning, you know, making the first drop into the lab project. It's never been used. So get rid of it. Somebody needs to assume the work on this, but it's nothing being done for two years now. Well, if, if you're confident of it being deprecated, we could also just delete it, but I don't know if there's any problems with that. For now I'm just talking about deleting the package lock Jason file. Yeah, no, I'm not talking about deleting the folder, but you can delete the log file. Okay. Yeah. All right. So the pull request then will also include the deletion of the lock file just to do more cleanup. Yeah. And what else did I have? Oh, yeah. So the back, the pull request backlog decluttering. I'm just going to have to do that next week because I'm still working on the list of pull requests that I want us to look at together. And also as we didn't make it and we would need him there as well. So yeah, I'll just put this item in the backlog for the next week. And then last one is the quarterly report, which I have not created draft for yet, but I will try to get that done tomorrow and then I'll send it out. So when you create it, will you create directly as a PR and the DOC level? Yeah. Okay. And if I want to edit it, then what should I do? I think you, because you are on the TOC, you have edit rights on it automatically because it's in the TOC repo of which we are maintainers. Yeah, but I don't want to do that. Do you want to share a description? And I'll give you updates as soon as possible. Like within a few hours. Yeah, that works too. I'm totally flexible. Thanks. Yeah, I, sorry, go on. You had other things to talk about. The last one is just for you. Because I figured maybe you wanted to talk about a documentation if you have anything, but other than that, I'm done. The only thing I want to say that is, sorry, I, I couldn't finish it last week. I got a bit sick. And I was traveling until Monday this week. So, but I do plan to get a PR together by tomorrow. So plan to work on that today and tomorrow. So hopefully can do that in time to add an entry in the quarterly report as well. Yeah, no worries. That sounds great to me. Just thanks again for doing it. Sorry for the delay. Yeah, the, I mean, we already talked about this on the, on the chat, but the SITP, sorry, the ITF conferences a couple of weeks from now. And the date for the our session got rescheduled, it looks like the preliminary agenda was on Thursday, the 27, but now it's on Tuesday, the 25th. Same week, but different day. Oh, okay. Okay, I have to go back and do some planning then. Because I wanted to, I wanted us to get together. Yeah. And I have a venue. I have a rooftop on my building in my building. We can do, we can do that. I'm there the entire week. So, and I believe Rafael also will be there. Yeah. Yes, yes. He messaged me as well. Okay. Yeah, I'll figure it out. Sure. There you go. Oh, nothing else from me. Yeah, nothing for me. No. No. All right. This is a quick one then. Thanks everyone for joining and I'll talk to you next time. Thank you. Thanks.