 Sorry for being late and also I did not have time to create an agenda. I had a few things to discuss. Oh yeah, the pull request. The second pull request about that fix that I made for the open API generator. Yeah, I think it got merged, right? It did, thanks for merging it, but it had a bug. Oh, okay. It was so silly of me, there was a race condition in the bug fix for the race condition classes. My screen. Can you see my screen? Yeah. All right, so then we can start the actual meeting. Hello and welcome everyone to the cacti maintainers meeting. I'm also invited by the anti-trust policy notice that I'm showing on the screen. And also the hyper-legal code of conduct, which is linked to you from the agent document, which I just created about 10 seconds ago, but it's important to have it because then we can now document the meeting. The one thing I have is two things, thanks for the PR reviews. And the other one is that I had to sneak in a second fix to my previous fix to the concurrency issue with the jar downloads. And so the whole request that I submitted to fix a Docker container issue. Yeah, share this stuff. Yeah, so here's the fix. I basically just made it so that it deletes the open API tools JSON file once and it forces it so that even if it fails to the lead because of whatever reasons, it doesn't fail the process itself. So with all this now put together, the code generation tasks should be parallelly running, but it should not have race conditions. And then the actual port request just about upgrading the fabric images. But yeah, so the reason I'm talking about all this is because I had to modify the commit message to say that also snaking the hotfix and also because I'm asking for reviews on this in an expedited manner just because it has a bug fix that hopefully makes the CR more stable, which is something that we desperately need because it's been slowing down progress a lot just the fact that the CI takes too long and then it has to be retried a bunch of times when it fails with false negatives. Yeah. I'm not putting this on the zoom chat so that you have access. Yeah, so that's all I had. You had some questions about adding the interns to be reported. Oh, yeah, just for that, just wanted to say that I'm working on the documentation. So made some progress, not yet finished though, but I should have something to show you pretty soon. That sounds great. Thank you. And, yeah, on the interns. So how do we like, do the interns have to join the hyperlegion organization. And they don't have to know, but I they can. It's, I guess it's more of a question for right. But I'm pretty sure that if they want to join they can. If I have to assign an issue to them, the name doesn't appear in the list. That's right. And that is because they're not in the organization. And they don't have, they also have to have at least triage permission on the repository, but you cannot give them that permission unless they join the organization first. So it's a multi step process. But if you don't want to deal with all of that the other alternative is to ask them to comment on the issue saying hey I would like to work on this. Or literally anything else. It doesn't matter. It's just that GitHub automatically gives you permission to assign the issue to their names. Once they commented on it. And the reason they do it this way is because people have been abusing other people by assigning issues to them without them asking for it. And then they would have something mean or a death threat or some crazy stuff in the issue description that had nothing to do with actual like open source software at all. So they they made this permission system for a reason but for us it's kind of annoying because it's really just some extra hope that you have to jump. Okay, that makes sense. If he, if they did want to join the organization, we heard us right, right. Yes, and they also change that so you don't message right directly anymore you just go to the either to see or some other repository I don't remember. They open an issue. And they have a template that you can fill out that ask the questions of okay who is this person what is the GitHub username. What's their email, and then rise sees that issue and then he adds them to the org so the whole old way of just messaging right directly is not recommended anymore because he was quite overwhelmed by the DMs. If I remember correctly the, they asked us to email community architects, but I don't know if that's the same procedure is supposed to follow or where is the double check the link, because I have it somewhere I can look it up. Because I was just doing it. Someone who just joined my team. Accenture as well. So if you if you give me a minute I can get the link for you. Oh yeah it's not a to see repo it's the governance repo. And then this is the link. It just takes you straight to the new issue creation and then there's one template specifically that you can choose for add someone to the high political you have work with the first one. Okay, thanks a lot. No problem. Other than that. So, right. All of our shoes from the Viva report to a guy. Nice. Yeah, officially we kind of said, I mean, the Viva repo, we're still keeping around because there's an item dependency there. So, but, you know, as soon as the dependency gets. I mean, as soon as they say they don't need it anymore than we can. Yeah, that's fine by me. I don't want to rush you or anything. If there's anything I can help with just let me know. Thanks. Yeah, but any anything new we are doing a new back pack so that we just making some. Yeah, vulnerability updates. Yeah, that's good to know. That's, I mean, it was always going to be a gradual migration. It would have been impossible to do everything all at once. We're still working on some details and we will continue working on some of them. The important thing in my opinion is that now we have the code in the same repository and then you're working together. We have communication and we have the issues in the portal question all that. That's something. Was there anything else. I don't have anything else either and I don't know if it's so we wanted to join maybe he couldn't make it today. Oh, yeah, I just didn't have time to read the score. So, okay, then. That's cool. Then we can talk next time and thanks everyone for joining. Thank you. Thanks. Right. Thank you.