 Let's get started then. So this is the OKD Working Group Documentation Subgroup meeting for February 22nd of 2022. We've solidified our agenda pretty much. So let's jump right into it. Code of conduct. It's ready to publish. I think we just wanted to have a contact email. And so I think you provided that, Diane, right, to Brian? Yep. So Brian, can you make a pull request with the content and we can merge it? Or what do you have to do to get that up there? I can do it. I'm just trying to work out where should it go? Because... There was a... There is... Looks like there has been a pull request made to the docs, which is 37383 on the OpenShift docs. There's a link in the... If you go to the agenda, there's a link to that issue. If you follow that, follow the trail. And it looks like Michael Burke did that. So I wasn't sure where we wanted it to be published, because it looks like this is going to the product docs, the docs.okd.io site. So I think that was just... He did that as he was working on it so that he could create an issue. So I think this wants to go to the main website. So... Yeah, where it says to do. Under code of contact on the okd.io site? Yeah, yeah. What I didn't know was, was I pointing into the docs or am I publishing it on the okd? No, publish it on the site. Make it a nice looking page. I think that's the explanation. That is easy to do and I'm just checking have I got the very latest version then. And I think that my thought is we want it to look as nice. So anything that we can do in web page format, I say we do it unless it's like something that's technical where it makes sense to be, you know, just pointing to a get document or something like that, just because I think it looks nicer and more together. Okay, where is the very latest version of it? I think that is it because I don't think anyone made any changes. Nobody requested any change. It was just the email. Yeah, so just adding Diane's email to it. That's all you need to do. Okay, so I shall pull it out of the docs and add it to our site. Yeah, I can do that. Yeah, if you do, if you do that, I don't, I think, and you can merge a pull request. So yeah, we had one person pointed out to me on Twitter who was actually a redheader in Australia. So I wanted to reach out to her and have a conversation and then try and pull her into docs. So there you go, Debbie, if you're watching this, this is why. All right, well, let's not work during, let's, Brian, go ahead and keep working. Let's move on to the next thing. So operator catalog, let's start filling in details in Christian's issue for any red hat operators we may be interested in seeing. You know, I think if we let them know what we're looking for, then we might end up seeing it, right? I'm optimistic. So nothing new on that one. I'm reworking the base repository. So let's just start making PRs. Brian, you and I can just start doing PRs because it sounds like we've that's what Vadim wants. So we'll just start making PRs for what we're going to move. Okay. What is a timeline to move? I don't know. We didn't really, we didn't really say anything about a timeline to get that torn down, basically. Well, no, I'm just thinking it's a best to do it there where we've got to effectively bug Vadim, or if we're going to set up the new org imminently. Is that something we could just do? Well, he wants to do PRs on it because he wants, what's Clayton Coleman? That's Clayton Coleman to look at stuff before we make any changes in terms of that. So even if it's sort of duplicate work, yeah, let's put in PRs on the OKD repo for what we want to change there. Well, I think effectively what we agreed is we're going to remove everything from there and all the new content is going to go into okd.io. So any technical document we want to persist, we're not going to actually change it there. We're going to delete it there and add it to the okd.io. Because the agreement was that that should not contain any documentation. Right, but that stuff on that. Right, but on the stuff on that readme anything that we want to change on that readme my senses Vadim wants us to like. You know, because we do want to clean up the readme, right? I think that's what we were saying is we do want to clean that up and make it a little more concise readme, right? Yeah, but all that readme is going to do is point to the okd. Any useful information from that readme is going to get removed and put into the okd. And I understand, but I think Vadim wants to sign off on that and he wants Clayton to sign off on that. Clayton was the original creator of the repo bazillion years ago. And I think that's out of just out of respect, they want it to make sure that folks are aware of like what we're doing sound. Okay, so you don't know what I mean, like, yeah, we're going to remove links and just copy. Yeah, but I guess what I'm trying to say wouldn't it be better for him to sign off on the new stuff that we're going to add to okd.io. But we would have to add him as a user to that repo. Yeah, he's not signing off on the content. He's signing off on the move of the location so we can continue to create content in the old location until we get him until Vadim corners him and gets permission to move the location. So Clayton isn't pretty much ever signing off on what we do in terms of technical documentation. He's just the Uber architect for the repo for all of OpenShift. So it's a slightly different variation on a theme of approvals. But yeah, and then that way we're covering ourselves for having made the move that it doesn't affect any CI CD or engineering build processes that we might have not heard about. But I think Vadim has us covered. So I'm pretty sure we're just going to be a checkbox, but it's hard to corner Clayton, trust me. Okay, okay. It does seem, you know, it's. Sorry, I just want to make sure I understand what we're doing. Are we going to sort of triage the content in the OKD.io in terms of how we want it to look in any location and get agreement in the old location? I think so because why copy stuff over. To me it doesn't make sense to copy everything over because ultimately, I think only a fraction of that is going to be need to be moved over maybe. Yeah, I agree, but I actually think it's going to be split up. I think there's that read me covers a multitude of topics. So as we move it over, we want to actually expand it and also separate it into areas of concern almost. So the idea of how the build is structured is different to one of the other sections which is different to another section. So we wouldn't be moving it over as a as a single document as a single reading document that was going to get split up across multiple technical pages and then expanded as we learn more and we understand where we're going. Yeah, Brian. Well, I kind of view this as your, your thing. So if you if you if you want to start on that, then, you know, sorry, do you want to come in while we're having a discussion. Yeah, no, what I was going to say is. It's easier to split things up than to add things. So it would probably be a good organization to first break it into separate docs. Each single themed. And then, you know, we can work on getting them expanded. Yeah, rather than expanding and then breaking afterwards. Yeah, I agree. I agree. The other thing that will need to be done is that we need to start adding folks over to the okd project which actually I need to invite you. So I'll take that as a task is start inviting you to inviting folks to the okd project repo. So that they actually have access because right now I think it's just Vadim, Christian, myself and Timothy. So let's let me get more people at it and there's that we can actually start this process. And anything else about this moving forward. So I guess just start doing your magic Brian and Bruce and everybody. I guess the other thing is to actually that I don't think we captured here that to close out the community repo. In the old location where there's those five documents and merge them into the okd.io. That was the other thing that we discussed I think in there. Yeah, I think if you want to if you want to go ahead and do it. Yeah. Yeah, I can do that. You're cool with that moving that stuff out of the community repo and discontinuing it. Okay, great. All right, let's add that for a Brian, you're going to have a bunch of tasks here. I know. So. Docs. Brian. Yeah, I began some working on the house so I've been a bit sort of distracted the last few couple of weeks so that should all be finished next week so I'll be back on. Exactly. You did lots of works. So, and you're, you're pretty much the, the web lead here. So when you get you a title like that. Okay, do you web lead or something? Yeah. Whatever helps you in your career. We'll call it that. Yeah, exactly. No more web masters. So, yeah. And if we want to stylize, I still I keep saying this I still have Brandon from marketing matters on contract if we want to. Brian work with him to make it prettier or whatever. Yeah, as I said, I am I am no UX designer. So any, I mean, we took on board and got the accessibility contrast past. But if he has any ideas. Would you be, would you be willing to meet with him and I. Okay, so let me, let me see. I usually have a call with him every Thursday. I think 11pm, 11am my time. So let me see if I can, does that, that specific time so. Oh, now that's a bit late for me. Where were you based again. I'm in the UK so 8 hours in front. Let me see if I can find an earlier time this week and because I have a budget that I need to use up and he's the he's the object of it so. Okay. Let's get that code of conduct and then make everything pretty. Get some SEO and tons of people come into the site. Okay, so next up is security. We just need to add that same email address, I guess. For the security liaison request and then that's ready to publish brand. You can do that as a. Log post maybe and then we'll tweet out the blog post. That sound like the right path forward for that. Because there's a little bit more than a fit in a tweet, so. I thought we had a volunteer for that. Oh, that's right. Someone did volunteer that someone said. Mohammed Mohammed. That's right. Mohammed. Yeah. Okay. So that we don't need to do that anymore. That's right. Well, as you can tell, I've been pushing a project to production the past couple of weeks and so I have not been. Well, I think what we need to do is that we need to actually put that on action on the website that we do have this function and maybe get Mohammed. To actually write this as a page where to explain what it's about and and how to raise security issues or how to get security information. So I think that will be a useful page on the site. And maybe we can ask Mohammed to actually do that as his first official task. So it's easier to get people jobs when they're not here, isn't it? Yes. Well, he sent me a LinkedIn request and I completely spaced it I accepted that and I think that's the only way to contact him. I'll have to see if he's on Slack or where he is. Okay, so get it right up from Mohammed issues in the repo. Okay, there this week, sorry. Sorry, just one thing. Christians link to the operators. Do we have a link to that issue? And also, should we be creating another subgroup or another section in the site just so we can actually get through the community? So we want to sort of where we're going to coordinate this so people can't attend these meetings but want to see what's going on. Should we create a page on the site where we're just actually doing the work and just let people do it in the discussion forum? I think in the discussion forum is where it's more appropriate and we can track it better. And yeah, there will be a little movement on the operator stuff shortly. It's getting the structure is being put in place but nobody wants to get anybody's hopes up. So we're being a little slow about the dribble until some operators actually get put in the repo. But it is moving forward slowly. Yeah, so I think any discussion about it or requests around it. Keep it, if you don't mind, keep it in discussions for now. Okay. Well, I actually think it's an issue, isn't it? It's an issue, yeah. Let me find it here. Operating list. Yeah, there it is. Okay. Four, five, six, yeah. We are going through this agenda. I'm having some connectivity issues this morning. So I apologize if I cut out. That's all good. No pull requests. Nope. Are we good to move on, Brian? Yep. Okay. Contact email addresses we sort of settled on just using the one for now. And then we'll have to figure something out. I think that ultimately that's not sustainable. No, it's not, but I think that's, that's all we can do for right for right now. And I think we will end up creating our own mail server for OKD.io. Somewhere. It should, should go to someone. There should be two of us theoretically on that. In case I get hit by a bus and don't get, don't answer it promptly. When the lottery and go off in the lottery. All right. I like the lottery better. Yeah. Okay. When I win the lottery and off to the Caribbean. Where my boss is right now surfing. Of mine. So yeah, so I would like to have a server set up, but I for now just have it come to me. And then I will just deal with it as they come in. I looked to just so people know. Fedora has a good process for this. The Ansible folks. It's a case by case thing and Robin Bergeron, who is the community lead for that, for that project. It goes to her and she parcels it out as, as she sees fit. But they do have their own email address because they were an acquisition and they were Ansible.com before. So they didn't have that problem. That's the short story. Okay. Let's. Now, let's see go over the task list. Okay. There's there's one issue that Neil raised three weeks ago. In the okay D. Issues. And this is about this matrix as a new avenue for communication. Oh, right. So document new main chat avenue as the matrix. Has anybody managed to sign up there because I've tried a couple of times and I keep getting my email domain is not authorized to join this server. I have not yet. Let's put that as a task for everyone to try to join. But if it's that hard, I'm a little concerned about it. Yeah. Yeah, I haven't been successful yet. Yeah, I went to some generic fedora. Right. So, I guess I could count as unsuccessful. Yeah. But are we like, in a way, like, I've sort of been aware of matrix for a while because the. You know, back back when. CentOS. Went to stream. There was a big guffuffle in the community and a bunch of people started up their own new version and they were using matrix. And that was sort of the first I heard about it, but in a way it sounds like fragmentation. I thought we're trying to we're sort of trying to move. Yeah, from fragmented communications. Yeah, I think we have to have a good group of us who are actually actively using it before we turn turn our discussion away from slack. Yeah, I mean, the argument Neil made was that this is where all the fedora folks hang out. And as for Dora is the underlying. OS, if you want to pull them into okay D, this is the way that we're going to do it. But I agree with you, Bruce. I've been trying to shut down. No, all the other ways and we should have one way that doesn't require you to create an account and doesn't require to jump through hoops and get a discussion is the place that I think we should send everybody. Yeah, at least it's registered. And so we have it if we decide to use it. Let's get in and what I said before, I think holds. Like, let's try to get in and if you can't get in, then I think that's a problem. Let's let some other folks try. And maybe there's something we're missing, you know, but if it's a problem, then we don't need to worry about it. We haven't made it public yet. So let's not make it public yet until. But I think the other thing is, if we do make it public, we need some commitment from people to monitor it and respond. So it's not a black hole of. No, no one ever gets response because that then just generates the bad behavior of cross posting everywhere. Which again, we're trying to get rid of where everybody sort of feels have to go six places to get an answer. Right. We did manage to get the. Open shift dash dev. That channel closed last week. I saw that. Yeah. And so, and no, and nobody complained. Yeah. And ultimately we get everyone using or many people using discussions because so much flies by in the slack channel. Yeah. And, and there's in the questions are all over the place and stuff like that. It would really be nice to have some organization. And some historical stuff where we can point people to other discussions. Sure. All right. So task items are. What did I forget? Let's see here. We have. Find out who is behind the LinkedIn. That's you, Diane. So when you get a chance. Oh, behind the okay D LinkedIn. Is there an okay. Oh, I didn't buy. I think you were not at the last docs meeting. I think I got. Yeah. I think I got volunteers. I did not see that one. Yes. So we need to find out who's behind the LinkedIn. Call out for YouTube content. I will write something up and they am. We should be able to do that. Yeah, we have a thing called bit warden, which I have to install on my machine to put in the software for it. And I believe you can use it. Vadim and I, and you will be the three. And then I got to do this game for a whole bunch of stuff. So bit warden is the. Yeah. Yeah. Yeah. Yeah. We have a thing called bit warden, which I have to install on my machine to put in the software for it. And I believe you can use it. I got to do this game for a whole bunch of stuff. So bit warden is the key here. So. Okay. And then I need to talk to you about SEO stuff in terms of optimizations for getting, you know, traction in that regard. Yeah, I think that just on that note, the conversation that Brett that Brandon that we have with Brandon about revamping the site he's also very good at getting SEO. Awareness on, on websites like little tags that you have to put on each of the pages and things like that. So maybe we can combine the upgrade the look and feel with some SEO stuff, Brian, when we have the conversation with Brandon. I want to, I want him to pick it. I need an excuse to pay him out. And he's very. Yeah, find contact person slash address for the CSE, which is the. We did that. Yeah, it's me and then we're going to use I Brian I sent you this string I think I believe to use the mail to or did I just send it to James. Yes, that went to slack. Yes. Yes. And what was what's the one above that one above that. Create list of links to our to our book to provide links into community documentation. Is that the old that we have that's the old one. Are you, I think you're on the old. Oh, am I a weekend. I'm a I'm a weekend. Okay, sorry. Yeah. Yeah, that one's done. Yeah. Let's see at machine with repo discussion to the main meeting. I will do that for the next main meeting. Move community docs out of the community repo Brian, add users to project repo Jamie and try registering with matrix everybody. Right. Did I miss anything. Yeah, I need to put the code of conduct for me. Oh yeah, right. Do you have the link to the okay D LinkedIn thing that you've somebody want wanted me to do I'm going on LinkedIn and not seeing anything that says okay D so if you have the link to that. Let me see here. Someone linked it to us in the last meeting and I for some reason we didn't. I'm just searching. Not find it anything so. Oh yeah, here we go. I got it threat Diane doing it just got them to take it. Okay, good. Thanks. London England apparently we are based in London. Yeah, I'm having. And we have 3 employees Milan Chavda. LinkedIn member. And SR. All right, I'm, I'm having network issues. Oh, there it is. It just popped up. Oh, that's interesting. All right. Well, let us know what the next meeting. All right folks, I'll see you at the main meeting or in 2 weeks at the next meeting. Okay. Bye.