 If you could put your name in the document, that would be awesome, name and affiliation. And so, the agenda is sort of collecting what we've been talking about, and yeah, please feel free to add stuff and sort of formalizing something that we can work with moving forward. And folks are putting their names here since they're such a small group and we all know each other. I think we can skip introductions. So, basically the community support text, there's an example of it in Slack. And we may want to refine that in some fashion. And one thing we're going to want to do is figure out where are all the places where it needs to go. I'm going to share my screen while you talk along so we can have in the minute meetings the screen because you were unable to share your screen last time. No, I can share my screen. Okay. Why don't you share your screen while you're typing there? Oh, oh, you know what that was actually let me check and see if I can because that's right. I forgot I'm not. And I think that makes it easier for people who are who might be watching this afterwards. Right. Let me see if I did enable that. I did. Okay. There we go. Yeah. So, okay, DIO website. So, yeah, so the one of the things that we might be able to do here real quickly is just knock out some of the places where we would want to put that text. So, I'm thinking the website, someone already started there read me up read me.md in the repo. And what else? What other places would seem we've already got it in slack, but we should let's put it in the, in the message that comes and description with the OKD Google form. So groups, the groups.google form. Oh, yeah. That's the other place. Where else? We don't have a Twitter account. No, we don't purposefully. But probably because then I'd have to maintain it. We use the open shift one. So we might. I think because it's, it's so tied directly into open shift in terms of promoting it. Okay. The might. I don't know. Period. I don't have to worry about that one right now. Are there any other places. There are places that we can think of where the community support text would be a helpful place to put it. Well, there is. And I will keep up, keep you guys posted. There is a movement afoot to redo the community links. On open ship.com itself. So there might be, depending on how I do it, but on open ship.com, you go to, let me just see. Find it here quickly. You go to open ship.com. There's a dropdown for. Community. And one of them, one of the links is. It takes you just, it just takes you straight to okay D. So, but there is a movement afoot to reshape that community landing page on open shift.com. So, when we get that done, I, I'll keep keep an eye on that and see if we can add some verbiage there. There any other place that folks can think of and doesn't have to exhaust all of our resources. Now we can ask the greater group to next week. I think this is a good start. Hey, the next thing to sort of come up with a list for is labels for member interest. So this came up in terms of creating subgroups for people voicing if they want to be involved in support, you know, part of the more direct support group, you know, the people that would get tapped if there's a particular type of question, etc. So what are some of the labels that we can think of for interests? What are some of the labels that people might want to associate to themselves. And this would be so, for example, in the attendance document, someone could put, you know, like this and then be interested in support. And, you know, documentation, etc. I think that we could put in one one label, yes, support, but the other one could be something specific to the, like Fedora Coro s, like an F cost person. Okay, there we go. F cost. And then the different to me, it would be helpful to know who's who's willing to talk about deploying on VMware on different on the different deployment platforms. Yeah, so you have to distinguish UPI versus IPI as well. Yeah, in particular VMware. Yeah, so so I think that's that that's that that would be key for me and then the documentation. And one category for I don't know what the word is, but maybe Bruce, you could come up with one public speaking, like people who are willing to promote evangelizing. I guess that's where evangelizing. Well, we'd all be evangelists. We are all evangelists, theoretically, is there maybe a better willing to, like, if I meet up.com region, I can tap them to go to what's, what's a good word other than evangelist though because we're all evangelists so like what would be a word that's Then perhaps just public speaking. Public speaking, yeah. I think I'm going to be able to speak by Diane. Speaking, and public references. What do you mean by that. Well, I'm trying like, like at you, Mish, you guys have a deployment of open of okay D. So. And I'm not sure whether this is member interest, but I don't know the other forget that one for now because that's something else. I'm thinking I'm trying to think the other thing is workloads. So we have deployment platforms that we're specific about, but like someone might be a data science person, someone might be. You know, a teaching like an edu thing so like a distinguish on. Specific workloads like automotive or. Edge or thing, you know, those different categories. Hi, Michael. Sorry, I'm late. So maybe I'm thinking with these types of things, it might be better to have. Maybe a profile for each member that wants. Like, and we have like a profile page where folks just add. And this would be good because we don't actually have a list of working group members, like a list anywhere that's like these are the working group members. And that's because you can drop in and out, you know. That's an interesting thing to say because all it takes to be a working group member at the moment is to join the Google group. Right. So. So there's a distinction between, I'd say. Active participants in the working group, like people who attend meetings, which is why I take the attendance people who consider themselves. Enlisted or subscribed to the working group. And maybe co-chairs like so 3 levels of that in. Yeah, and I, and I don't know exactly how to, how to break that down. But I think there are a lot of, there are a lot of lurkers and that's not a great phrase for those, those lurkers, but trying to get them. And that, and that brings me back to a bit to the public reference, like willing to say that they are, you know. And end users, you know, of OKD, they actually are using it in production or. In home labs or wherever it is. And maybe one of the other categories could be home labs. So besides. Because that seems to be one of the most popular. Yeah, now Christian did link to a. A document cheese I didn't grab the link. I'll have to dig through the. The notes, but there was a link to something that was in the charter of the group to like people having different like. Categories of interest or whatever, but I guess it never got fleshed out. So we'll do this now and then I'll take a look at that link when, when I get a chance and make sure that it aligns or point out where it might not align with what was done initially in the. Charter for the group in terms of these labels. I think the other thing at the only other thing I would add here to call up because it's such a popular topic is home labs. The people for home lab and we have deployment. But I think I would call out specifically home labs. Yeah, that is a very hot topic. Yeah. So that so that I would leave it at that for now because I think workloads has to get expanded and we'll have to figure out we have the taxonomy document for. Platforms, but the other thing that I wanted to cover, I think I shoved it into the was the pair review. And I don't know if I know Bruce is doing double time and Michael's here. But I'm wondering if Mustafa and Bruce, if you've got any more work done, or if Michael, you saw any more tagging by Mustafa. There were four or five in that initial push in the initial push, but did any more get added after the fact. Yeah, I know Mustafa was going to go off and work on it. And I didn't check up on him. I haven't noticed any emails. I'll go back and take a look. It should be enough to look in the issues list. And see if there are any because I just, you know, I don't want to. I don't want to drop the ball on it. I do want to keep tabs on it and see if that worked for you, Michael. And I did not have access to add any labels to it. And I'm wondering if you, if you have access Michael to add labels beyond. Yes, like, okay. And if you did that, yes, I did. Okay. Can we put a few links into this document of some of those issues, those four. Yeah, if anyone wants to add them go right ahead. Michael, you have him here. I go find them just second. Oh, thank you. And that way we can. I'd like to use the same approach you do in the main meeting Jamie and walk through those issues. And see just see what the status is of them. My concern is that Mustafa, I'm sure is now getting gobbled up and worked on is working on a number of other projects as well. Is that this drops through the cracks. And I really wanted to make sure that we had a good process in place and then try and do that. Hack the docs day sometime this summer. And the other thing that I had Jamie, you should get an invite. Your optional on it to come to. Basically, I think it's she's Mustafa's boss is has a whole. We all know that they have a whole swath of other folks that they want to run through this program and get them up to speed on using okay D and Shalafi is her name. I'm not sure if you have an invite in your inbox Jamie, but I asked them to include you in the they want to have a conversation about how to do this. And utilize those. They're called customer facing engineers CFEs. Did you get an invite. When would that have come. It was just today early this morning. So, I don't see it, but I'll check my spam folder. Okay, and I'll just add you. I'll just go check now and add you to the meeting. Early morning me on 30. Yeah. Okay D strategy and CFE interlock. And afford this to you. Just that you weren't on the invite so I just resented with you as in just a note saying that you're optional. If you can't make it. That's okay. What we're trying to do is get them to sync up with us and then come to the next meeting and make sure we're all on the same page here. But not waste the demon Christians time or Charles time. Did you guys find any of those links or am I just looking in the wrong one in the chat. Okay, the only ones that were actually labeled or tags. Yeah. Didn't label the issues and I go my PRs. Yeah, we couldn't add that was part of the problem. So, and we haven't solved that mystery yet. Not sure we can. That's what I was asking earlier. So you, you aren't able to add labels. Yes, I just, I did not label the issues I labeled my PRs fixed issues. Okay. There's those. There's about four of them in there. Try and capture them all here. No, maybe there's only three. Before I did, I was just about to push paste that one too. There's only three in the dock now. Yeah, so no further work has happened. So I'll ping Mustafa and see. No, here's the other one. These, these are the four. So, so what I, I really like Jamie the way that you run the other meeting and using the issues. Approach like looking at each of these and seeing what's missing. If it, if it's been fixed and just walking through them. And I'll ping Mustafa and see if he's had any. And not able to do any further work on it. Okay. If we could walk through each of these and maybe and get a status. Yeah, let's start with this here. Okay, let's start with the 1st 1. My screen again. Okay, deprecated features 1. Close that 1. Yeah. Oh, it's closed. Okay. Yeah, it is closed looks like. Okay. Next 1. Did not mention our costs. Okay, I think that's it. Yeah, I mean, that's pretty straightforward. Cool. And this one's still open. And he hasn't responded to your request. So this is installing a cluster. So, yeah, so I think we need to response on that before we can. Yeah. 18 instances of our costs in it. Yeah. Oh, yeah. Yeah, I wasn't sure what the image name was that you pulled down. Yeah, so I'll just, I'm just going to ping him in Slack now and see if he has Bruce. Do you have an answer to that? I, I don't. I believe that that was the one where there was a. A long template that for installation. So the idea was that you would have to update it and. Test it. Before changing the document. So that was that was going to be a bit. Not trivial. Because if he, if he's not able to do it, that's what I'm. You know, if he's just, if, if the mode that we're in right now is that must if I can only go through and tag them and find them, but he can't finish them. Then these are low hanging fruit. That brings in next week's meeting and. See if we can't get someone to take it on. Yeah. So let's look at the other 1 to is the other 1 similar to that. Yeah, I didn't expect them to stuff that to actually be able to fix all of them. I think there is some advantage in just opening issues on them. Yeah. And then somebody else that can go in and try out a fix. And of course, there were a few of them that were. Easy documentation changes that you probably didn't have to test. Yeah, there are a couple I could push right through. I was hoping that even could just sanity check them. Right. And so is this 1, this 1 still open to example is incorrect. And El Michael was, was going to do something on it. But it doesn't look like it. Doesn't look like yet. And I did in the chat post that that is it's. OS ID, I think fedora was what we came up with that it should be. Close this one too. It's closed. The 1 spot. Close this one. closed. So, Muhammad. I don't know what your interest is in helping out here, but and if you've done deployments of open shift or if you're part of the customer facing engineering team, or are you a red hatter. Hello, I'm, I'm not a red hatter. I couldn't participate in the work. I'm actually part of the community. I successfully want to play them. Okay. I guess. And it was after 3 months of trial and error. It was so hard, actually. And I actually get stuck in for a while. And that's why I'm. And I don't know what the sort of. Work should I put into this group? So that's why I actually, I guess it's my 4th. Session that I'm cooperating. But I don't know what should I add. To this community. Yeah. So, I think you have a valuable point of view. To be quite honest, because you're so fresh to it. So. And as we pull out tease out these documentation things. It might be. One way you could help is helping us find the errors in the documentation. And that's what we're trying to. And I know some of the low hanging fruit is just. Simply incorrect late incorrect use of the word. Rel Coro s that was the thing we were going for with Mustafa. And Bruce. Last week. And so just finding any references in the docs. Okay. Where they incorrectly. You know, say use rail Coro s and they, you know, instead it should be. So that was that, that's the test. Of this process that we're iterating on now. So. If, if you wanted to go into docs.okd.io and even log find, find that. That would be great using this format that we're. We've been talking about the past couple of weeks. That would probably be a good way to. Help us a little bit. And get get your feet wet. I was hoping you were on the customer facing engineering team. So, and then because this Jamie is probably. The easiest thing to ask Shalafi on Thursday. To get people to help us with as well. And I have an outstanding, I need to write a little blog post based on. Most of us experience on how to do this. The thing that. And that, that could be your template Mohammed for going and adding new ones is what I'm, I think I owe everybody is a little blog post on okd.io. So, you know, help us hack the docs kind of thing. So I'll do that later today and get that published in time and share it with you. Questions I have, I think are still from Michael Burke. Because I think it's. Since we're not able to label things. If we simply just put in brackets okd. And in the title. Is there anything else we can put in to the description to let you know that it's, it needs to be labeled as documentation so it shows up on your radar I'm just trying to. I don't have privileges to label anything and you seem to be the only one. And like Mohammed couldn't get it and Bruce probably won't get it. You know that those kinds of privileges to label things. What is what is it? What is enough to get it down your radar to look at Michael. Think just assigning it to me. Send me an email. Okay. So the slash assign Michael Burke and Diane Mueller works. For you. Yes. Okay. And then can we ask you to add the 2 labels and I will do that. The next step so for these 4 if you even if you can just go back in time so they're good examples. Okay. Sorry, what are the 2 labels? Okay, the only and. And documentation. Oh, okay. Yeah, so that it's clear that it's documentation. Done. So that that would be good and you do that then I'll have those 4 ones and I will use them as examples in my thing and I might clean up the titles on a couple of them. Because they should all have okd in the brackets and I think one of them does not. So. But yeah, that's a pretty simple process when you find something and. You know, then it's. And we can move them forward, but I think there were I first you counted at least 20. Odd references and we only have 4 listed here. Yeah, well, I mean, that was approximate I didn't count. And. As I say, my understanding was that the point was that Mustafa was going to. Take that as a task to finish that off. If it turns out that he doesn't, you know, he doesn't have time to do that, then you could just send it back my way. Yeah, and maybe, and maybe. And that's that's the simplest one and what I was trying to do was get all of those ones done before the next real working group meeting. We're not, not that we're not real today working group meeting whole working group. Thank you for their correction there. Correct label. So that we could then ask everybody else and I'd have that blog post done. And we could do a little update there and ask other people to take a look at docs.okd.io. And use the same format. And then the ones that, you know, Mustafa can answer. So I suspect the one that you've got him tagged in there asking for deeper examples and the non trivial ones. We can ask people if they could take a look at them in the phone. That's, that's what I wanted to get through today. Hey, excellent. Let's move on now to. Are there any new projects that people want to add to the list? This is kind of a full plate for us right now. So maybe. These would be down the road. Was there anything else you can think of in terms of documentation. We should put on our radar. Well, it's not a new project. It's moving. Michael McCune's moving of the guides over under okay.io is still not completed yet. So I would say. And I'm not sure what the. Okay, I put that in. And have like a question mark for status. So we can get the status of that. Any other things that we should have. It seems pretty full, but. That's it. You know, it's the blog post is on my radar. I'm sitting in summit this today and tomorrow. So I ought to be able to get it done because the chat's pretty quiet. And I'm not answering too many questions, but I think that's that that's the next step. If Mike Burke is okay with. So we have all document out documented by blogging. And then it will have once we've shown it to everybody else, we probably need to find a place for. How to document how to document how to log an issue, a docs issue in the repo documentation somewhere. That would be the other. We'll get there when we get there. But I don't have any new projects and I don't really want any new projects at this moment. Anybody else. They really want. That's about it. And so we can give people back their time and let them go enjoy. The happenings. At the virtual event. And next week is the full group meeting. Same bat time, same bat channel. And then what we'll do is we'll have someone who was in this meeting. Sort of provide an overview of what we discussed and sort of report into the, to the larger group. And the idea would be that as. And at the next meeting, I'll be sort of walking through folks through the idea of creating subgroups with ideas as we have multiple, multiple subgroups coming be at the. Support subgroup or the documentation or whatever subgroups like each one would report in at the main group meeting. And I think that would be, that would be good and keep things organized as well. So, I'm just asking in the chat. Mohammed, if you don't mind, could you send me your email address and what I'll use you it for is a guinea pig on the blog post. And get your feedback on that. And because. And then. And I'll share it with Bruce as well. But that way, if something's missing or you, you need more detail. You can let me know. Diane, what's the status of possibly getting a slot on OpenShift TV? Is that move forward at all? Yeah. And we can definitely do that. So I was definitely there's Mike McHugh on there we go. Oh, I'm there. So maybe Mike can give us an update. Definitely we can do it. I'm thinking monthly on Fridays at the same time slot would be a good time, you know, once a month. And I was just going to bring it up again at the next full meeting. But yeah, depending on what you guys's schedule is that would be great. And I was also should have said I got a note from Joseph Myers who got his vaccine shot today and is under the weather. So, you can welcome today. Mike any update on the transitioning of the guides to the repo? Sadly, no update. I've just been swamped with kind of day to day stuff. I'm still trying to learn that framework. That's in the in the other side to like in the on the dock site to like push everything there. So I have an idea of how I'd like to put the content there. I just don't know the technology yet. Daytime stuff is just taking up too much of my processing power basically. All right, well keep us posted. Anything else you want to bring into our attention? We're sort of winding down. So. Yeah, no, I apologize for being late. Yeah, I am keeping track of that stuff. I would like to get a PR in there. It's just, you know, we, we just did the 4.8 release and our team is this is kind of extra detail. But our team is working on the out of tree cloud provider stuff that's coming for 4.9. So like right now we're under a crush to get all this out out of tree cloud provider stuff merged into OCP. And get all the tests and everything running before we get to the 4.9 release because that's like, we have some drop dead dates for that stuff. So like, unfortunately, I've just been kind of wrapped up in learning about that stuff and doing that. But I would like to get this stuff in there. If anybody knows, you know, if there's anybody out there who knows the framework really well and has time to like do those docs, I'd be happy to like pair up with them and just kind of like pass on whatever knowledge I could. But otherwise, you know, hopefully I could do something this weekend or maybe next week. I think Joseph pairing Joseph up with you would be a good thing. Once Joseph has some time. Yeah, I mean, he seems to know it really well and that'd be perfect. You know, because all the all the markdown docs are pretty much like ready to go from the guide side. It just needs someone to kind of organize them and put them on the doc site. And like, if I have a feeling it probably wouldn't take more than an afternoon to do this. If someone knows the framework, you know, it'll be really quick for them. It's just taking me a long time to like read up on the framework and figure out what mistakes I'm making along the way and everything. We will put a little note there to pair you up with someone. Good to see your face. I'm not showing my face because I broke my camera. But I will be back tomorrow and I'm just double timing in in the red hat summit. Directory today or community central stuff. All right, let's give folks some time back to their days. A lot of folks are sort of pressed for time. I'm pressed for time as well. So next doc meeting in two weeks next full group meeting a full working group meeting next week and Mike I was just saying that basically someone that was in this meeting will sort of provide a check in at the full group meeting and sort of go over what was covered here and stuff like that. And since you joined late or I don't know if you saw it in the channel, but here's the hack and the agenda document for this meeting that we just had. All right, folks, have yourselves a great rest of your day and we'll be we'll all see each other. I'm sure very soon. Take care guys. Thank you all. Thanks, Jamie.