 The agenda, I'll put the link in the chat here, if someone doesn't have it. Hey, anything that people want to add to the agenda to cover everything? Bruce, I think you had a question that we'll cover in the beta section. Yeah, we'll cover it. Yeah, exactly. There's a name in the attendance section. Yeah, Brian? Yeah, there's one thing I was just thinking about in terms of when we get changes, as soon as people are going to want to make changes to the site, how do we want to do reviews? I think we probably need to work out a process in terms of just how we want to go and I know we've talked about this in the past, but just who should be doing reviews and other issues that we need to, or any process we need to apply to reviews. And who to review? Okay, I added that as an item. Let's go ahead and jump in so there's no updates on the charter update and placement. I haven't had a chance to do that. I was finishing up the video stuff, which I just finished last night. Beta site, Brian, go ahead and take it away. Okay. Yeah, so we're finally live. That happened this week. So you'll notice that the site now looks a little bit different and we are fully onto the MK docs. There's a couple of things that I've got to tidy up. I've done the changes, but I haven't actually pushed them to the site yet. I think there's a couple of links that got broken where things were pointing to the old site and now need to point to the new site. But yeah, I think we're pretty much there. I noticed as I joined Bruce, you made the comments. So yes, that's one of the things I've got to change. When I put the beta site up, there wasn't the versions for OKD. There was just the one version. So we decided we wanted to get rid of that menu because there's no point in looking at all the OKD 3. 2.1.versions when there's just the latest. But now that Michael's put the versions in, I can go back and point to the previous site. In the short term, if you want to get it, if you just go and click on the bread trail, the left-hand-most link, it takes you to that page. So if you want to get to it immediately, that's where you get to it. But hopefully by tomorrow, I should have pushed the updates and we're going to have that landing page back. I think that we didn't say that we wanted to get rid of all the versions, just the 3.versions. Because it still is useful to have. We do have people out there that are running even 4.5 because I keep seeing problems updating 4.5. So we sort of need the 4.5 docs, the 4.6 docs, 4.7 docs. Yeah, but when we had the beta, they weren't available. We just had one version of OKD, version 4 was set. No, there was a point in time, perhaps briefly, when all of those versions were available. And at one point, the latest disappeared. And a different point, the latest point to 4.8. I don't think we ever saw 4.9 as a version, but there was a point where I think 4.6 and up were selectable. That's fairly recent behavior, because while we just have, so when the beta was published, there was only the 1.4 version. So that was probably a race condition between the old site and the beta site. And that was made into the old site that never made it into the beta site. But anyway, we can talk about what we want there. Because I think I'm not sure if it may out. But from the experience we got with 4.8, we are maintaining only the supported version documentation. So it depends on which version of OKD are still under support by the community. And I think that's a question I haven't really answered yet. But there's a point where I think the community can say, okay, we don't have enough institutional knowledge or effort to officially say in any way that anyone should ask us questions on this. Because you know what I mean? Like, I don't know. It just seems like it's asking for, and it's also, it allows, it sort of gives the impression to people that they can stay on. The version that they're at, if they see it in the pull down. And if they see that it's, it's, if they feel that if it's in the pull down, well, then it's something that's supported. Yeah, that's a good one. Yeah, just just a moment. So I'm just so I'm clear and I think anyone who's watching this video is clearing that just share the screen with the docs dot OKD dot IO. And those are all the ones that are available in the docs there. So those are the ones that I suspect we should be point being able to list on the mk docs version of OKD dot I or are you shortening that list up. I'm pointing to the page you landed on. Yeah, it's going to go to the page. But I mean, it is a very interesting question is what is a supported version of OKD because I know OCP have just changed their long term support to be every version from four or eight. But in a minute, 4.6. Long term support is supported. But on OCP, it's only 4, 7, 4, 8, 4, 9. Now that I currently supported everything else is out of support. So we're still listening. 3.x version in the docs. Yeah, but if you're supporting it yourself with the docs for your version not be useful. Yeah, well, but I think it gives the impression that that someone is maintaining those docs and someone is maintaining the resources. There's links within those docs that go to like playbooks, Ansible playbooks and things like that. And so it's kind of unclear, you know, do we have a guest. Oh, cool. Hello. Yeah, that'll resolve in a second, whoever it is. On the OCP docs, though, you can select the version you want. Right. Correct. With the docs that came up when I clicked on the docs on the new site. You only got 1 version and you couldn't select. That's a point in time thing that'll be gone by tomorrow. We will, if you point, if you go to the left thing on the breadcrumb, that's the page I'll land at. Which is the page of Diane show, which has the drop down on. So that's going to become the new landing page for docs. So, again, I do think the bigger question is, what are we going to say that we. Support in terms of the community, because ultimately that does mean maintaining. The linked resources in those. I'm just going to just clarify this because every time we say support someone at red hat loses their wings or something. Angel loses their wings or an essay dies. I don't know what, but. Probably cries. There is no support for okay D what I think is, is what is our commitment to keeping these documents available for people to go back in time and. And have access to them. So, and I thought what I heard at a previous docs meeting. Was that we were going to stick in tandem with the OCP docs team or whatever they had in. Docs dot open shift dot IO, we would stay in tandem with that because we're relying on the docs team. To generate those. And so as as OCP and open shift drops. Documentation, we would drop them off our list is what I thought I heard in the past. That's what I thought we had decided. But maybe there's a little bit of. We had a situation where maybe there was a miscommunication or something. Here's, here's the issue in a nutshell is that we. Within those pages are links to resources and descriptions of things that even in terms of Kubernetes may not be accurate anymore right in terms of processes may not be considered best. Processes best practices. Right. And do we want to keep that around. And create extra work for the red hat employees. Who have to maintain that. I think that might be a question for Michael Burke, who is the point person for the docs. My understanding is, is that like, say we have a 3.6 set of docs sitting out there. I think that was the last one on the list. I'm not positive. And something goes out of date. An ansible playbook is no longer available. You know, it's removed from wherever it is and get hub that it was linked to. That that's not anything that we're going to redirect to a newer ansible playbook, or that Michael is going to that link will just be broken. And so I, and that's kind of how it works with other things as things go out of date and go state links go stale to. I haven't checked that if that happens with OCP, but I would defer to Michael Burke. Personally, if they do that kind of upkeep on the older documentation sets for open shift, I don't think they do. I think if that playbook. I mean, those dead as it becomes a dead link. It's a dead link in the open shift docs too. Was keeping those things up to date would be a very big job. I think that we should do a bit of distinction here because whatever will be declared as supported by reddit. It's not meaning that it will be supported while maintained by the OKD maintainer. So, even the documentation, I think that if within the OKD community, we are going to fix packs that are reported against four or seven or four dot six, it's fine keeping documentation back to four dot six. But if within the OKD community, we receive a bug and we are not going to touch it because it's something that nobody is going to work on. There's no real meaning in keeping documentation for such versions. Yes, I'll just put it there's the OCP. Drop down and there's the OKD drop down. Yeah, and I would bet if you go and anecdotally, I would bet if you went to the three dot oh container platform, there would be a bunch of broken links, things that no longer existed that it linked out. Well, they also have their wonderful red text overlaid over everything that lets you know that, you know, this is actually saying this is not supported. So maybe what we need to do is make a decision about which one is no longer going to be community supported and some red overlay like that on that and and I'm fine with it, but I maintaining the links is going to be a big deal. Let's let's table this and have folks think about it until Michael shows up at our next meeting. There's six of us on the call and then there's Michael and then we can also ask the larger group. What they think, because in a way, in my mind, I think it does also impact people's perception of when they come into the channels asking questions and things associated with the release and think things that release are associated with earth that are associated with an OKD community. In terms of chat in terms of, you know, us providing these guides and things like that, like we generally are only going to provide guides and focus our efforts on promoting things in the community that are supported that are versions that are in sync with OCP. That's my sense, but who knows, you know, and Vadim might have some input on this as well. Alright, so let's table this just because it's it's probably a larger discussion. Brian, what was, are there any other lingering issues. I don't think so. There are some bits I've got to do. I'm working on putting a section on creating or updating content. I'm working on putting a section for using sort of container images rather than having to install stuff locally. And I've also sort of playing around with the community and already workspaces, the CHE and the CHE and creating a dev file so you can actually edit it within that environment. And so again, you don't have to install anything locally, not even Docker or Podman. You can just run it on your container, on your cluster, your OKD cluster. I want to put a little bit about inclusive language in there. I think I've got an issue open against that. And as I say, I've just got to fix the landing page for the documentation now that we've got that dropdown back with multiple versions in. That's it. There's no technical issues or there's no challenges that we've got to really overcome. And we're sort of into business as usual now. So if people want to tweak the look and feel or they've got suggestions for better layout or better wording, we're business as usual on the new site now. And then your next item is about basically for review of suggested things, who and what and where and what not. Yeah, it's really because obviously I'm a committer on this and not everybody is. So it's really when somebody makes a pull request. So is there a process that we as a group want to do to evaluate and agree and approve changes? Or I mean, I'm sort of doing it myself at the minute and just reviewing it and making a call. And I'm just thinking as we are the documentation group, should we be more proactive within this forum to actually review and push changes forward? Could we say something like in this docs meeting, we will review it each time we meet the pull requests that come through regarding the site and keep it as simple as that. I mean, in the past, I just willy-nilly did them as I saw fit or as people gave me stuff and was just grateful. But I think if we use the same process, Jamie that you use in the main meeting of looking at the pull request issues and that that are related to the docs in this meeting. And then, you know, do the, you know, merge the pull request if it passes the muster here. As long as we have, you know, I don't want to say quorum or anything like that as consensus, I guess is the word that it's okay and maybe that we have had Brian do a technical review of them of it and just tell us and just use this meeting. That is that with the rest of the group is thinking. See heads nodding. Prety, did you have anything you wanted to chip in on that? No, I think I agree with it. We could review the pull request and I'll be more proactive with reviewing the pull request. And all right, next thing up is the name and scope of the install and read me now that the site changes happened. That's something that work can begin. I'll begin on that and I'll run it by the group as time goes on. Inclusive language update basically done and Brian said you're going to have a little blurb on the new site about that. And work will commence now on the build doc outline that we can submit to have Vadim sort of fill in the blanks or at least look over that he is to have something for building OKD and people knowing sort of where all of the pieces lay of Vadim's obviously kind of busy right now, but I think if Brian and I work on something now that the site stuff is out of the way, maybe we'll have more time. Oh, yes. On that one, Jamie, I think it's worth also just going back to the discussion we had at the last full meeting around. Code ready containers this this know the single node install. And it sounds like there is something to do there. People are quite interested in the single node install versus CLC so I think we need to include that within this topic as well. Yeah, I think you're right. Yeah, I think that's that's a good one. And Jamie, I apologize. I don't think we did we reach out to the folks. To schedule a time to find a time for them to do that CRC snow special sick. No, we did not yet. My sense is that now that the website stuff is done the floodgates going to open on all of the other things so there was a lot of emphasis on that and some of the other projects going on for me the video stuff. We will set up a time for that and once that group is solidified and has met. I think it's it's a great way to create documentation as you go. So as they discuss things, say, okay, this needs to be in the documentation. This needs to be in the documentation, etc. And in terms of the code ready containers. Charo had his document on his blog is a great starting point and then building on that I think is something that we can. I just wanted to see if we could let's let's try after this meeting to touch base with it was Daniel Neil Neil Gamba and Daniel Axelrod. I did reach out to Steve Spiker and a couple of other the folks on his team. The PM for code ready containers in there. He gave me the name of two folks to include in that sake too. So hopefully I don't move it forward. Let's see code of conducts. That would be Michael for the search and replace. He's not on the call so we will come back around to that. So there was so we've sort of been lobbing back and forth this idea of setting up our own Twitter or not. If we set up our own Twitter someone has to man it right someone has to do that work. Do we think we have enough people because I don't have the time to do all of it myself like there would need to be two people basically to be able to do that. I think we have the resources for the volunteers for a second person to do Twitter duty for us to launch our own Twitter. I could do that I could help with that. Okay. All right, well then that would be great. So, I think maybe what we could do to start is look and see what Twitter handles are available to us. Okay, what we could use if you could spend a little few cycles on that and see if we can reserve one of them. That will be a good start though. And again, where I think we last left it was as we have and as we need to I can retweet anything out with like an okay D hashtag out of OpenShift Commons. So if people have things or blogs or things that they're doing, we can start doing that and that's easy enough and are you a red hat or sorry, I can't. Yeah, I'm with Red Hat. I work for the CFET team. Yeah. Okay, so I thought so. I don't recommend to retweet everything with hashtag okay D because there are weird stuff with okay D hashtag on Twitter and I wouldn't really. Oh, no, I know. Yeah, so it takes a little bit of vetting so maybe DTRI if you want to do that and just set up a Google chat inside and you can include Jamie as well in that and then if there is something that you need me to retweet. Okay. OpenShift or OpenShift Commons that should be you can just feed it to me there. Okay. Okay. Okay. Or do it to me in Slack whatever wherever you want to do it but find me. And I would I'll wake up whatever time it is. Theoretically. Okay, but I think that that the person that the person who reserves the okay D whatever the Twitter handle is should be should be with a red hat email address. So, I think that's the one thing that legal would like us to do so that it's owned by because it's a branding thing. Okay, thanks for letting me know. So I'll come first. Let me come up with the available handles to you and then we can move ahead from that. Yeah, I would recommend to get open source program office involved with because we have a bit more than a count that we can use to store password for those kinds of account with. They that is mandatory for everything that I stuff I have the bit warden stuff is cross all over red hat. So once we find it, it'll get put in there. And then if any of us gets by bus. They can still tweet. Let's be an optimist. I am a lottery. Yes. Okay, so let's. Okay, I've added that to the task list. And then actually you're with the next thing survey. I just came back from P to haven't started on it, but I do have a couple of questions in that. So, I created a list of questions in the user survey discussion that we based it over here so that. So, I can see. So this is the discussion and I can see there are there some comments by Sandra and Adam. So, do I finalize, do I include their questions in the final question list or. To take a look at and see if it's into what, you know, what I mean, folks can look at the discussion and give you feedback, I think, but I'd like to let you roll with this and make some. Some editorial decisions. Sounds good. So let me come up with a final this by tomorrow, the first draft and then I'll share it with you guys and then we can take it. Perfect. And we can use. Open ship commons would be a good once you have the Twitter. Once you have it done, we can tweet it out. I would also post it on a couple of places under LinkedIn and on the mailing lists. And in the, you know, the Kubernetes things, but I think we can get a good. Round of feedback on this very, very well done. Good. This 1 more question, Jimmy, do you want me to look at some of the existing questions that red hat OCP related? Previous survey questions or. Yes, I think so. What does the group think? Yeah. Yep. Excellent. This is great. Thank you for running with us. We've needed it for a long time. Now, I guess in that it's been a while since I saw a list of questions, but are we asking what version you're running in all of that? No, no, no. I'm not asking that. Do you think that we should ask that? Well, I think I think one of the, I think that it is a difficulty since we don't have telemetry. That we don't have a good handle on what people are running. Okay, like OCP. Okay. Yeah, I'm going to write that question on. And I think that goes back to our already discussion in terms of documentation. But if we find it's a large. User base that are still at sort of 4.4 or 4.5, then that gives us an incentive to actually keep the previous versions of documentation around and stuff. And I guess that should be a multiple selection list because people to be running more than one. I would be also interested to just in the number of people using OCP. Which is kind of an unknown. Okay. I would say folks should, should put it in the, if you can put it in the, in the ticket. Then that way she doesn't have to put it in all these notes right now and people can clearly say what they think should be in there and whatnot. So please update the ticket with these thoughts that you've been thrown down. And then that creates a record moving forward of how we came up with, with this. Yeah, yeah, that would help. All right. And let's see next up is just reviewing the task list. Let's see. Oh, do we have any new business any last minute walk up items that folks have. Yeah, I just, I just got a question. What's happening with the time of this meeting. You went back an hour. So this is an hour earlier for me. And I've just looked at the Fedora calendar. Time doesn't change, which suggests when you guys go back week after next. I think it's a, I think it's scheduled on UTC. It is. So it stays the same in UTC like North America is about is about to go off daylight savings or whatever we're on. So it's going to move to the night. So that's what I'm asking when America's go back an hour, is this call going to go back an hour? Or are we going to be out of sync the talent, the public calendar? Of course, that's a Diane question. I believe we're sticking with whatever UTC is in the Fedora calendar. And so I just adjust based on whatever the Fedora calendar says to me. I don't know if we can we have this conversation every year. But I'm pretty sure we just stick with it. We can write it out so that in the future we know. So, I think it makes best to stick with UTC. Right. It means I'm going to have to come an hour earlier. Is that it? Yeah. That's what I'm asking because everyone's used to turning up at this time. Yeah. For me today. Yeah. And what I'm saying is, is it okay for people because I mean. It's actually best for me. Right. Earlier for you is better, right? It's better for you. Right. Like I have it in my calendar in UTC time zone. So it automatically shifts. Yeah. I'm just checking because everything else with my work moves forward and back on daylight savings. So it's the same time slots. Right. So I'm going to stay on the UTC for a week apart from these 2 weeks when Europe and America are out of sync. But this one looks like it's continuing. So we're going to stay on UTC. So I'm going to stay at this time zone. Yeah. And I will do what I always do when it switches over. But as I will stay on the air afterwards for everybody who forgot. That happened every year. I show up and they're like, Oh, yeah. Do it again. Just putting a reminder out when you put your, your, your message in the channel, Jamie that. Yeah, for the North American folks, it's coming in an hour earlier. Jamie, can you share the task list? Is there. Yep. Yep. So, let me, let me share my screen really quick here. What Diane didn't do. Okay. So the task list we have. Manipulate manipulate the Charter, which is me right up code on site automation, Brian. That's still a work in progress. Code of conduct edits Michael gather legal input on external repo social media. Diane. Just so that we know where we're standing with that stuff. Connect with OpenShift Twitter leads to push out okay to contact Diane. Get beta site running and get lab. DNS routing options, right? Bruce, you were going to do some experimentation. And yeah, I was actually, I was pleasantly surprised that it should be possible at least do the. Make docs on Git lab using the Git lab runner. And so I haven't actually tried it yet. I did look at a number of other people have done similar things. And so I guess mine. When I, when I do get that up and attempted to running, then it'll be a question of whether or not the add ons all pull in. Right. I'm not, I'm not there yet. So, okay, we'll leave that on there. And then of course, look for our Twitter handle options. Is there anything else I've missed? I think that has been discussed something like four weeks ago or something like that about moving the OKB website on GitHub under an OKB organization. Is it something that we drop it? No, it's it's still there, but we're going to decide if we're going to get lab. First to build the site as opposed to to GitHub. And then once we decide where we're going to land, then we'll deal with like, okay. Moving to respect. So we're going to this is this is the first stage of that. Yeah. Okay. All right. I think we're good to go. And Diane, any events that we should be knowledgeable about coming up? Well, there's always events like trust me. There is on December 2nd, if you're in Japan, we're doing it all Japanese Openship Commons gathering. So stay tuned for that. The next big event for us is dev comp CZ and and just outside of Prague and Bruno. Anyone who has permission to travel is in and wants to that would be a huge thing. It always snows though. Just remember it's not springtime and check in the Czech Republic. And then there's going to be a number of other things coming up in the spring in the first 3 months of the year. Then we'll get a schedule together and see. But the next big thing would be you in May. I think. All right, so nothing too much for folks that didn't notice there is a. Just before, uh, Kubecon, uh, America's, there was a release of GitOps principles from a new GitOps working group with the CNCF. Which is some pretty cool stuff in Christian Hernandez from redhead is on that group and stuff like that. And I'm sort of tangentially following what they're doing. I might get involved with them as well. But that's kind of a cool thing because they're, they're talking about a lot of automation stuff with clusters and GitOps practices and stuff like that, which is kind of cool. All right. Let's call it a day and if anything comes up, be sure to communicate with each other over the email list or in the, in the chat channels. Okay. So Detry, I just pinged you in G chat. So you should see something and invite from me and we'll add Jamie into that once you. You're there. So anyways, thanks everybody. Take care. Have a great day.