 All right, welcome to the OKD Working Group DOCS subgroup, and we're going to jump right into it. We're going to try something different instead of doing introductions. I would encourage folks to look at the meeting notes, and there you will see the people who have attended the meeting, and their affiliation. And for any new folks that are here, we'll give you a chance to introduce yourself. If there's anyone new, nope, no one new here. So let's jump right into the crux of the biscuit. Current projects, the guide transition, what's the status? So I fixed up the PR that I had there. I took out the references to OpenShift and changed them to OKD, and also put a note in the read me about how to add more guides. I think we're at MVP status for this thing. If we were ready to merge it before, it's probably enough of a baseline that we could merge it now, and at least people will know how to add more things, and I think it's probably tuned up as much as we want for just an initial outlook. And what I did today, I broke GitHub. I'm blaming all of GitHub going to, I couldn't add an issue on something today, and apparently the webhooks are down. So I will merge it, I'll merge it. I think you can still merge. I just, for some reason, there's certain little things that aren't working like add an issue. So I will merge it after this call as soon as it comes back to life, and send out a little note about it. Thanks. Whatever it is, it's intermittent, because I was having issues as well, and on my third try it went through, so. Yeah, I just like claiming to have broken GitHub. I'm going to let my team members who are having problems, I'm going to let them know, like, come talk to you, Diane. Well, yeah, I know how to break everything. So it's a useful skill. There you go. Putting it back together, not so much. Breaking, yes. Anyways. So for the charter update, I started to make my first round of edits to the charter. One of the things I noticed is that in the charter, it actually says that there will be seven days for voting on issues and things like that. We've done none of that stuff in terms of process. How do folks feel about that? Should the charter be changed? Or is it just that we've not made any fundamental changes that require a vote? What are folks thinking about that? Well, I have an opinion about that. I think there's some clarification that should go on about what kinds of issues we would vote on, because things like adding the guides or changing the OKD.io website don't really require any kind of major voting, just consensus, in my humble opinion. But if and when we wanted to say fork OKD or ARM, like scenario, something out there or to make sure that it worked well on some other cloud platform. And that, I think, would then be required. So like if it was a code-based change, and I don't know what you call that level distinction there, but that's where I think the vote would have to come. Because we have conversations where we're like, yeah, it's not doing this and we need it to support that. And we've heard, I don't want to call Neal out, but I will. Neal Gampa often says things like Fedora is going this way and you're going that way. So I think some clarify, and I don't know what off the top of my head, I can't think of a suggestion, but something that is documentation changes, marketing or brand awareness changes, those kinds of things don't require just consensus and informing the group. And things that were, yeah, consensus is good. And other things like a major fork or... So technical and process changes would probably require a vote. Does that seem... That sounds like... I also think it's a community maturity issue. Most of the people that are active and would want to have a say, turn up to the meetings. I don't think from my understanding that we have a large population of interested users that aren't really being active in the meetings. So I would see a statement like that is more applicable where you have a much larger community and it's impractical for everybody to join into meetings and contribute to meetings because it's too big. It's one of the reasons I ask for attendance at all the meetings and to people put it in is because when we get to that maturity level is that attendance at a set number of meetings and participation is what might eventually get you voting rights when we go to a model that is voting on, like widget changes on the website kind of thing. But I think right now if we did it, we decided, and I'm going to use forking for ARM as my theoretical thing, if we made a move to do something like that to create an OKD light for ARM or whatever we needed to do. Trust me, that entire working group mailing list would wake up really quickly and want to say in it. So and we would have a very interesting first meeting or second meeting after we put it out there as an issue, I think. It's always surprises me who's actually paying attention. And yeah, so that's I think for the smaller but it is it's totally a maturity. We haven't hit the tipping point and we also haven't requested any major changes to the code base. And I think the other thing is then we need a process on how we announce a vote and how we get votes, people's votes in, is putting it in the meeting in the HackMD. Is that good enough or do we need a more formal process of these are the areas that we're requesting people to vote on? So I think the charter. Oh, go ahead. I was. But just to say it is in the charter that we posted on the Google group mailing list. So is that good enough would be a question, I guess. Yeah, so there is a process that I like and it's like what the CNCF TOC uses when they're calling for a vote. They use the mailing list and they link to an issue on for commentary. So there's a there's a nice little standard and maybe we can steal something from the TOC's governance. It seems to work good and it captures the commentary and keeps it to be a semi-rational and civil discussion. So and and it's trackable this history. So by using the issues list as well as the mailing list, it's very public. And that's what Fedora Cora West Group does as well. So, yeah, we could steal from them. I'm happy to help you steal. All right. OK, I'll give a stab at creating some clarification on the different types. So by the next docs meeting, I'll have something and folks can take a look at it in terms of like delineations of what is voteable versus what is just non-voteable like words that accurately describe it. Something like process, technical and then the other thing being like non-voteable would be like cosmetic or documentation or something that I guess something along those lines. OK, so updates to the OKD banner. So I made a change to the banner per our discussion from two weeks ago and what came out of the last main group meeting last week, which is I and this is just in the repo. It hasn't been built. Diana proved the merge, but it hasn't actually been built into the website yet. But dropping the recipes because the recipes were I mean, it looks kind of cheesy and it's because there's only two recipes there that have been there for like a year. And then, you know, and plus recipes and guides seem to be conflicting. You know what I mean? Like people can do guides for things that are recipes, right? Same ends and then community goes directly to the discussion. The OKD repo discussion. So let me pull up that. Let's see. Now, just Jamie, I just know that that guides entry will go away when my PR is mirrored. It'll all be just one installation page. So we won't have kind of a doubling of that information in the menu, at least, right? All right. I'm going over there now to see if I can merge it so we can pull requests. Just want to wait and down there is another thing that has to happen. In parallel with that is we need to update the slack because you added the direction to go to the mailing list, the Google group for support at the top of the slack channels. So we need to we need to point that to the discussion groups as well now. OK. Let me put that in the notes that we have that is a thing to do. This is a change Google group. Text and I'm merging you, Elmico. Let's see if this actually works. It'll take a few minutes. Yeah, hold on a second. I'm just I'm just wondering if there's a bug here. OK. I think there I think there is a bug. I just need to I need to push one more update. I will not squash and merge them. I love squashing and merging other people stuff. When it doesn't break the Internet. So what else do we need to do to help with that delineation of resources? There was some discussion during the main meeting of this. Brian, you had some ideas as well. What what are actionable things that we can assign to folks to do the separation more clearly? I actually think it's it's more to do with documentation. So when people arrive at the community, they've got a landing site and there's a clear. And that team was very clear. We didn't use the word support. So if you want to connect with other community members to help to ask for help resolving issues. And go here. And we should have an etiquette guide, I think where we just lay out how you ask for help. So the information you should include like what platform you're on. If you're following a set of instructions, put the link there. Any error messages, how to get the must the help bundle, the log bundle together. We should just put little things like that in. But that's very, very much about community member to community member to resolve issues. And then we should have another group. If you want to become involved, whether we call it the working in the working group or the steering committee or however you want to word it. We have a separate section. And then it talks about the process of how we meet where the minute meetings are, how you can raise a question, how we track issues and work in progress. So it's very clear. This is where community members ask for help. This is where community members come who want to contribute and it's very clearly documented. And it means that if somebody wants to join in, they don't feel like, am I doing this in the right place? Am I doing this right? Because that was my first. The first time you put something somewhere is like, I'm just trying to work out what everyone else is doing and hopefully doing the right thing without getting the hate mail from community says you often do if you've got it wrong. So it's getting that. So I noticed that links can be put in the left side of the. GitHub discussion sections. So if we if we go to. To share your screen. Don't mind and show us what you're looking at. I will let me let me turn off notifications that you don't see things like. The baby is awake and things like that. Hold on one sec. The baby is one now. We are assuming because on the. Yes, the baby turned one a week and a half ago. Yes. Okay. And he is awesome. Okay, so sharing my screen. Okay, so if we look. Here down here apparently you can add links down there because it looks like Vadim added okd.io. Would it be good to have a link here to how to ask questions. Or I can you can you. In discussion items. I don't know if those can be pinned or not by the repo owners. Oh, here's what's contributing go to. Okay, here we go. So. We could have whoever has right access over this repo Vadim or whoever put a how to ask questions under helpful resources. Does that make sense. Yeah, because right now we're linking. We're going to change things so that community goes or I think we're going to change things so that community goes to this discussions page. And then folks could have links down here. And then when they go to new discussion, there could be under helpful resources like. How to ask questions or something like that. Again, what's the use of the various classifications within the discussion is you can sort of classify what what are you asking is it a general isn't an idea. Is it a question is a. Go and tell so again we can. We can help people sort of. Be more direct in terms of, as you say, this is how you ask a question. Yeah, and isn't there a. Isn't there like default for each category. Can't you do like a. Can't you modify this. To actually have a template. I believe you can. You can write. So why don't we come up with templates for each of those categories. That fill it in and so. For Q and a, for example, when folks select that the text would be something like, here's the best way to ask a question. Or for a ideas, here's the best way to, you know, that's a Brian, does that sort of address what where you're headed. Like here. Yeah, if it works. I'm not that familiar with discussions. I know it's Peter. I haven't really got that deep with him yet. So. And yeah, that would work. But also, I think back on OCD.io just have a page where we just sort of lay it out. So if people are being sort of anti social, we've got somewhere to post them to where we sort of say. And these are the rules. Please follow them. Sure. Yeah. You know, I know about a month ago when we were saying, where do we point where do we sort of post the sort of the guidelines. It's those guidelines. Yeah. Yeah. And I think that that's something that the CNCF is doing now I noticed on all of their streams. The meetings and thereby streamed meetings. They're actually talking about at the very beginning, their code of conduct and saying, please don't post anything in the chats that violates go to conduct, et cetera. And we have and this and I would say this is one thing that we have a failing at red hat with our projects is we don't have a unified code of conduct template that we can use on projects. I haven't seen one El Mico recently. I'm in the last time I asked legal for something I got some pushback of on that because one of the issues we have is like, if you put something like that in place is what I was heard. And I'll go back to the the well again, you need to have a process or dealing with it, and people willing to deal with, you know, the, you know, reaching out and talking to people and all of that and I don't think we have. And I'll ask Deb Bryant and the Ospo team, again, what the, and that was about a year or a year and a half ago that I have. Now, would that be some with the day and would that be something the chairs would do. Would it be part of the. Well, it's the chairs. It's one of those weird, weird edge cases, because okay D is a red hat prop hosted project. And not a CNCF project like Kubernetes or something like that. I normally what I do, especially when I host events that are co-located with CNCF, I just put in a link that we follow the code of conduct for CNCF because we're co-located with their events. So that covers my events pretty much all the time because then because I'm on their premise and using their facilities and stuff. So, yeah, it's, it's something Mike that that we need, we need to figure out. They may in the year and a half since the last time I belly ached about it, maybe they've got something figured out that we can use. And I have to take a look at Fedora CoroS team is usually up to snuff on all of those things. So let me take a look at that. And Mike, maybe I'll rope you into that too as the other red hat around this call to see if we can find a good example of an existing red hat sponsored project. Because if you look at the bottom of the OKD page, it's got a little bit of a footer around red hat. So it's, yeah, welcome to my world, Brian. A little bit inside baseball here is like, yeah, when you look at the red hat open source communities, like in a lot of cases we are participating in communities that are either have their own foundation or they have their own community infrastructure. And OKD just happens to be one of the projects that we host. So, yeah, I mean, I totally echo everything Diane saying it's it's a little bit of a weird place inside red hat. I think even Fedora CoroS that group comes under the Fedora umbrella, which solved this problem for themselves a long time ago. And we've never hit the tipping point of enough math mass or to warrant going full Fedora on everybody though I'm about ready to do so. That's an interesting that's an interesting notion, Diane, especially when you think about the release and CI mechanics that we've been talking about in the OKD community. It's like in some ways that would be freed up by if OKD became a completely community on project. You know, then it's like it starts to become a much different story about like where do we do release mechanics where do we do CI and stuff like that. Yeah, and yeah, trust me, I've been thinking about it a lot like because and I and Jamie and I were chatting earlier. I just ran into some folks from Brazil who are hosting OKD at South Hollow University and they have a beautiful cloud that they use the UI and the interactions are just amazing. And I would love to see a hosted OKD somewhere, even if it was a test environment for us to use and as a playground. But that might be my friends. Have you been talking with Marcel at all? Sorry to take this in a completely different direction, but like, I've had some discussions internally recently with like Marcel Hill and Amelia and Machi about like the operate first effort and how we can reach out to the OKD community. As having a public cloud that we could do that kind of work on. So I think there's a lot of talk happening about this. Yeah, and we have. And the other reason I think we have a big planning meeting coming up for the with under Stephanie cheer us as groups that I've been bringing on bringing it up again. That, you know, it is if they want us to do the testing of the edge cases for cloud deployments, which is one of the value propositions for having an open source thing is that they get all this feedback from things that we can't resource the hosting for. Then we need some resources to do the testing. We can't. So anyways, I digress, but just to say the code of conduct thing has always been one of those things that we need to we need to I'll hit them up again and we'll see what we can do with that. It's the same, you know, the same issue with getting the. We'll get to it later, but the inclusive language update. I'll reach out to the powers that be, which are my will and Jerry, who are my webmasters for OKD dot IO and figure out what the impact is. To get that structure and they will do it will is great Jerry's just been on vacation Brian just so you know, in the Czech Republic, they get more vacation time than we do in North America. So let's move on now to anything else that we need to do. So Diane's going to look into working group guidelines and conflict resolution. Anything else that we can do to for towards the separation of the working group and users. Anything else. All right, well, let's let's leave it where it is because things might become a little bit clearer. Once El Mico gets that last bug fixed and that's merged in and the new website stuff is rolled out and then we can look at the front page and the various other pages and Brian, you have a lot of input. And I want to make sure that we go through that list again and make sure we've covered everything in the near future. The next thing I wanted to do is go through the read me and then it. So, and this sort of factors into the install thing a lot of people have commented that the read me seems to be like every single possible idea about OKD and it's really problematic. Do folks share that I have that opinion Brian I know you voice some concern about it. Anyone else have a sense about the read me being overloaded a little bit. I guess the other thing is what is the read me for and what is OKD.io for because we have content in the repo and we've got content on OKD.io. And there's some overlap and there's some unique content in both. Yeah, and some of it is. Oh, good. Yeah, and it is just a little bit like because I mean you've got a guide section in there. And we're going to put a guide section on OKD.io. And there's information in here about doing install there's an install section on the. So there just seems to be a lot of overlap and. I just think some clarity what should be in here versus what should be on OKD.io and let's let's get some. Some sort of uniformity and so this let me give some history on the guides part what happened is is the guides got created here then. They got cloned by me for preparation for an event then they got cloned by Mike to incorporate into the OKD.io website. The guides will eventually go away because all of that now has been superseded by what is in Mike's repo. So the provenance is even a little sketchier than that because we started off some of the guides started off as an effort we were doing on OCP to document like what deployed platforms look like. So there's like kind of like a double history on some of these things. And I think what Jamie is saying about the guides going forward is kind of where we want to go, I guess. So OKD.io will have the guides. So this will be gone. Troubleshooting was the idea that we would show folks how to read log bundles and do other things and Vadim contributed that and he's also going to I think add some other things that we talked about. So if we look at this. There's the explanation. Then there's the working group stuff. Then there's getting started should how should we do this so that it links into the install stuff. Should there just be a link to here's the install stuff on OKD.io or how do we how do we separate this out so that it's not all in the read me and that we're not maintaining two sets of documentation or three. I was going to say should this not just be a go to OKD.io read me. And then everything else is in in the documentation site or is this going to be more documentation for the working group. Do we do it that way so this becomes that the repo is more about how you compile OKD or how you compile installer and put that sort of stuff in here and put the end user community on OKD.io. I just think that there needs to be. If I'm looking for X, I go here if I'm looking for why I go here. It's not if I'm looking for X, it could be here, here, here or here. And you know what's really going to blow your mind. Brian is there's actually a community repo. I just put it I know I've seen it like we're all over the place so. So should OKD.io be the main single shopping point. I mean, I think we need to change the underlying technology so that it becomes easy to add things there. And then that should become a single shopping point and working group members should be encouraged to contribute and add stuff there so that becomes the one point. Anything you want you should start by pointing them at OKD.io and then that should give them all the information or links off to other places. I think that I think that makes people's life a lot easier if there's a single place to point them and say OK, you can get to everywhere else from here. Yeah. Yeah. This place is actually organized and understandable. And you can, you know, if you need to troubleshoot, there's a place to go on that, etc, etc. And then that can point you off to other places. So are we suggesting then? Yeah, I agree Bruce should are we suggesting them then right here where it's where the getting started starts that we actually just cut it. And have like, like, okay, we just have this paragraph. And then it just says for details about installation and contributing and blah, blah, blah and the working group. Go to OKD.io and just all of this gets subsumed into the pages that we're creating off of OKD.io and just over time, move this over to OKD.io pages. Like over the next couple months. Yeah. Yeah. That would be my recommendation. Okay. So that's Brian and I that's I'm voting with Brian on that anyone else straw poll vote. Think about, what do you think? I think it makes sense. There are any downsides to this. I know there are some people that they just work off of repos and they're, you know, they're the hardcore repo folks. Right. And that's how they. Don't forget OKD.io is a repo in itself and that's what I say if we can change the technology. So it's just marked down documentation in that repo. It's effective exactly what you've got here. Right. It's a single place single source. I think that would mean if it was, yeah, if we switch the technology and it was more community updates driven as opposed to. Diane and Yammel and you know, and occasionally a community member who hacks through it and tells me that everything's out of date. Yeah, I would bunch if we can get the resources and people's brain trust working on moving it over to as Brian suggests. I liked what you did earlier the demo that you, you know, you did, I am totally game for that. And then all I got to do is get the, the web folks at red hat to repoint OKD.io to that place and everything. All the traffic will redirect. And that's much better, much healthier on everybody. All the, all the instructions on this like in this read me about like how to manipulate images and how to extract things and do installation like I don't think we want any of that here we want to we want people go into docs.okd.io if they're going to like. If you're going to do an installation go to the official docs don't like, you know, like what's here I have a feeling people are coming here and trying to do this like, you know, I saw some command up there for how to extract the tools from release image and whatnot. I feel like this is totally the wrong place to have people doing that stuff. I mean, at this point, you know, back then it made sense, but now it makes less sense. Yeah, right. Well, it sounds like we have a game plan then. And then the question is just. Brian, do you have your, your little demo up in front or can you pull it up to share with us. Yeah, I mean, if you want to go back to the discussions the links in there to just. Before you do that. I'd like to circle back. I put a link in the chat to the Ansible groups code of conduct, which to me work reads really nicely. And I would be happy to lift and shift that over to somewhere and and Brian and Michael Burke is on here. We can slide in like if I make an edited version of that for us into the to docs. As the Ansible folks have it. Into the official docs. Yeah, or just the OK D version, but can we add a page. I can certainly ask that. Yeah, if you could take a look at that. Yeah, because what my whole thing was, I mean, ask forgiveness later. If someone else at red hat on another red hat project has gotten the code of conduct reviewed by legal. Then and into their docs, then it would just always live there and we can point to that from wherever from OK D dot IO from in GitHub in the in the contributing documentation. And if it legal team that we needed to change it, we could just change it as part of the docs itself. I think Ansible probably has already gone through this once or twice. Just assaults there. So Michael, if you do need me to make an issue so that we follow up on it, or can you take that on. I would take it on. Yeah, Diane. I had a quick look at that and it looks pretty good. The only thing that stood out for me is the word offensive. Because these days, people get offended by anything and everything. And it's very hard to adjudicate. Yeah. So, but the. So, and then I guess then the secondary issue would be okay. So who decides. Yeah, well, I think I think that's that therein lies all of the conversations that I've had with red hat legal. And. Yeah. I don't have an answer for that. As the rest of the world has, but I do think we need a starting point to do that. And then we can. No, I'm fine for that. We probably want to review it in the group. Yeah. And I guess if it has to be with legal, then, you know, go for it. Yeah. I think that let's, let's see if we can, if Michael, if you can figure out a way to get work that into the docs. I think it won't go into the open shift docs, but we ought to be able to create a new page in our own docs. And if that happens, then, then we'll just go back and then we'll review it as a community. All right. So Brian, back to you. Thank you for letting me interrupt there. No worries. Okay, so this is actually a site that's based on MK docs, which is a static site generator. And based off Markdown, which uses the Python standard Markdown library. And so what I've done is I've just taken some of the content that's on there and I just played with it. And for the front page, I'm more or less copied exactly what's on the current site, but you'll notice the header and the footer is different. Unfortunately, there is some clash of CSS because the MK docs CSS and the bootstrap CSS that the front page, they use some of the same. Some of the same attributes. So it's not perfect. But what MK docs does is it does give you the ability to to customize things. So this was just a demonstration of how you could customize a page if you wanted it to look different. And but what you get along the top is you get your navigation. And again, you've got a lot of choice here we can actually have drop down menus here. So if you just say go to the, I think blog or community, you just go to one of those are good to go to community. Yeah, so you'll see that we've got a further sub menu now that pops up on the left so I can actually go into different sections within community. That could be a drop down under community or I could move the top menu totally to the left. So if you go on to say getting started, I think it's that section should work and go to CRC. Then what you get on the left on the right is then a table of content. So if I've got subheadings, I get an in page table of content. And this is all just generated from the markdown. So if I put like level two and level three headings within the content, they'll appear in the in document. So if you've got a big, a big page, you can actually navigate and they're all linkable. So you can actually copy the link to a section. And the other thing you've got is you've got a search bar with just off the there and that's the type. So if you type something like vSphere, so you'll see it's actually pulling up immediately the pages that have got vSphere on. So it's a searchable content. And again, this is all just generated by the markdown. And I think something like this is more what the community, it's more useful just having that sort of search feature, having the menus and both the table of content, also the in page menus, it just makes things a little bit easier. And then if you actually go into the Git repo, so if you just click the Git repo link at the top right, that'll take you directly to the Git repo. This is based on. So you can see that it's all based on GitHub actions on the GitHub dot GitHub folder. And if you push to the main branch, and you've got an action here that will actually build and republish to GitHub pages. This is hosted on GitHub pages. So this will automatically build along with the build. It does a spell check and a link checker. So if you've got broken spelling or broken links in there, it won't publish it. The GitHub action will fail. But that'll go there. And then if you look at any of the pages, you'll see that they're all just pure markdown. So in the doc section is where all the content is. So there you've got the pure markdown. If you go into the blog section, that shows you one of the. Yeah, go into the. Yeah. So if you just look at raw there, you'll see that this has got one of the extensions. It just uses the table. And you've got just the table as pure markdown just using the. And you've also see at the top there, we've actually added some spelling where there's some words that weren't in the standard dictionary. So you can just put a comment in to actually add words that aren't in the standard dictionary. So other than that, it's sort of fairly standard markdown. It does. We do have some extensions. So let me just find one. Yeah. If you go into the community page, just the one below there, you'll see that you've got that little to do. And if you go back on to the website, you'll see that that comes up as sort of like a little header section where you've got to. Yeah, you've got that to do section. So that's a way of doing like notes or warnings or errors or to do or information just with three explanation points. And if you want to, we can put tabs in there as well. I haven't put it in the website, but three equals sign gives you a tab and you can actually have tab sections. So if you want to do different instructions for windows or Mac or Linux, you can actually just put them in separate tabs. So anybody can get up to speed. As long as you know standard markdown, anyone can get up to speed and create content very, very easily, whether we want to put a pipeline in and build it within a red hat sort of infrastructure, or then we just want to leave it to get up and actions and pages. I guess we've got to change the, the footer because it says powered by red open shift online. If it's all by get up actions and pages, we probably need to take, take that off the footer. And what I also did in the discussion item. I did sort of raise a lot of issues in terms of the styling because we can stylist anywhere we want in terms of what have you want to style it. What should the front page be? What color schemes do we want? I just picked the colors from the current top header section on the current site, but we may not want those colors. So that there's a whole. And actually, I actually put it within the site, didn't I? Yeah, if you go to the community page, the contributor, and then the OQDI review, yeah, this is the content actually put it on the site. So just little things about the project lining page, the actual styling we want. And then obviously we've got to think about how, how we want to organize it, what's the top level menus be? And how do you want the content to look and where do we want to go from it? And again, this shows then you've got the high level navigation for community on the left and then the table of content for this page on the right. So I think this is a good technology. I've been using it for a few years now in a couple of projects. And I know there's somebody on the King K native projects. They have a similar problem where their current technology. You need sort of a master's degree to actually understand how to write a simple page. So they're looking at the same technology for K native. And there's a couple of projects in IBM that I've put onto this. And it just seems a reasonable, a reasonably stable, easy to use technology. The only question I have is, is GitHub has GitHub pages. Which is even simpler. That's what's hosting this. This is hosted on GitHub pages. This is just, this is this. Is it the same thing as GitHub pages or is it? No, this is good for pages. Okay, so that's. Diane, what you may be thinking about is the previous incarnation of GitHub pages that was built on a technology called Jekyll. But GitHub has moved away from that in favor of these more generic rendering pipelines. So you can do things like use, what is this MK docs you were saying, Brian? Yeah. Okay, then, then I'm like totally down with it. So, I mean, all we really need to do is add a CNAME directive and whoever owns the OCD.io would point it to the GitHub page. And then we put a CNAME tag within the repo. And then you're done. So, I'm, I'm game to try and move our OCD and when, you know, to work with you, this, this group of people to get that, all the stuff over there. And when you're ready, just, you know, we'll re point it. Yeah, I mean, there are quite a lot of questions about styling because I said I just did this very quickly within sort of a couple of hours. So the front page needs to change quite, quite drastically, I think it needs to be simplified and made easier to navigate. And there's a lot of sort of bootstrap in there that you notice that when you move off the page, there's a little bit of inconsistency in the top header. If you go to a different section, it's sort of because of the bootstrap MK docs CSS conflicts. There's a little bit of inconsistency there, but and then obviously, is there anything else you want on the footer? And if we go and get a page, we probably need to take that that one, that central link out. And so, and this will come out of left field, but Bruce and Jamie, are there any college university students that might want to take this on for like extra credit or swag? Over the summer to get this done is there. I mean, we all check into that. I think one of the things in pulling someone in is that they because they're not familiar with the history and sort of the discussions. There might be some hand holding at the beginning to get them sort of aware of where we want to go and whatnot. Particularly because theoretically we'll be editing and cleaning things up as we move it over, right? That's a process of cleaning up the pages and and jettisoning some things and adding other things. I can ask around for sure. Yeah, there are lots. I wouldn't want to wait for that to come about. Yeah, I'm just trying to think of, you know, and I know all of us have workloads. Mostly what I usually do in stuff is lift and shift as is, which is not quite what I hear everybody wanting to do. It'd like to make sure there's a home for everything that exists right now on okd.io and then cut over and then keep clean clean up from there. So, you know, we don't lose anything. But I think that's a good plan actually is, you know, don't try and do everything at once. You'll make it perfect and move things over. And then, you know, you're not even sure what you lost in the process. Yeah, I mean, I mean, the easy way to do is I mean, I'm happy you can use this repo or we just set up another project in the open shift, like maybe a beta site. We get it working and when we're happy, it's live and then we can just switch it over and we can just do the push into the okd.io site. So it's probably easier as just having a working beta that we can build on, let people contribute to without necessarily maybe having to do the full pull request as sort of official as we do. A bit of a sort of lucid project to move it quickly. Yeah, I know I'd be totally down. If you want to just talk this I'm happy. If they want if you want to spend a time I can go over how it's all all the conflict files. It's fairly simple. I mean, I think I put the link to the mk docs. I guess the question now is who has actual. So, Diane, you have actual control over okd.io. I do. The only thing that I don't have control over is redirecting the C name that I have will Gordon is my and Jerry follow is on vacation. You can't add anyone to that right anyone from the community. It has to be only read. That is a I don't think I will double check with there, but probably not. We had a Joseph Joseph's got right. Oh yeah, that's right. Joseph has rights. We can add people to that. Why not. Okay, well then why not add Brian. Okay. And then Brian can create a folder within the repo that is the content. Yeah, for the new site, and then folks can just chip away at it. What I'll do is I'll create it. I'll create a different branch. I'll create a beta branch. There you go. And then we can put all the new content in the beta branch. Perfect. And Brian, can you just do me a huge favor and type in the chat your GitHub ID. Or you're the link to your GitHub ID. You're actually seeing it. It's the top it's be in this. Okay. All right, cool. Let me just ask. We've got. Well, we've got seven minutes. I do want to get through everything else. So let's. Let's get up to that point of getting that. Then give Brian access. Brian, go ahead. Create the branch and then we'll. Take it from there in communication offline. I do want to get in the meeting to the. We have like three more things to get through so inclusive language update. I have a quick one on that actually. Well, Brian, go ahead and give us an update as to where you are. Nothing's really changed since last time I did the, all the scans and I created the pull request with. And all of the issues that come out. I mean. And most of them. Were we're just in the sort of comments of code. There weren't too many issues on the site. Yeah. The main one obviously is the branch name master. Going to main and then there was just a couple of other, other typos that. And but I'm guessing if we're going to change the technology. We can fix that as we migrate the technology. So here's a quick question that sort of ties into this, the community repo. What are we going to use that for the working group stuff is that or what. Diane, what do you want to do with the community repo and that actually does have a master branch still. Which actually you could change yourself because you have the ability to do that. So what do I want to do? We're no longer using the agenda that's there. For for meetings. So. I don't have a real strong opinion about what we do with that. I think there should be because it exists there. There should be a landing page of some ilk there that gets people to. The working group and and otherwise, but I don't have a strong opinion to be quite honest. Is that just for or is that a mode a general catch all for other community projects as well. It's a catch all for everything to do with open shift. So. That's that's why we have this separate okay.d.io repo for things that we need to do because then we don't have to ask permission. So do we then want to put because that was one of the issues is because I was doing the agenda and I wanted to actually create the agenda without having to do pull requests and stuff. I went to hack and do we want to use part of okay.d.io as the working group. Like meeting notes and membership and we should payers and all that stuff. Does that make sense. We should. Is there any issue with a separate folder Brian. Being non website stuff or things that get rendered differently or maybe don't get rendered. No, I mean, if you look at the get repo, there's a docs folder everything the docs folder. Is taken as being content for the site everything outside of docs folder isn't content for the site. Perfect perfect. All right, well I'll take that on is moving the stuff from community over to okay.d.io. Anything else on the inclusive leg language front. The other one that we've got to do is obviously the main okay D repo. We haven't looked at that yet. I don't even think Vadim has the ability to change. Yeah, that's going to come. That's going to come with open shift doing their update. No, when that that group does that that should is there. Let's see which that's sorry guys I was trying to do something else to get Brian and something here but I'm not on the page with you right now. So which repo is this I'm sorry I was outside of this it's it's it's fine. So the the okay D code repo that falls under red hat and I don't think Vadim actually has the ability to change branches. Does he have no ability to change branch names. No, that's about his pay grade even. Yeah. Okay, so we'll we'll wait for that one. Michael you had volunteered to do a docs process documents like basically outlining the document that outlines the process for identifying bugs in documents and stuff. Yes, got to start on that the other day. Of course I put it in the Google Docs I think I can only share with red hat folks. Well, when you get a chance maybe at the next meeting if you just let us see sort of where you're at with that the idea being that we want to direct people to something so don't have to keep repeating ourselves. Like, go to this page to learn how to submit a issue on okay D documentation. And then the last item on our agenda in the last minute that we have is Brian and I will work with and to create an outline for Vadim. To create a build guide and the reason being that since Brian and I are slightly familiar with it but not completely and we have questions asking questions is a great way to get someone to write a good doc. Because they're not writing it from what they know they're writing it from people who don't know questions from people who don't know to Brian and I Brian will team up and do that and make some progress on that. And I think the other thing is, so not to overload Vadim. If we do that is a sort of community call. We can actually write based on that that sort of transcript we can then write the con the documentation. So we don't put the, the work on Vadim to actually write the end documentation. If we get the questions answered we can then write the documentation and get Vadim to sort of just review it to make sure it's correct. Yeah, perfect. Does anyone have anything else before we close the meeting. I got, I got something. Oh, hold on. Okay. Who said who spoke first I didn't catch it. Okay, yeah, go ahead. Yeah. Sorry, I last week I actually start. Seeing the oracle has a cloud apparently I didn't know. So is open shift or okay, do you going to get into that or not. It's not I mean, if you're talking about UPI installations, you know, you, you can install it on whatever kind of like bare metal infrastructure you want to but if you're talking about like cloud integration with Oracle cloud I don't think it's coming anytime soon I haven't. It's not slated on our next few releases. And when I say that I mean like, there wouldn't there's no machine API provider for Oracle cloud there's no cloud controller managers for Oracle cloud so like Kubernetes slash open shift will run on Oracle cloud if you treat it like a bare metal type deployment, but you're not going to get cloud integration through a KD so you're not going to have, you know, the components I was talking about. Okay, cool. I actually asked that because they've got apparently arm based processors and they actually have a lot of it. I don't know how. So that would be a good playground to sing for deployments and stuff. And there is a problem with they don't give you access to the machine directly so I don't know for you plan solution. What can I do that's attached the ignition file to the user or and they don't let's. Yeah, let's talk about that actually in the main meeting because there'll be more engineers on in the main to talk about that so we'll talk about that next Tuesday in the in the main meeting with the larger group because Vadim will be there. Christian will be there and they'll be able to chime in on some of these things. I'm sure. Okay. And Brian, we're adding you now to have access to the okd.io site. It should ripple out in a little while. I didn't do the same for me. So that I can do the agenda and stuff in there. Yeah, and your your Jamie type in if you could just type in your. Yeah, let's do it. It's just my full name actually. Thank you. All right. And then Michael, I think you had something else was it you who had something. I had a question just on the document working on the file issues. Do we want those issues created against the open shift repo or the okd repo. It's it's against the documentation which is. You know, the open shift repo and it's the ones that you'll end up tagging. So that would be the open shift repo. Yeah. It is the documentation source of the open shift. Yes. Right. Yeah. Yes, that's what I just want to make sure. Yep. I've seen him in both ways. I think we're good. We're four minutes over, but we got a huge amount of work done. Thank you everyone. Thank you very much for hosting and doing this. So thanks a lot. Thank you. Yeah, thanks.