 So, welcome to the documentation and communications subgroup meeting for December 14th of 2021. And this will be our last meeting for the year. And actually the last meeting for the year. And so let's start out looking at current projects. So the charter updates. Nothing yet for me on that. Nothing yet on the, the basically install and read me stuff. We're almost got everything moved over. And created doc for the build outline. Haven't done that yet. Vadim hasn't been available for a regular meeting time. Brian, maybe we should set up a time to meet with Vadim and just talk to him about this. Like separate in the new year, since it's been kind of hard to catch him at meetings. Maybe you and I can just ping him and the 3 of us can have like, even a chat meeting or something like that. Yeah, that would be good. Okay, excellent. Code of conduct, search and replace. Michael, have you had a chance to do a search and replace on the code of conduct document? I have done that. Yes. Run through and clean it up. Change some of the wording around just so it's not a direct steal. Okay. Vadim has given his looks good to me. So the rest of the team here can take a look at it. Should we look at it now? Or should we do async and send something out to the working group mailing list. And have folks respond on the ticket. Async probably be sufficient. Yeah, I think async is better because I think reading now we take up time and folks are sort of hash things up. All right. So I'll send some, I'll add that as a task. I'll send out something to the working group. Send email to working group. To look at. Code of conduct. Survey, I don't know. The status of that is, I think we'll have to reach out to Dreeti separately outside of the meeting. It's 11pm for her. So. Yeah, have you been able to get a hold of her on the Twitter stuff or the survey stuff in the past week? The last time I messaged her, she was out of the office and I haven't tried again. So she was on, I think on. Yeah, there's, I'll keep pinging her to and CC you on in Slack. So eventually, because I would like to get the username password shared with between you and I as well for the Twitter. So in as well as figure out what to do next for the survey. Yes. Yes. Yes, Daniel is not here to talk about the guides updates for folks who weren't at the full meeting. He was in the full meeting and gave an update. And we decided to do it as a discussion thread. So he's going to be doing that probably in the new year to round out the guides update and then that'll clear everything out of the repo. That is sort of content related. And he'll work with Brian on making sure that that's all nice and pretty on the website. One more in there. In early January or late January, we have the dev comp CZ, which is now virtual. What I'd like to do is add a task and I'll take this on to with some with. Christian is to update the presentation slides that we've been using. Whenever we do an office hours or when we do these meet up hallway meet up things at there so that we have an updated set of slides. We've been using the same slides for a while. And I think they're due for a bit of revision as well, especially with the new release and 4.9 information. Make sure you grab the version that we had in. What was the event hours from a couple of months ago, right? Because that one, yeah, that did get updated and he worked on that a little bit as well. So if you can, if you have the link to that somewhere, just throw it in here or share it with me and I'll do it. I just want to make sure we have some of the latest stuff in there. And also because Bruce, you had been asking those questions about C groups V2 that and that is something that's in Fedora CoroS or is coming in Fedora CoroS. But it's not in real nine. So a little, I wanted to add a slide in just sort of the early warning system for that coming and when it's coming in, in OCP and, you know, what's that? So I'm sure other people have things that they want to add in or update as well. So I think that's the thing we should just keep a refresh every once in a while. So it looks slightly different at least. Yeah. And I think that's as much of a documentation issue as anything so that people know what they're getting and how to change it if it's not what they need. Yeah. Yeah. So yeah, so that's that's that's the only other issue that I or topic that I had. Great. There's there are no new issues in the repo that I saw. That aren't things that we've already talked about. Of course, the low contrast for the for the CSS. Brian Innis, you're on the call. I think I had Brandon Johnson send an email out to you and I and I haven't reviewed it yet with some suggestions for the. Where did he send it to you because I don't. He didn't receive anything. I thought he sent it to your Gmail account. So, because, but if he did, if you didn't get it, he did send something and I will dig it up. I had him review it and make some suggestions on what we could do to make it more. A better read better readability and more. For people with disabilities being able to more accessible site as well. So, he had some good suggestions, but I haven't dug it up and I'll dig it up and resend it if you didn't get it because he just had to send it to you and with me CC and so. What was his where to come from? I'm just looking at my junk mail to see if it sucks. His first name is Brandon Johnson, and it might have been from his Gmail account. He is a red hat contractor. It could be Brandon. I don't see anything. Let me just go into my inbox and see what I have. Just the two of you synchronize outside the meeting and see if you can figure out if you can just contact me that I just couldn't paste it into Slack. We can look at that. And there was one, two or three, the modifications for inclusive language. I think we've, we've taken that through the main meeting. Let's go further action on us. It's all on product and other repos. So, I just wanted to make sure that everyone's happy that I close that issue now. Yes. That was awesome. Yes, here it is suggest it's the title string is suggested CSS changes and he sent it to bri.inus at gmail.com. Oh, that, that one. Okay. I'm just going to take that one. I don't actually check that one. International man of mystery with many accounts. Yes. So I'm going to forward it to Jamie as well. So he has a Jamie. Thank you. And there you go. I need to go and work out how to get into that account. What don't worry too much. What is the email address that you do check Brian. It's bri.inus UK at gmail.com. Go ahead and put it in the chat. That way she can just read it or copy and paste. Yeah. And you will get spammed. I've already said it. Right. Let me go put that in there. Okay. And I'll send it to everybody. So you'll get it. Yeah, I was wondering why I hadn't heard back from you on that. I read it. I didn't read the whole thing. It just didn't. All right. So in terms of issues, so you're dealing with the accessibility ones so we can let that go. The other one was the group charter legal input. So we basically have the legal input in terms of external repo and social media. And that one be closed out. Yep. Okay. I'll close that one out. Well, I'll come back to it and close it out now. Actually, I don't know. Just get rid of it. Information gathered. No issues. Okay. Close with comment. There we go. Let's see here. Missing security contacts. I got that one. I'm writing up my. Ask for someone in the community to do that and. Code of conducts that's in process. So no other issues. The poll request. Where are we on that poll request for the virtualization documentation, Brian? Okay, so I actually have merged it, but I was hoping to get. Some reviews on that. And we sort of had a conversation last meeting that. It'd be good if we as a collective as a group. And they pull requests rather than me just doing it. And so this meeting should own the, the, the, the content. And I just felt that if I was just doing everything myself, then it, it doesn't reflect this group. So I left that one hoping that somebody would comment and nobody did so I just closed. I just accepted it and merged it. Okay. I guess if no one responds after, let's say. Between the time of a meeting, you know, 2 weeks. And that's what I did. I went and closed it before this meeting most of them before this meeting. So I left 1, 1 duration between documentation meetings and then I merged it. Okay. Perfect. And we should be better about that. I'll make sure I send reminders for folks to look at these things. We'll add it to the task list. And that actually brings us to the task list. All right. So what we have is create a list of links to add to the PR against product documentation to add the extra book. I still need to get done sending email to the working group to look at the code of conduct. I'm going to do that and then share link to the latest slides iteration with Diane or to Diane, I should say. Did I miss anything in terms of action. My goal is with those slides is to get a good deck that with speaker notes in it that any of us or anybody in the working group can give a at a meet up or any time internally. Just grab this deck and it will be semi up to date. With the latest release note. Whatever. Then we will have that for 2022. For sure what I would be inclined to do is make it part of this group's process to maybe quarterly. Go through it as a group. If even asynchronously, just to make sure it has the latest and greatest. And that way it doesn't have to happen in the lead up to an event. It's just part of our process and this is that would be that would be awesome. We are very all of red hat is as well very event driven. As you see product releases going out in terms of when red hat summit happens or coupon releases. So it would be nice to have it on a quarterly cadence. Do we have any thoughts about where that should live. In, in the, in the whatever the github repo is that we create the github.com slash. Okay, the project or okay D and on that note, I will say I reached out to the one fellow who was following that repo. The one turns out he follows 350 other repos as well. So he just is a follower. Nobody has responded to me from that. So there is a process at github. Where I can ask to take over a site and I will, I will put that in, but yeah, so maybe in the new year, if nothing happens from github that they don't respond or whatever. We'll just go with a okay D dash project site and be done with it. All right, I'm adding a task for you to do that process go through the github process. And I'll create a ticket for it just so we have a documented that we tried and if it doesn't work then doesn't work. Okay. And I can't remember that mean we've, we've given up on get lab. I think so because of the lack of discussions. I think and because we're so because we're using discussion for so much right now. Yeah, and we can always move it down the road, right? Yeah. I think most, if not, most of the red hat. Bonsored open source projects are in github and culturally, I think our communities lean towards github. So, not, not that I have, I like both of them. So, it doesn't really matter to me, but I think I'd rather stay in github where we have people already connected to us as opposed to disconnect and reconnect. And making that ask of people. Diane, I think it's like the okd is enough better than the okd projects that I think it's worth really trying for that one. Yeah, I'm going to, I'm going to write to github and it I was trying. There was a guy Kevin hook who was hooked to 300 as I said 350 github projects. I thought he was the owner of it. I was mistaken, but he did respond to me. So kudos out there. Developer over at Pinterest, who's very into security. So, yeah. Speaking of which, close out with one thing. Did we want to say anything about log. For Jay, like, it doesn't really impact us. Directly because the only thing in open shift that was impacted was the logging operator, which we don't have. So, that I know of there's nothing that directly affects that it directly affects okd, the vulnerability. Does anyone have any a different sense that that's that there is something we should be looking at. Should we say something like we are not aware of? Should we just make a quick little comment on this? We don't have a security person to do it now, but it might be. I'd rather not. It's going to impact us and we are not supporting the logging operator personally if because if we do then it's going to distract I think from the open shift messaging around that or the red hat messaging and I haven't even looked to see what's what's out there. Yeah, but it might distract people. Yeah, as well as if you say, like, I looked at that one and it was like, okay, noted. But if you say that it doesn't affect us. Then you're really taking a stand. Right. And you're setting yourself up if something is shown as as pop up. Yeah. All right. Well, then that brings us down to the end of the meeting. Any last comments or questions before we sign off. I'm just looking forward to 2022 guys. And getting working more with Michael and getting the extra book in there with the guides updated and it's going, I think we're going to rock it next year. And I think so this has been a fantastic year and everybody's work. That's right. Yep, we're going to we're going to wait that extra week to give folks a chance to settle in and what. So the next docs meeting is what what's the date of it. January 11th, January 11th. Okay. And the next working group is on the 18th. That's right. Yep. That's right. And I need to go and actually delete those calendar events. So I will go and do that today. Cool. Right guys. Again, Brian, Bruce, Michael, and especially Jamie, thank you for everything you do. It has really rocked this year to have this external and extra support for docs. More of this. Cool. Yeah. And what you do. Happy holidays folks. Talk to you soon. Bye.