 Meeting for May 3rd of the year 2022 and we have an agenda there. Bruce, if you want to go ahead and put your name and I'll put the, by the way, I'll put the agenda link in the chat there. Right. And take a quick second to look over the agenda and any modifications we need to make anything. Not quite right. Good. I've got a couple of things, but I can add them into AOB. Yeah, that's fine. So, Adam, Adam, where do you think appropriate? Um, why don't you go ahead and do that and I'll cover the 1st item because we'd have that taken care of. So, last week we talked our last meeting. We talked about archiving the community repo Diane put that in Christian signed off on it and actually the community, the old community repo. That has now been archived. So we just need to add those few pages into the current documentation that we wanted to save. And actually, I think you did that. Is there, is there any page that hasn't been moved over yet, Brian? There's no page that hasn't been moved over, but there are a couple of things like the, like the subgroup. Chairs that we haven't actually, right. So, they haven't followed what we said we're going to do in the charter. Right. And, and so I wanted to actually make it public and announce it via Twitter. But it turns out there's a complication with Twitter, which we'll talk about in just a bit. That's the ongoing saga of the Twitter. Okay, so technical documentation. I understand it's a work in progress. Brian, you're still. Yeah, as I said, as we were talking before we started the meeting official, I broke my cluster. So, I spent days sort of trying to work through things and probably made it 10 times worse. So I'm actually going to just trash and rebuild the cluster. Then I can continue with that work. So hopefully there'll be some progress before the next meeting. And I can contribute to my time is going to be freeing up. Okay, great. Yeah, working group repo will be waiting to move things over once we actually have our moving plan, which we'll talk about towards the end of this. I haven't got a chance to do the moving of the working group menu around yet. That will probably happen tomorrow. I'll have some time for that. So some updates that we need to push out is I decided to do this as a Q way. Sorry, frequently asked question FAQ. So we actually get asked a lot about like are they going to many 4.9s. And it makes sense, I think to do an FAQ and then wrap it with some texts that says, by the way, this applies to 4.9. Yeah, go ahead. There is an FAQ section in the community documentation. So probably we can just add it into that. Right. Exactly. Yeah. And the 4.10 blocker is over with now. And there is a new 4.10 section. We should change this that they're okay. The updates new. 4.10 that came out. I haven't updated to that one yet, but I hope to, and that was actually Vadim cut that one. So Christian didn't have access, but Vadim stepped into to cut a release. So that was cool. Deaf testers, we need to push out a request for that. And then CRC push out a request to see if anyone of us, but we got another CRC question or actually a handful of CRC questions since the last meeting. I'm continuously surprised how much CRC attention how much attention is being put on CRC in the community. Well, I mean, in the last, what's the last OpenShift roadmap, they actually did talk around a new effort around CRC for OCB. So I think that might have generated some of the interest because I think they're looking at a ways to cut it down further to give that sort of desktop because the sort of micro shift is an edge that doesn't have the GUI or doesn't have that OpenShift experience where CRC is meant to give you that a personal OpenShift with a very, very similar experience. Although some of the monitoring and the advanced clustering stuff is missing, but you do get that developer UI experience. And I think that's why there's the renewed effort there. It's a bit of a dissonance here because I'd be interested to see how that team has got it getting on, which is talked about the, I forgot what they called it, the group that have their own cloud. They were going to look at that. Right. Yeah. And then for the SEF testers, do we have any instructions because when I first started this group, one of the challenges I had is, how do we set things up? Because a lot of this, the instructions are written for OCP and it assumes that you've got access to the registry with the Red Hat operators on. So, do we have a link that we're asking for testers that they can actually follow to set it up, sort of work with? Yeah, I think we might approach, maybe we can get Sri to write those up. He was the one who actually had access to his own stuff. Maybe we could ask him to just write a quick page of instructions to demonstrate that. I did see that they have narrowed down the error a little bit more. And are we looking for SEF in cluster or SEF out of cluster that the cluster uses? I think in cluster first, and then anything that we can do for out of cluster is good. I didn't get a chance to read what the latest update was, but apparently they did narrow down the issue even more. And there is a bugzilla further upstream for it. Okay. But yeah, I mean, it would be good anyway because we get a lot of questions for it. So let me see if I can get, let's see, I can't. I guess a related thing is that there actually is somewhere in the weeds, a Rooksef operator. Yes, there is. Which is not in, of course, our operator repository, whatever that might be. Well, for OCP, they've actually done quite a good job because they've rolled it all up into, I forget what they call the operator now, let me have a quick look. In OCP, the OpenShift Data Foundation, that's got the RoofSEF and Nubar, so you get file block and object storage through that. So we want the equivalent really for OKB. Yeah, although it is fairly straightforward, like I installed Rooksef long time ago based on Charles' instructions. And his instructions didn't get updated because he moved on to bigger, better things, but the next time I had to install it, I started with the manifest files that were in the Rooksef repository and just compared it with what I've done before. There are not that many changes that you have to make to it, so it's not that hard compared to many other things. Sure. It's just that, and it is possible following the instructions in the Rooksef documentation once you've got it installed to upgrade it. To minor releases or major releases and so on and so on, and that has generally worked without too much grief. But one of the things that I think it's almost sort of an underlying miasma is that nothing is easy. Compared to many other projects, open source projects, when you do many things, it's a relatively high risk and it's easy to get it over your head because the actual framework is quite deep. I spent, I guess, three weeks teaching Kubernetes implementation to my students and barely scratched the surface. And there were lots of things like networking was too big for me to really touch, much less storage, which is probably worse. Yeah, and it changes on every platform, depending on what's the underlying technologies. That's right. Yeah, and I think that's where, if we had a good operator catalogue, you may not understand it but I mean, with OCP, I can set up a cluster. I can then put the storage foundation on to get object block file storage, I can put key irons, we got local registry. I can just put GitOps on I can put pipelines on and I have a full sort of self contained development environment. I've even put code ready workspaces on hold their workspaces, whatever they're calling them now. And I get this full thing. And I don't need any skills. It's just point and press with the operator. Right. No, I think I think that's really critical. I've been actually pushing that. If you once you get to the point of, okay, the shiny new toys installed, I want to actually do something. Yeah, then you need the various catalog operators. Yeah, and that's why I've been sort of my mantra we need to get these operators. Right, but we're moving forward. I guess we've been sort of sidelined by having to follow continual upgrades. And they are working on the catalog, the new individual catalog for okay D. Certainly that project has been sort of put aside slightly because of some of these larger issues that we're looming. But the okay D catalog we are told is coming right now. Okay D specific catalog. So let's see what happens and push for stuff like this to make it into it or rally the community. But I also, I also think our technical documentation that we're doing will enable people, because again, if I look at the operator. I'll point to this registry thing, but now that we know that just replace that one with this okay D. For 10 operate base image. And then I can just use docker build or podman build. So even things like that I can go in and stop building operators with the instructions on how to do the what john sort of gave us for how to build an operator. We can use that to build the additional operators from just the gate source. So I think the instructions were doing on how to customize okay D will help build operators where when you just look at the gate repo it's just like well nothing works because we don't have access to the registries. We now know how to get past that. I think that's a big plus. Yeah. Okay, took a little bit off course, but by the way, I did install the the latest for 10 without a hitch. Okay, good. No further problems there. And I did go back and just out of interest. I installed the OCP CRC. And that works fine. Okay, which in a way, and it is for 10. Because one of the reasons I installed it was to see because churros instructions were based on for eight. And I wanted to see what, you know, I mean like, obviously, if we're going to do a CRC it has to be at least at the same level that the OCP one is. That's one of the reasons why I was installing that again and also see whether or not it took down my laptop with all the other stuff that's on there. And it seems fine. I don't really have a case and even to use it though. The other thing is that's why I think we need to sort of reach out to the community to get some users who actually have a need to use this and and really, you know, run some things on it. That someone trying to learn OKD would want to do right because this is a learning tool and experimental tool or experimenting tool. We need to find some people who are in that position to give feedback on the builds that we do. Right. I mean, there are, I don't know, there's probably close to a dozen Kubernetes, you know, minimize versions that you can install. You know, like mini cube or kind type things. Yeah, for sure. You know, K3 K8. I mean, the list goes on and on. And I'm very similar. You know, like, I used kind. In the class that I was doing and I had to go back and forth between kind and many cubes trying to see exactly what the differences were. They were guessing CSC gives you things like source to image and it's those workflows that are subtly different from native Kubernetes. Yes, you can achieve them if you put the extra projects on. But just that whole developer workflow with the developer perspective. And saying I can take a git file. It'll then work out. Okay, I can see you've got a maven file in there. So I'll choose a source to image and yeah. Okay, so I think I think where you're headed is really the point in a way is that we if we don't know the purpose for it. Then yeah, it's hard to know if it's worth doing or worth spending time on versus everything else. Yeah, so maybe we should have a discussion of the pros and cons of okay, like. What would it buy somebody because we can always point people to the red hat OCP one success that they go get a, you know, developers, you know, free account. And therefore then they get a, you know, pull secret that will avoid a lot of the grief. And yeah, if they want to do something bigger, if they want to do something bigger, then, you know, they should go over to okay D because if they try and use OCP in a sort of production like environment, then somebody's going to come after them. I don't know if that was true, but at least it's in theory it's true. And, but some things I mean like like mini cube does have a console. It's not as nice. For sure. And all of the, all of the red hat people that are doing all these demos pushing serverless or whatever, they seem to uniformly use mini cube. And the guys that, you know, Adobe that was, you know, teaching operators, he was using mini cube. So I mean, I don't really have a dog in the fight. Product wise. I mean, to be honest, if you're on a laptop. And I think this is what the effort around CRC is. You've got a laptop. CRC is too big. It's too heavy. By the time you've got CRC working, you don't have any resources left for your workloads. And I think that's where Kate's kind K3S, they give you a Kubernetes environment and under two gig of memory. So you've still got a substantial part of your laptop resources free to do your workload. I mean, if CRC is going to be useful, it needs to be into that sort of, that sort of domain where I'm not taking 80% of the resources just to get the base platform running. And I can't really don't have any space left for workloads because that's where a lot of people are with CRC, whether it's OKD or OCP. It is quite a heavy desktop environment or laptop environment for Kubernetes and if I want to do a quick Kubernetes demo on a laptop, I'll pick Kate. Well, and why is that part of that is that, OK, so like the console software has a dependency on metrics. OK, which includes, which pulls in Prometheus, which pulls in all that stuff. And I don't know how well, like is it even documented the dependencies between the different components. But also don't forget that OpenShift is all operator managed, which in a big environment is a huge advantage. But it means that if I run a base system, I'm at 200 and something pods just for the base system. You have that recent error that puts you up near a thousand pods. But I think this is where we're trying to run an enterprise grade offering on a laptop. You want all that management capability when you're running at scale. But on a laptop, it does exactly the opposite. It needs too much of the resource. Well, that's why like at one point we sort of threatened to start up a working group. Which I was happy to be on to go through and slim down the CRC and try and figure out exactly what's required what's useful. How can we do that and. And I'm guessing this is what the useful thing. And I'm, but I'm guessing that's what this new OCP CRC. Effort is about that was announced in the OpenShift program. If you look at what was it then what's what's next. Presentation. Yeah. Yeah. Let's let's stop. We need to communicate to people to get other CRC folks in the conversation other than just ourselves. So that's, I think what we need to do next. But, but I think for our. I guess limited resources. I don't see CRC rising that high compared to all the other things that we need to worry about. So I would leave the question mark on that item. Okay, so moving on to the Twitter issue. So there's an issue that the, the, the Twitter was set up with a Red Hat employees email address. And from what I can gather that Red Hat employee is not going to be an employee or is not an employee anymore. And so we have to connect it to a different email address. I messaged Diane about this I have not heard back. The, the, the other thing that this brings up is we really need a. We need to start looking at setting up an email address that is particular to the group and that is accessible by multiple people or, you know, or provide an email list. For setting things up or something like that, like we set up a separate Google group or something to where we are then able to. Not be dependent on one individual for these types of things. Is it required to be an individual email address or can it be something that we can then manage with aliases. Well, you mean from the, from the Twitter side or do you mean from the side. From the Twitter side, I think it's 1 email address per account. I could be wrong. I don't know. I'm not a Twitter is not something that I'm that I use a lot. So, but yeah, I believe it's an it's attached to a particular email address. I don't think there's any way to delegate. But we can investigate that, but that's where we are right now. I mean, regardless of of that part, we do need to figure out the part of. Getting it attached from the email of the right going to be something like okay D at red hat. And then the red hat people forward that to whoever it really is. I don't know that that's a workable plan. To someone to If it's got a red hat.com, I'd imagine it's like most they won't allow anybody outside the organization to have any control or publish anything from that because that then comes back directly on to red hat. So I think if you do that, it would only be limited to Red Hat employees. We need to check that with Diane but most corporates have that sort of policy. I think. Oh, good. I think getting a Gmail account or a something like that that we can then have multiple people know the password of is probably the way to go or something like that, unless we've got some money and we can set up our own and pay for our own mail domain. Well, we can do aliases if we. So here's the thing. Can we need to check with Diane about this. Can we convince the red hat admins to put different MX records in the domain. Because if so, I don't know. I don't want to get over the heads of anyone here if you've not dealt with mail administration, but in essence, in a domain record, there are what are called MX records which point to mail servers. We if we can have them set the MX records to whatever we want, we can set it to someone's server. I'm have I run mail servers happy to volunteer them. We could use Google. We could use whatever the question is just can we get them to change the MX records because then we could get admins at okd.io, whatever at okd.io and do multiple aliases or whatever. It's just a question of, can we get them to change the admins? I'll put that on a to do to ask, because that ultimately will decide if we can get something at okd.io. Yeah, but I mean, in general, it's bad practice to use a human beings. Yes, for that sort of thing. Yes. Yes. 100%. So we'll put to do is that Diane about changing MX records. Okay, so that's the scoop with the Twitter and I really at this point, I want to get on with that election stuff of the of the chairs, but I want it to be transparent and I feel like I mean, I guess we can post it in the okd Facebook group. We could put it in, or in the OpenShift Facebook group. We can put it on the working group, Google group, and we can put it in the Slack. And I don't, no one is using the matrix account. No one's chatting in there and I don't know. I think we need to have a conversation. It exists. I've been in there, but we'll see. Yeah, I prefer us not to get into that because if someone writes, I'm not going to check. Right. Yeah. It's to spread out as it is. Okay, surveys. Well, I did get the survey from Drity. And so the link is there. We should asynchronously go over this over the between now and the next meeting. And I'll send a reminder out maybe next week on the working group email list. Any questions that you think we should add? Is it good enough? Whatever. Let's hammer this out and then send it out to our users in the various platforms that we just talked about. Does that sound like a plan? I mean, we've been sitting on this since November, so I'd like to get it out the door. You know, and ask questions about website stuff and everything like that if you want, Brian. And someone's got. Edit access. I think I do. Because I'm just saying just looking at it. I'll tell you what, if not, I'll just recreate it and give you all edit access. Because the 1st question definitely needs changing because it's saying what version are you using? And there's not 4, 9 or 4, 10 there. Let me see. Customized theme preview. Yeah, I do have edit access to it. And so I should be able to add collaborators as it is. So I will add you folks as collaborators. And. And we'll go from there. That's not like a plan. Yep. All right. Request for testers. Yeah, we need bare metal testers. We're getting more and more. It's amazing how much bare metal stuff is going on. That and CRC are really surprising me. So, but then by their metal, does that include. Like a virtual bare metal. I think so, I think it does have to be or is there anything specific we need this. Let me check with Sandro to see if they've got people. At the main meeting, we can ask Sandro because he should show up. We'll find out like where they are at and if they have people who want to. Test some stuff and write some stuff up for us. They've been kind of dormant lately. But maybe we can find out if they can volunteer some people to help with some documentation. Or at least circle the channel a little bit and answer questions when, when folks have questions that would be helpful. Let's see what else. Style updates. We all have style. We have, we have good style. What was that? That was for the website. Installing update. Yeah, so Brandon's cities pull request. And you should have noticed that the look and feel is slightly changed. And we've got a much brighter main page on the light, the dark mode hasn't changed an awful lot, but the light mode has got significantly better as more readable and better contrast. So, I'm not sure whether he's actually planning to do anymore, but that's, that's the work that he's done so far. And I thought it was important to get that release before we actually do any moves. Can we acknowledge his efforts somewhere on the site? Or, and I would say Twitter, but once, once we get that, but just be like, thanks. For the efforts to update our site, but like, I feel like we should give some acknowledgement because this has all been done sort of in the background. You know, and that was a great thing to volunteer some time to do. So. Yep. Awesome. So if you want to write something up, then, and then we'll just post that in various places, like a little two or three sentences or something. Okay. Yeah, I don't want to add too much to your task list though. So if you want. You can delegate to Bruce or something. And yeah, I mean, I'm totally get a Twitter or something. It's difficult to know where to put that. Yeah, I mean, what we can do is we, I mean, I know there was a blog on there that we haven't used since we actually moved over to MK docs. I don't know whether we want to kill it off or try and get it made active again. We could put something and maybe ask him to maybe ask Brandon just to put a few words about what he did and. That would be actually, I think. Yeah, that would be really cool actually and explain why and our focus accessibility and things like that. Yeah. Yeah. So, so that might be good way of doing that. Just pull a blog where we can sort of thank him and then put a paragraph from him. Can you head that up to get a paragraph? Okay. Yep, I can do that. And then the last one publishing update so when we publish and it does a spell check and a link check. And now the question is do we want to keep doing that or do we want to and the reason I ask is because things like the minutes Jamie he broke us with all the spell check. Oh, yeah. Yeah, I did notice that. Yes. And so the minute what I've done is I've just gone in and disabled spell checking on your minutes section so everything in that minute and everything below that is now removed from spell checker. And so it's really do we find that automation useful or a pain in the backside that we want to get rid of. It's always nice to have a site that's practically spelled and all the links are always working. But it means when someone wants to do a quick update, they can suddenly get stuck with someone sites broken or someone's taken a page down and it's not something they're interested in fixing but their update is now blocked because of it. Yeah, I don't have I don't yet have automation to actually go check to see have we got any broken links this week or anything like that but so it's really. I want the publishing to be as easy as possible to encourage more people to do it. So it's what people think is the right balance there. So we just put them as warnings and not block it or do we have to say what's important. I would say so here's the issue that came so here's an example of how nitpicky it is. The thing that was that was throwing the air was that we have in our attendance name. Affiliation close parentheses. Apparently the way that that is written causes an error in in the link checking. Because it's thinking that it's a parentheses for URL. And so we can't find for example University of Michigan as a link. But there's a way to turn off at the top of the page right like for the for an entire page. Yeah, there are sort of like the spell and there are various things you can put in so for example some of the pages. I've actually added page specific spellings that accept is everyone's email address and things like that it both with spelling on. So I think the link checking and the spelling. What's what's our straw poll vote here my vote would be to turn it on what Brian what do you think Bruce what do you think. Well okay so I mean I think spell check is a useful thing. Especially if it's flexible on UK versus Canadian versus American spelling, you know for color and, you know, honor and things like that. I've actually said it to say that we must be us in us. It did it did but I have said that in the majority of people are in the US I have said the end US is the accepted spelling for our site. Well I'm in Canada if that helps. I know it's one of these things where. Well I have a you in it. Are you saying you want to keep it on. Well, okay, so it seems like there, there, there should be. You know, some like it sounds like a bug in the spell checker. If something in parentheses has to be a URL. That's the link checker. And that's the link checker. Okay, but so a bug in the link checker then because. Well, no, it's actually the rules of lockdown. Yes. Okay. So, typically I was wrong in the most literal sense, right? I made it like, yeah, so maybe to escape the parentheses. Yeah, if you escape it, or if you put it in quotes, a block quote, it doesn't check what's in a block quote. But if you just have it as normal text, it actually breaks the rules of lockdown. That was the issue. Okay, so, well, that sounds like a learning issue. We can fix it the source. Well, it means that we have that I have to, you know, when I write the notes, for example, for this meeting. I need to do all of that and then make sure that I copy and paste with all of those things in there. It's fine. It's just, I'm wondering, you know, how much time do we want to spend on that? I mean, the other thing is I can do what I've just done. Disabled for a section. Yeah, right. And for the minutes, if we just want to say the minutes or whoever writes them up is what gets published. Yeah. Waltz and all, then that's okay. But I actually think if you've got a main section of prose, and it's just got lots of spelling mistakes in. It just makes the thing, no one cares about this. No one's actually cared enough to write it properly. Yeah. Yeah. I do like that you call it prose as if we would have some very articulate poetic descriptions of. Okay, you know, open shift in Kubernetes. Yeah, I mean, the poetry is different, of course. Exactly. Okay, so I guess we'll keep it on. I will be a little more mindful. And if we can maybe turn it off for now for meeting minutes, just because it is typing in minutes stuff. Okay. It is turned off for minutes now. Yeah. Okay, good. Cause when you're typing stuff in, it can be very. You're just trying to get it in, right? You know, and right. Technically, we, we really should have someone else taking the notes as opposed to also leading the meeting. But we'll get there when we get more people involved. Okay, so is there anything else that we need to cover to do is are to check with Diane about changing the next record. That's me. And then Brian, you're going to get a blurb on the website style updates that we can share out to give some credit and thank you. Yeah. All right. Anything else we need to talk about right now before we disband. Sounds good. Do we have a timetable for when we want to move over to the get, then you get repo. I wanted to have that conversation today, but I was kind of hoping that Diane would be here or someone else other than just the three of us. I don't know. I mean, do we want to have that conversation now? Well, we are going to have to line up, for example, the keepers of the, the, and the NS records. Yeah, things like that. We are going to have to do things like that. I don't want to wait because I feel like there's that list is actually pretty big. And I don't want to, I don't want to hand it off to Diane until I know that she's going to have the time to do it. I mean, what might be useful is just to actually for the next meeting, have a plan that we can actually just put up. And if you want to do it in Slack, or if you want to actually just curate that in a discussion. That's what we talked about before. Yeah. Yeah. Just so we actually have the list of when we actually decide to sort of go for it. These are all the things that we need to consider and line up. So we actually have that discussion and say, okay, we're going to do this in two weeks time. And everyone lined up for two weeks time. So do we want it in the OKD IO discussions or the OKD discussions? Well, everything is in the OKD discussions. I don't think we're actually not using. Someone put in February 15th. What should be the purpose and format of the guides? And I think that was the folks doing the guide stuff like Dan Axelrod and Christian and you participated in it apparently. Okay. Yeah. Well, it's up to you. What do you think? I'd stick to the open shift one because that's what everyone's using. You're rather than the open shift different about CS. Yeah. Yeah. Okay. So. Okay. Do you want discussions on creating one now? Okay. Oh, the other thing I wanted to say is if you have to look at the issues. I think we've got three or four issues in the open shift.io repo. I think most of them are old and we can probably close. There are things like the charter. And I just I was just trying to tidy everything up before we actually do the move. Make sure that we don't use anything. So I was just trying to shut them down and I think. I mean, we're already crafting things like the charter outstanding actions, which I think is one of the issues. I'm just thinking. Can we actually close off issues and shut down things and. Okay. So hold on. I'm just finishing up this discussion. Okay. Plan for repository transition. New discussion is created. It's 1206. Discussion 1206 minutes. And it's there. And to do is I'll say this is for everyone is to. Work on the transition transition. All of us. Okay, great. All right, so in terms of those that you want to close Brian, what are you thinking. And just. If you look at what's outstanding is there anything that. That we're actually going to do off. Can we actually close them for being stale. I'm just getting the list of mail. I think we do need to have a conversation about the matrix. Situation update group charter. I think we're good. We can close that. Yeah, I think security contacts. So I. We got a hold on that I sent an email to. Um, Mohammed. Who had volunteered to. Uh, to do security stuff and haven't heard back. So let me reach out. It's like we connected on. And then I said, well, I'll send you an email since we're in different time zones. And then I haven't heard back from them. Um, but I certainly laid out what we would need help with. So, I mean, for me, I think we should close this matrix one off. And put it in discussions because I think we need to come to a consensus in the main group. Yeah, as to we've set this up. And nobody seems to be that keen on actually engaging in using it. I know Neil's Neil's desperately trying wants us to use it, but. Yeah, but he's not saying anything or posting anything or. No, but so I don't think that's something that. We're not going to add it to the documentation unless there's a consensus that we're going to use it. People are going to check it support it and. So I would like, I would say, let's close this and leave it to a discussion group. That's fine. Because it's just going to sit there and do nothing. The charter will happen and then obviously this security contact. Well, the security contacted we decide to just in terms of the contact. Tell you what, let's keep that open because that might be affected by the MX record discussion. Because if we can get like security at okd.io, that would be fantastic. Yeah, but I think there was also the issue about, can we do anything about it? So we're actually does raise the security concern. Because at the end of the day, it's OCP source code that would need to be altered. So there are, well, but some of it is Fedora. Some of it is Fedora. Some of it like there are some unique bits. That are okd specific in it so we can't treat it completely like it's like it's just OCP rebranded because there are actually some unique bits. For example, we did the change to see groups V2. Before OCP did. There's also a couple of system D units that are unique. So there are some things that are. But when you say they're unique. If they're not in OCP, then they're in Fedora repo. Is there anything that we've written is okd that could have a security exposure. That wouldn't be covered by because all we do is pass it off to Fedora or to OCP. I think we need to do an analysis. The appropriate path is to actually do an analysis of that and see what type of artifacts are. Okd specific and there are some I know that there are some things. In a node that are okd specific that aren't just branding so. You know, and particularly once we get into the community, the okd community operators catalog, if there's a security issue with the catalog configuration. But let's actually look at that. Ok, is there anything else then. So is there to do out of that. I think we'll move that we're going to move the matrix discussion and the security discussion to the main group and see we're into the main group and see. Yeah, I'm just going through all the repose. I'm just trying to shut down anything that can be shut down. So when we do the move, everything's clean and we don't have to. Worry about taking issues with this because I think code goes across quite easily with a. A sort of a fork. Where we're going to leave all the issues and discussions behind. I think. I think so. Yeah. Ok, cool. We'll see nothing else. I'm going to bid everyone do. And stop the recording and I'll see you all at the, I'll see you all online as we hammer out the transition plan asynchronously. Yep, sure. I send out a reminder on that. Thank you. Thank you. Bye.