 OKD documentation subgroup meeting for March 8th of 2022. I dropped the agenda link in the chat. I'll drop it one more time in case some new folks have showed up. Look over the agenda real quick. If there's anything that you think was missed, please let us know and we'll add it. If there's anything that you think should be removed, please let us know. I would like to add one thing. Someone at the meeting last week suggested that we needed to start a new hack MD. File because it was loading slowly. I don't know if that's true for everybody else, but I'd like to. Just get people now that we're everybody's opening hack MD. If it's loading slowly for you, let us know. And maybe we need to make a reset, like past ones as five or something. I think this what I think this one's okay. I think the main meeting one is the huge one. Yeah. You may have to do that. So I just wanted to get that on the record there. Right. So I've added that to the agenda because there's also maybe a discussion about maybe we now that we have control over. A repo to actually start utilizing posting minutes in the repo. Since we have a little more direct control over that, but let's get started with our current projects. So. Code of code of course, there's a little mess up here, but code of conduct. You want to go ahead. And take that Brian. Yeah. Okay, so see if this is going to work. Are we seeing a screen. You're seeing a screen. Okay. So I've got the, so this is my, my working draft. I've got the code of conduct in. I've linked it to the community. And so just said that the link to the code of conduct should be made visible at all events. And when you click it, you get into the code of conduct. And we have four places where the word who appears. Just really. Oh, I see. Keep going. Keep going. Yeah, so we've got four places where the word who appears. And I just really want to have a discussion in terms of what we want or who we want to name here. I've looked at the answer in fedora. And there's a mixture of organizers. Sometimes they say admins moderators and local organizers. And I'm thinking we could either say community admins leaders, moderators, or working group leaders. So for example, when we're talking about who should be expelled from the community, we may take that to the main working group. And I just really wanted clarification of these four places. And then I'm ready to publish. So the first one, can you read this or is it like uber small? No, that's fine. No, it's good. Okay. So the first one is in this paragraph. So all community, all events, community members are governed by the code of conduct announcement policy. We expect. Working group chairs. Group chairs are organizers. Then that covers local and online events. Yeah. I think that would be, yeah, that if we can do working group, we can be organizers may mean like event managers like Jen Madria and the folks who run all of the community events as well. So I think if we do working group chairs and organizers that that helps because they have they're the ones if we are on the ground doing something like if I do a commons event or we post an in person event. We'll be responsible for and be the point of context at those event work things. So are we happy with that? Yeah. Yes. Right. So coming down to the next one. It is again this one is that the same organizers are working group chairs. So the first, that's just the to do. So the. Yeah, I've just put the to do is to give me the, and also to put sort of little comments and say who, what are those views so that's just me to remind me something. Okay. I think if you use the same phrase. But for the first one, I think the second, the second who might just be working group in that paragraph. The second who just might be working group. The years. I would agree with that. The leaders are, are we going to take to the whole. Okay. I could say, okay, the working group. So I think the 1 thing is, and this is not to cast dispersions on anyone. But if we, the way the working group works as a whole is basically anyone that shows up as part of the working group. And someone could stack the working group if they were, they knew that they were going to be challenged that their membership was going to be challenged. They could just have a bunch of people show up and suddenly, you know, vote against that. I'd be inclined to think that the chairs would do it. And the chairs would probably as a matter of process reach out to the group to get some consensus but ultimately I think it was responsibility would fall on the chairs. Yeah, so I would say the Oki do the Oki do right the okay D working group. Leaders might determine that the offender should be barred from participating. So after the word group leaders. Because we may eventually change it from Charles to something else or whatever. Yeah, so the working group leaders might determine. Okay. And again is this working. I mean, this one's difficult because if you have an online. Yeah, online events. So I think this one goes, this one goes back to the working group leaders and organizers. Because it may be the organizers at an event that would be here so I would go back to the original phrase here which was. Working group leaders and organizers. We've less to leaders anywhere. No, yes, there is a document. It's actually in the community repo. A really out of date document. I updated it a couple months ago. Okay. Yeah. Yeah. So are we happy that. Looks good. It's that one that I've just changed. I, yeah, I think, yeah, that's this works for me. Nicely so thank you guys for getting this done. Can we do it as event organizers and working group leaders will be happy as opposed to. It seems to flow a little bit better that way. Yeah. Yeah, instead of the or I would give you that. Perfect. So I have a PR. With the code, with the draft of the code of conduct. You go to docks.okd.io. Do we need that any longer? Nope, Brian, you were thinking no, since we're going to put it in the, in the main repo, right? I think that's what you were thinking, right? Yep. So I can push this one now. Oh my goodness. That only took me 2 years. 2 years at least based on my PR. This is your PR with the 4. I added the. I added the email address in that came from Diane. And then those 4, 4 versions of those 4 words. Then it's exactly as your PR is Michael. So after contributing. You've contributed a lot. Oh, Michael, thank you. Okay, so that's me. Fantastic. That will go on probably shortly after this meeting. Excellent. All right, next up is. The operator catalog. Start filling stuff in in Christian's issues. I haven't seen anyone add anything yet. Someone linked to. That issue. And it's, there's like nothing there that they were linking that the link is from. I don't know what that's about. It was probably just me taking note. In the conversation again, there is that there has been and we can get Christian next week to update a little bit. There has been movement. Internally at red hat on, on discussing this and getting it done. So it is moving forward a little bit, but Christian or Vadim, whoever joins next week. I'll make them give the update so I don't miss speak. Yeah, there was an addition on the 20 or 23 days ago. Of the web terminal. And that it occasionally appeared in the docs, but it'd be great to add it to the community operators. So that's another one. Be mindful. Let's see here. So reworking the base repository. Brian, have you made any PRs? I have not yet. I was on vacation and I just got back Monday, so. No, I haven't. I've been trying to get my head around what's in there and to actually separate some of it out. I think we're going to need some guidance from body my Christian just to actually work out what's still current because some of that that was added quite a while ago. And I know there is some movement to adopt the formal fedora process and move away from Vadim's repo, but I don't know what the status of that is. And to be honest, I don't quite understand everything that's in that read me. Yeah. So I started looking at it, but I think we're going to need some input from either Christian or Vadim to help with that. What I would like to do is get Vadim to I know he's been pressed for time and did he make it to the main meeting last week. No, he was in that he was ghosting us. He was in the back chatting Christian answering questions, but he couldn't come online. He had another meeting. Okay, what I'd like to do is to just pin him down to meet, and maybe we do it on video at a different time, but at a walk through of the build process. As it stands now that they're upstream in terms of the meat machine config operator the MCO. So that's a recent development and it would be nice to have Vadim actually walk us through this on video for posterity. So that we all sort of understand the process as it is today now that they've made some of these changes, so I'll reach out to him and see if we can schedule something like that because working on a document with him. Like write that out may not be so great but if we can get him on video just talking about it, then we can write a document ourselves and sort of, you know, have him look it over and make any tweaks and stuff. We want to try to avoid putting too much work on him. New business. We need to do a press release for the 4.10 GA that just was completed as of this morning, I think it was, or maybe yesterday morning. Diane, can I trouble you to sometime this week we resolve the Twitter. Yeah, I'll do that today because I've got to set up bit warden and I'm in a quiet place so I can actually get that done today. Right. Give you access to that. Who wants to take a swing at writing the press release for 410. Okay. D4 10 GA. Is it a press release just a paragraph? Well, just a paragraph early. Yeah. Is it really a. Just to keep the naming. Is it announcement that we put on the blog on the site? Yeah, because a press release at Red Hat and so many other things. Yeah, sure. Announcement. Yeah, yeah, for sure. When is it going live? Given the conversation at the last main meeting in terms of versions. Right. Then the thing is, is that apparently. The links were wrong that he sent out on the working group list, and he had to like respond with new links and stuff like that. That's a good question. Let's find out when it is. Maybe let's just wait until it is actually. We don't understand anything out unless people can actually go get it because that's going to be a trigger for them to go. And do something about it. And if it's not there, they'll just forget about it and not come back. Open shift proper is delayed. Yeah, until the 10th. Is it? Okay. We should at least get the text together for a little announcement paragraph. So anyone want to take a stab if they don't, I'll do it, but. Maybe as example, 4, 9, 4, 8. No, we, we haven't, but what you can do is look at what they do on the open shift. Combo announcement and just make a skinny version of that and and link back to that too. Michael, if you could do that, that would be fantastic. Okay. And this would be just something that can fit into a tweet. So. Or do we want to, Brian, are you thinking that you'd want something more substantial for the website and then a tweet just condensing that it's up to you. Um, it's difficult to know because. So much of what ship with a new version of open shift, a lot of it comes in the operators. So, if you look at all of the developer stuff, we don't get that in, because it's all part of the pipeline and the GitOps. Operators. So. I think sometimes it's difficult to actually work out as a user rather than as a member of the community. It's difficult to work out. What do I get? What am I going to get in? Okay. Because what's what's when we get the operators, I think we're going to be in a much better place, but I think until then. It's a little bit like, well, what will I notice in terms of what I can do today? And yes, there's usually UI updates and there's maybe new section. And if anyone's on a particular platform, the CSI storage stuff is probably going to be new. If they're on a platform that's not affected, I'm not. So, I think that that's one of the challenges with okay D okay D and I'm not sure it's catching that on. So what I would say is if you write a blog and, you know, paste it in a PR and assign Christian and Vadim to review it before you post it, like make them reviewers. Then they could maybe edit out what's what's there and what's not there because honestly I'm in the same boat as you are it's really difficult for me to tell what the differences, especially since I have not been installing it lately. So, or maybe do this in the inverse right a shell and then have some bullet points that are empty and tag that into it for them to just fill in the bullet points because they would know, ultimately, as opposed to us guessing, like just have them inserts that I'm sure Vadim would be like, this is going to be beneficial. This is going to be beneficial this this this. You know, that might be a way to do it. The easier you make it for Vadim right now Vadim's in the Czech Republic and he's got family and places that are not not safe right now. I'm sure. So, the easier you make it, you know, he's really responsive as he always is but that would be the best. I mean, so whatever you can do, but I think if you especially if we use get and make docs or whatever. Let's make use of this new system. Yep. All right, so what I'm hearing is Brian work on a blog post. Michael work on a tweet. Is that right? Okay, Brian, are you saying that you know, that's fine. No, no, I mean, I'm just interested that this has gone from if no one else would do it, I'll do it and all of a sudden Michael and I have now got it. I'm joking. I'm joking. I'm joking. Well, I mean, in terms of the Twitter, I wasn't going to take on the blog. Yeah, I think I think the tweet thing. We're going to give Vadim access to the okd.io Twitter as well as Jamie and myself. And we can give it to Brian as well. We can just have a bunch of people. You know, do the blog will be one thing. But each time a release goes out, I was going asking Vadim just to send out a note on Twitter. That's just a standard. I did one or two early on when we first set up the thing. It's not the full announcement, but it just lets people start paying attention there or something. And so there'll be a differentiation. There'll be the release tweet and then the blog tweet, you know, the descriptive one. I was doing what? And Vadim is doing the release tweet. And when and if you get the blog together, then tweet that log. So, so Michael, you can sort of hold back for a second until the blog post is done. It sounds like it sounds like Vadim will directly do the release tweet. So you don't have to do anything yet. Yeah. Yeah. Not yet. I will do a blog post. Brian doing the blog post. If you want to collaborate on it, let's let the people who are doing documentation stuff decide amongst themselves what they want to do. Okay, so I mean, if Red House going to put out sort of like an official, I think we use that as the starting point. And then as Diane said, we cut it down, make it maybe a little bit less formal, a little bit more community friendly. But then we also need to then pull out the features that are operator based and on delivered. So if you have that text, Michael. Okay, you don't. Okay. It hasn't been posted yet. Okay, so when that's posted, I was just going to think that Michael has access to the pre-release version. When that comes out, I'll grab it. And I'm happy for you to sort of collaborate and tell me that my grammar is wrong and spelling is rubbish. Sorry, I just want to go back one. Just talking about that. Do we have clarity on what we want in that Christians issue? In terms of because we keep saying go and update that issue. But when I look there, there's like a huge list of stuff that's not included. That's upstream that's not red hat related. So I'm just doing what we want. In terms of what the working group needs. So I think what we should do is, is maybe put in a comment in that issue. A prioritization. I think would be helpful. So if we look at the at. Pipelines, what would be another one to get ops one. What would what would be logging right so pipeline get ops and logging are probably the three most popular. I think. I think. For virtualization, they also wanted the storage one. Right, right. And I would quite like the eclipse chair of the already workspaces. Well, so let's tease that out out of because there's like 25 entries there. Let's tease out like the top 5 so that we can provide some feedback to red hat. Who has taken the initiative to do this community catalog or this specific catalog, I should say. Let's provide them feedback as to what we think is the most important. Then, whomever can take that back to the group that's working on it. Does that sound right? Yep. And are we clarifying that it's just the red hat. Provided operators. We're not going to. Yeah, we can because ultimately that's what it's going to be for now. Yeah, I was going to say, are we going to try and engage with upstream communities and say, get the. They're like the project key. Into the catalog where that is a community project rather than a red deliver project. I think we could, but since this is the 1st iteration of the catalog. The easiest will be probably red hats. Offerings and then maybe phase 2. We go and start because then you will have something that you can say, hey, look, there's this thing that exists. It's in OKD. We would like you to be there. I think that helps make the case. Yeah. I mean, another approach is I go and find an OCP cluster, go look at the red hat catalog. And then we pick from that because it's the subsets of the official red hat. I've got to give you a list. I can give you a list of operators right now. I've got a bunch of 410 and 410. Okay, I've got I've got them at work. I can log into the word clusters and yeah. Well, if you can do that, then yeah, do that and then just pick them out. My votes would be for logging. And pipelines. Right. And get up. Yeah, those 3 are the most important in my mind. Yeah. Yeah. Okay. That's dealer conversation real quick. Yeah. These, this is these lists are operators that are not in OKD code. They're not in OKD. That's right. Yeah. Did they not be documented? There shouldn't be documentation. There shouldn't be any OKD documentation. Because they're not you. What comes with OCP comes with pre installed red hat licensed catalogs. You don't have entitlement you don't get to an OKD. We don't get those catalogs. And now you can certainly enable the catalogs and put a trial here, which means you do get them. But I'm not sure how legal that is. Yeah. So for example, I'm looking right now and installing open shift logging is in the documentation. Yep. This is the scheduler web terminal. And I think pipelines is in there as well. Yeah, I think it is. So, yeah. So here's logging, for example. And yeah, it's, it's not available. It'd be great if it was, but and by available, we mean, and this is something that actually Christian Hernandez brought up to me. He's like, well, you can install it. Are you asking about, for example, the GitOps being available in the catalog directly in the community catalog. And it was like, yeah, we want it to be in the catalog, not it's supported to be installed from the repo. You know, by installing the CRD or anything like that, like we actually are saying it should be in the OKD catalog. You know, if the operator is not available, all that functionality is not available also. Correct. Not, not unless you go and do some stuff. And to install the catalog manually, which means you need to go and take the upstream, build the operator, build the catalog, install that catalog, which isn't trivial, which isn't trivial. Yeah, and if you look at the documentation, a lot of the documentation, for example, what I just linked to is installing open shift logging and it's actually installing it from the catalog, which. Yeah, it assumes it assumes you've got access to the, to the red hat catalogs. Yeah. And we can make a list of those that might be helpful. We'll put separate documentation PRs. Well, I'll add that to the do to do is to help Michael locate these things to pull them out. Until ideally, we can put them back in or modify them in some way to be able to put them. All right. Does that answer your question, Michael? Yes, it does. Okay, excellent. Absolutely. Okay, so now we are up to. New business meeting. Okay, so we talked about. And I'll change that to announce minutes of press release. So now we're up to meeting docs. The. The new repo is active. Diane, you were given a. An invite and it expired. So check your email. There's a new invite for the new repo. And, Michael, what is your. Handle off that you would like to use for okay to the same handle you've used elsewhere in. Okay, yeah. Okay, and that's my Burke. No, it is not. Oh, what is it? Michael dash Burke. Amber 9781. Okay. Difficult question nine. No, no, I'm sorry. Michael M Burke 5678. Got it. I found it right. All right. You have been added sir. Okay, so now everyone has has. Invitations or has accepted them to be owners in the new group. So now we can start doing stuff in the new group. What is the thought on documenting meetings? Do we want to stay with HackMD? Or do we want to do actual. Meeting minutes or maybe pull them out of HackMD. And put them into GitHub after the meetings. I don't folks want to approach meeting documentation. And this would apply for the main meeting as well. Obviously. Yeah, I think if we could switch over to make docs, this would be a good time to do it. Yeah. If everybody's willing to do that and take that. That's my opinion. I mean, it's also what you guys want to, you guys are ready for that. And you want them to be part of okd.io link it in there. Yeah, you want to separate separate place. I think link it into the okd.io site. Yep. Okay. That's doable. Yeah. I will be out the next meeting. So. Diane, do you want to take a crack at it for the next meeting or do you know, wait. 2 weeks until the 1 of it. Let's wait 1 more week, week, week then and do next week's in the HackMD so that we're all on board and we can announce it then that we're switching. Make sense. Do we want to page page per meeting? That's probably not a bad idea. Yep. Okay. And next up is, are there any issues or pull requests that we should be aware of Brian? I'm just going to look now and not that I'm aware of, but I'm just going to have a look now. Issues. Nothing since the 1st of Feb. Well, now we can just review the task list. I do have. Sorry, I just have 1 more thing. So I've been working with Brandon. Who is the web. Designer. And he's taking a stab at. We're sort of judging up the styling of OCD.io. And so he's given me access to his repo. And he's he's actually gone and updated the colors. So hopefully we should be getting a new slightly improved look and feel with with better styling. And so I'll keep your data on that, but I just wanted to sort of let you know that that work is ongoing. Okay, so let me put this on the notes. Your website sign. Brian is working with Brandon, right? Yeah. Fantastic. Okay, task list find out who is behind OCD LinkedIn Diane. Yeah, I put in a request to the folks who track those folks down and I haven't gotten an answer back yet. So it's a good reminder. Because we don't want to get in the business of takedowns. There is someone at Red Hat who was paid to do that. Right. Okay, so next item up is in process, a call out for YouTube content. I do have the playlists organized better now. And so I will be. And once we get the once I get the get credentials, I'll be able to put something out. Talk to Diane about it. So we talked about a little bit. We haven't talked anymore about it. And machine OS repo discussion to main agenda because I wasn't at the last meeting that probably didn't get added. But I can make sure that's on the agenda for the next meeting, like before I am not available. Move community docs of community repo. That's Brian. Nothing yet. I'll do that this week. I'm sort of getting back into being able to do stuff. So, I'll do that this week. And try registering with matrix. I haven't tried. I'll give it up. I don't think it's going to be a go to be quite honest. I haven't even gone there yet. So. I did reach out to Mohammed for our security liaison work. Haven't heard back yet. Mohammed is like seven hours ahead of me. He was on our last week's meeting. Oh, okay. He was on our last week's meeting and we said that you would be touching base. So he's waiting for you to touch face. Okay, my son is like a message and I also have linked in so. That's what it Diana, are there any upcoming events that we should know about. There are many. But the big one is okay. Okay. D presence at. E you in Spain in May. Sounds like both Christian and Vadim will be traveling at the very least Christian will be able to be there. So we will probably try and schedule some in person. Meetup type. So I will get the next meeting I will call out and see who else is going to Spain with me and Christian and see if we can't set up a meetup. Oh yeah, Michael, everybody volunteering. It's funny. I don't really want to go myself to be quite honest. I've been there a number of times and I love it and it's beautiful. I'd love to let someone else go. What we're going to do a commons gathering there and we will do some, it will be a microchip presentation there that will be obviously using okay D as well. So they'll, they'll be a good presence for okay D there and as well as that so I'm going to try and see if I can find a space to do a meetup for okay D folks there. We'll see how it that works out bases at premium there. Diane, did I see that summit has been announced. You might have I haven't. I'm going theoretically. So if you see it announced let me know I'm on the hook to go so I haven't seen a date. May 10th through 11th. A location. It's in Boston. I haven't seen. Yeah, it's Boston again. Yeah. I will. Turns out I'm going to be in the Boston area. So I've been ripped into going. So, I was moderating the lovely place to be in May. I know. I went to summit in Boston. What was that three years ago? Yeah, it was nice. Okay, so that's events. Is there anything else we need to talk about before we. Going going on. All right. Well, thank you so much folks for all of your time and efforts. And see you at the next meeting and I'll check in on tasks and prod folks along. Just to make sure that we get stuff done. Yeah, I'll try and get all the Twitter stuff done today. But he's asking for it too. So I am. And that's social media people really want it done too. I know. Yeah. It's up. I know I'm going to everybody for your hard work. I'll reach out to the person who twigged me on Twitter and make sure she gets a review of it. And that's something actually we can tweet out as well that we now have it up. We should now that just so we know that. We should link to it because the code of conduct says we should link it at every event. The URL. So we probably need to add that as a. Agenda page or a. I don't know whether you put a label on a meeting. When we do. When we have the minutes. At the header when we put the dates, we can maybe put a little on hyperlink in there. But we've seen that done so that if you, here's the date. Here's the code of conduct and then hit the agenda. Don't be just doing that. That would be fine as part of the new make docs initiative too. So. Where is it on the site. It is in the community section. I'll close it. It will be up in about. In about 10 minutes, but just so you know, if I just show you, this is my developments environment. So it's local host. So this is where I do all the editing. I can preview it locally. But if you look, it's actually under community. Yeah. I assume you get rid of the placeholder. You know, Katie. There is, there is no placeholder now. It's that's where it's going to be. So the site will look like this. And then again from the community, we've got the code of conduct and we got the link to it there. And then this link should be made visible at all events. Gorgeous. Excellent. Thank you for your hard work on this very much. Appreciate it. Take care. Have a good day. Bye. As well.