 It started. We've got the slim crew here today. Diane had to step away for an all day meeting. So, and jump right into our agenda. And it looks like actually, I can take time. Brian Michael Bruce, can you put your name in the in the document here? Okay, you want to put the document in a chat just so they don't have to go and find it. Yeah. And Mike is not here to talk about this transition of the guide transition. Let me see if there's anything in PR. Oh, yes, actually. So Diane merged it 14 days ago. It looks like they did get the last little bit squared away. And so the guides now are merged into the okd.io. So we can actually list that one as completed. Okay, I had questions about the charter update and placement that I was going to ask Diane, but since she's not here, we. Updates to the okd.io banner. I did make the change to get rid of the recipes link. So now it is all just what is okd installation documentation blog and community. And why don't we actually, this seems like a good place to actually move and put Brian's stuff. I'm going to move our agenda around here because actually now would be a great time for Brian to give us an update on the beta site. If there is any updates. Yeah, unmute myself. So that always helps. Yeah, there is. Easy about doing this. Yeah, go ahead and show your screen if you want. Hopefully you can now see that. Yes, we can. Thank you. Ridiculously small. Okay, so I've actually created the beta on the okd.io. And this now does contain the site. If you look at the gate of actions are there and when you push, it actually runs the action. And that action will go into a spell check. It'll actually check all links. So just a warning whenever you do an update to the site, you're also responsible for fixing any broken links. So it checks all the links in the site and will tell you there any broken links. And then it'll obviously publish. Now the one issue I have is I don't have access to the settings. So if I go to mine, I have access to settings, which allows me to go into pages and configure. To source GitHub pages from the GH pages branch. So we need that setting made because at the minute. The GitHub pages site is not active. But I actually don't have access to the page. So if you look, we actually are creating the. There's a lot of branches in here. We are actually creating the GitHub pages site. So this is the source of the beta site. So it's all there. It's all working. But obviously until we turn on GitHub pages for this project. We don't get to see it. So I don't know whether you have access Jamie. I just looked and I do not. So let's add that actually as a to do. So we'll need to get whoever read had access to this to go and turn that on. Just then again, we can actually send them a screenshot of this page if you want. We just need the source to be GitHub pages branch. And we want the root and nothing else we can enforce HTTPS. And that's it. So in the pages section on the settings, just those two settings. And that will turn on the beta site. And then it'll also give us the URL. So that's probably just going to be the open shift dash CS GitHub.io. And then it'll be OKD.io would be the URL. So that's actually getting the site there. So every time we push code to the beta branch. It doesn't touch the main branch or the master branch as it's defined here. It's just this beta branch will actually kick off the GitHub action. To actually do that. So if I go back to my site that I sort of tried all this out. We do have some decisions to make. So this is what it looks like at the minute. Now I think we need to change this. I want to make this much, much simpler. This also uses bootstrap framework, which causes some issues. So if I shrink this, you notice that it doesn't necessarily work very well. The menu just doesn't work because the bootstrap is interfering with the underlying MP docs framework. So there are some issues in terms of just getting that reactive sort of content working. So we do need to work out what we want on the simple site. And then also, are these colours OK? I mean, I just picked from the home, I just picked these two colours. But I don't know whether this is what we want the rest of the site to look at. Do we want it to be different colours? I'm using red as the active highlight. So there are a lot of style issues. I've actually picked up the font and the styling from what we have on the current site. So I've actually adopted the same fonts as the old site uses. But again, there's a lot of sort of style issues that we need to discuss. And then obviously we just need to make sure we move the content across. Because obviously what you've just done, I mean, I didn't put the recipes there anyway, but the guides, which I sort of suggested belong here under the getting started instead of a separate thing. There's all sorts of things we need to. So I don't know whether we want to do it in these meetings, have a working group, a work session where we just go and get it agreed and sorted. Or whether you're just happy for me to come up with something, make it up as I go along and present it and say, do we like this? They go. So, well, let's see. I'm, I'm a little bit pressed for time myself or other meetings for like other meetings in addition to what I have Bruce. What's your time. Okay. You're okay. Yeah, I'm okay. Okay. The only thing that I know of that was important to Diane is to maintain at the bottom or to include at the bottom of whatever we did. The end user community part and the commons part is to have that featured. I don't know if it's necessary to be on the same. Front page to be on the front page the same as it is now, but it was important for Diane to have that to list those partners and list the community commons as something that people can dissipate in. So, well, yeah, seems that Diane, like this seems to be from Diane's standpoint, a dual purpose site with one of the significant purposes being marketing. In other words, a, like some new potential user sort of sitting around. You know, fat, dumb and happy. I can say that because I'm fat stumbles across the site. And they should be incentivized to want to install okay D. You know, after buying a bunch of hardware. And so, and then promoting it to the world. Right. And I can see that right yet. I'm not the person to advise on that side at all. Right. My interest is more on what's useful. And, you know, because I think like from the standpoint of a technical person. They will very quickly get annoyed by the marketing bump. And if there's not useful stuff, then they're not going to go back. It just makes sense to have it be a sub menu under community. Maybe the last item under community or something like. Yeah, I don't have a problem with the, with the homepage being marketing bump as long as it's sort of clear what you click on to get the good stuff. Right. I don't know, I guess we'll have to save that for Diane to see what she's partial to in terms of format and stuff. But I would say the rest of it, Brian, what are you most comfortable since you're sort of leading this effort? Do you want to do it in these meetings? Do you want to wrangle people for a separate meeting? I'll hand that to you and you can run with it. Yeah, I mean, I think the big thing is just to get a consensus on dialing color, the colors to use and do we want it. I mean, there is an option where we could have a dark mode and a light mode with a toggle switch. It'll pick up your browser's preferences if we want that. So these are all things that we can turn on. And it's a configuration thing. So it's not anything to do with writing the content because you write content in markdown. And whatever we decide is a styling will get applied to that. So it's not as if the decisions we make. I'm aware this. This is our community presence on the web. So I'm a fairly new member. I'm happy to go and sort of start throwing things up and letting people shoot me down and saying that's terrible and go do better. Yeah, I like that. Maybe we need a different color here. But if people want to have a say, I'm equally as happy to have a say and however people want to do it. At some point you're doing stuff that makes you a valued member. Yeah, there you go. Well, does it make sense? So, I mean, I don't know who else is going to be coming to these meetings right now. Folks are like really busy. And in the past, we've had like basically it's it's plus Mike and then plus. Muhammad Reza and then Michael and that's basically been it. And then. Drity. So really it's been this core group of people. Does it make sense Bruce and Brian for you folks to go off and and work and then just bring something back. So the larger group. Because there's going to be stuff coming up in these meetings that we're going to have to address in terms of some of the other documentation. Installation documentation and things like that. So maybe in terms of the design stuff. If you folks go off and figure out what works best and bring it back to the group and chances are unless. American time zone brand. I'm UK based. Okay, so that so that gets a little bit trickier to find a common time. What time zone are you in? Are you East Central? I'm a Pacific. So that's even worse. So let's go just like Diane. So eight hours apart. Okay. So yeah. I mean, what I can do is I can do things and put a comment in the slack channel or wherever and say, I've made a change. Go say on a and we can take it from there and I can, we can do it incrementally on ask people to the comment. I mean, the problems is people tend not to comment. And then when it goes live, there'll be an outcry of who did this. I don't like this. But I think I think that that you're the optional dark mode, light mode is good. Yeah. Accessibility reasons for accessibility reasons. Okay, I actually have. Oh, let me just check one thing with Bruce. Bruce, do you seem to spend a lot of time in the channel though? Well, basically, I turned off the notifications because I was getting one every second. Yeah. Most of them useless. Does it make more sense, Brian, for you to use the Google group and put something in the Google group when you make a change? Yeah, I can use a Google group if people want me to do that. That might be better because that's easier for people to retrieve if they can't look right at that moment. Okay. There's at least a trail that's easier to follow this. And my email is actually like my work email is public. Okay. Okay. Yeah, I can do that. So the one question I have and maybe Michael can tell me. I'm assuming I've got to remove this. Because if we're going to be GitHub pages driven, we're no longer going to be powered by Red Hat on OpenShift online. I'm guessing that would have to be removed. I know that any legal things that we need to put in like license or copyright or any of this sort of stuff that we need to be aware of. Because Michael doesn't know who do we ask to know about that. Yeah, there is no copyright or anything on here and most communities have a some licensing or copyright stuff in here. And I say, I guess I've got to remove that. Yeah, we'll have to figure that part out. And so do those, let's see, we've got the Twitter. Where does the Twitter go by the way? Does that go to the OpenShift Twitter? So that's the same as exactly what's up. That's the same as what's exactly on OKD.io now. It's the same. Yeah. But what does it go into? Yeah. It goes to OpenShift. Okay. Oh, and it goes to OpenShift Origin for GitHub. I just noticed that there's actually a link on the front page that goes to Origin instead of OKD in the community section. I just noticed that a little bit of go. Which one was it? And again, we go to the OpenShift Facebook page. So to say that we are a community driven project, we seem to be sending everyone to OpenShift. Oh, you know what? It's the Fork the Repository link that actually goes to the old Origin. Okay, so we need to change those. Yeah, that needs to go to the OKD. Yeah, because this talks about like 4.6 and above and... Okay. Oh, interesting. As of July 2020, the purpose and maintenance strategy of the repo varies by branch. Apparently Origin is used to sort of a jumping, well, I don't want to say dumping ground, but a jumping off point. So yeah, we definitely want to instead drop people into the OKD one. Yep. All right. And so yeah, we'll put that on the list just to find out about legal stuff. If Michael doesn't know, like what do we need to have in terms of any type of, you know, insignia for copyright or anything like that. I do not. I could look at what OpenShift has. I'm sure Diane actually knows someone that can give us an answer. So let's put it in that in the to do... Much safer. Yeah. And I guess just to go looking down further the agenda, when we actually do the switch, we can probably handle the inclusive language update at the same time. That's probably a good time to do that. All right. Okay, so I have a next item in terms of this, which is priority. What do we think is priority to move to the beta so that we can move the beta over sooner than later? Like, because there's a lot of sort of sort of crufty type stuff. What would be helpful to move to move into the beta so that we get a good sense of navigation, appearance, and functionality? The way I was planning is to get the beta to the state that we'd want the production to be at, and then simply just do a pull request to push the beta into the main branch. No, but I mean, in terms of moving content over, because we're not just going to... I mean, are we just going to take everything that's on the current site and dump it into the beta? Potentially, yes, with a sort of... Because I mean, we sort of have already gone through the site and said, well, we need to get rid of this stuff. So we looked at the recipes and said, well, that's going, that's old. So there isn't a lot on the site, to be honest. Yeah, I guess that's true. Well, I'll move the blogs across, I'll move the guides across. I think because obviously they went on since I did the fork. I know I rebased the fork on today, but I actually did the fork a month ago. So I haven't put any content that's recently been changed. So I'll try and pull all the content that's currently on the site into the beta. As you see, I've already sort of suggested new locations. I'll put the guides within the Getting Started section. And my idea is to get the styling, the colors and the content to be the state that we want it in production. And then when we all agree that it's at that point, I think we switch. Right, so should we put, so are we in agreement then that nothing new should be put in the current repository. I made that one change to the header, but nothing else. Are we good or is there any anything else that is an immediate thing to change until we're ready to go live with the beta. Yeah, so I actually rebased the beta after your changes. So if you look, I rebased the beta changes. There is no, there are no changes from where I did the rebase. So we should be able to merge the beta onto the master without any conflicts today. So ideally it would be good if we could not do huge amounts of change. Right. I don't know that we need to change anything else right now. My sense is that the people who wrote the guides aren't going to be coming back in the near future to update those. Well, I'm hoping that it's going to be a matter of maybe a couple of weeks, maybe at next docs, we can ask for approval time type timeframe. I'm not expecting this to be going on for months. Yeah, I think that we could conceivably have content changes. And that I don't think we've really looked at it to see. Okay, like all the information that people want to access frequently. Is it easily accessible. Like I will occasionally find new stuff popping up when I do a Google search. That I didn't even know existed, which is really, and some of it is stuff that Vadim did and put in markdown. This, you know, somewhere in the, you know, like. You know, the, the, the GitHub slash install slash. You know, if you go down a bit, then you find a fantastically useful. Yes, document. There's actually a build document about that's buried. That's about like how to build. Yeah, so like someone said, and I noticed like, like, whenever I'm on a different machine, I need to find the status page with the updates. I have to poke around. Right. And so, so things like that would be, I think are generally useful enough. They'd be nice. Like, if you go install, then there's a link right to it with a meaningful. Name so that you know what you're clicking on. I mean, the hope, the hope is that once this goes live, making updates to the dock site is trivial. Right. And anyone should be able to do a pull request without needing to understand middleman and how to do a full page web development. It's just going to be a simple markdown file. So my hope is that once this goes live, the changes to the dock site become much more frequent and we're much more responsive about saying, we should really add this to the docks or even to the point of there's a release that's got an issue, a known issue. Let's put that up as a known issue or release for a point X. And we can actually start making the site the go to place to find stuff and find the latest information rather than. I mean, looking back at the history. Okay, the I hasn't really changed a huge amount for quite some time. We're not using it as the, as the place where we post up to date information. Right. And it would be really useful to have such a place. I think, but I mean, I think, but again, I wouldn't throw in too many factors at once. Is there like, I think your plan is a good one, which is get what we have now rebased. And then we can look at the making changes to make it more serviceable. One thing I do have. Yeah. And one thing I do have Bruce to your point about very documents is. And I can actually modify the agenda to reflect this is further down we had an ongoing item. That was the name and scope of install that MD and read me that MD, because those are the ones where you want to get to the install that MD because that has the link to releases. And there's all that navigation stuff. I want to have that conversation with Vadim since Vadim created those two pages. Where are those pages. So, if you go to okd.io. Or sorry, if you go to the okd code repository. So, github. Okay, so it's not the documentation. Right. And this has been sort of an ongoing confusing thing is if you go to, yeah, it's slash open shift slash okd is the. Yeah, okay. Yeah. And actually there's some stuff that needs to get pulled out of there like those guides need to get deleted because those are the old ones. There. There's the troubleshooting stuff. Which talks about log bundles. There's the contributing page which talks about actually building okd. Like, I feel like contributing needs to actually get changed to like building okd is contributing in terms of the group can mean a lot of different things. Right. And, you know, known issues he actually has been updating known issues with known issues for builds and stuff like that. So my take is that this repo all of this content should go to okd.io. It, it deals that way because there's really nothing here that's like scripts or anything like that. I think the the guides might have a couple of scripts or something like that. But no, there's no it's all content. So my sense is that yeah I mean it should go like yeah even navigating through here I'm not seeing anything that isn't just some flat pages. Yeah, I think so. Where is the installed or md or is that in the. So it's if you go to, is it install md or what is it let's see hold on. We find it it's. The same page. Oh no it's releases so if you want to click on releases. So if you go to the getting started part. And then there's releases that goes to the long release page. Which, where is that in. Is he updating that in real time the releases page. The releases pages auto generated right. That's generated by the system. Yeah okay so the releases pages the is the GitHub releases tags so it's it's the yeah it's the right project releases rather than a content page. Right, so for stuff like that, does it make sense to keep it. That's got to stay there because that is effectively a CI. Not a documentation feature. Right. Let's see the nightlies page. But all the stuff in the read me. It's mixed. Yeah, it's like all over the place. Yeah, a lot of I think we need to refactor this ideally and put it within okay. So it's, it's organized and it's, it's easy to follow. Same with things like the FAQ. Yeah, I think that should be a feature of all kitty.io. And then obviously the. The log information. And then the contributing as you say it is a good source of information that should be there. This should be part of our documentation. So should we have a just sort of throwing this out should contributing be its own link up at the top, or should it be under community. Like where ultimately would we want contributing to be because it is different than installing right. I mean at the minute I sort of put it sort of into community. And then it's a, it's a sub menu in community. Does that make sense. That work for folks. Make sense to me. Yeah. Okay. Anything else on this topic. Oh, delineation of resources for work group and okay users. Diane was going to look into the working group guidelines and conflict resolution. I think we can post something. She's can't respond to that. Diane did want us to provide text for what to put in the Google. Description and to for what to ultimately put in the chat channel so that they don't like cross reference each other. Because actually the chat I think says to go to the Google group. It's mixed. I mean I think eventually if we can get the community page on okay d.io. Then that will be a good place to send everybody to because that will then in a more of a both way be able to say, are you an end user? Or do you want to contribute and these are the differences and this is where you go to do that function that's where you go to that function. But until we get that page. Stable I mean the current community page. Well right now the link goes to the discussion directly. So I would say that's probably the best place to send everybody to until we can. By the way, I did notice that Vadim is now actually closing down. Issues. That are not true. Val, you know, verified his issues and directing them to the discussion, which is, is great. Yeah. Yeah. I would support sending everybody to the discussions page. All right, that covers all of that. So, Brian, in terms of inclusive language update, did, is there anything on that ticket from those three folks that were assigned to it. Yeah. I haven't been notified of any changes. Let's see if there's nothing. No, those folks are still assigned to it 28 days ago. Response. So I would say in how long do you want to wait Brian before we ping them again. If we're going to move across to the new site, I can fix everything as part of that. And then as we transition from the current scheme to the GitHub actions, they're going to have to turn off whatever automation they have. And at that point we can just rename the master domain, which is the primary action on on that. I think when we do that transition, we close this ticket down. Okay. Alright, that's easy enough. Okay, and now we're up to Michael's first draft of the docs on. Submitting an issue on the docs Michael, do you want to walk us through a little bit shows we got. I mean, sure. I just started in Google docs. But unfortunately it's a red hat only Google doc, unless I explicitly invite you all in. I can find it. You see it. It's a decidedly simple little document. I assume people know what to do, know how to do these things. I just wanted to start by mentioning that the okay docs are built off the open shift docs. So any actions they want to take go against that repo and not the okay D repo. And folks need to file a PR. Directly against the documentation. I got a link that goes over to here and use. Is that the wrong page? What's the new button there? What is that? You can look into that. Or you can file an issue that should go right to an issue template. Sorry, this is our template. You create issues. And we discussed this I think last meeting. What types of changes we wanted to see listed expressly errors typos missing information product names, the operating system, blah, blah, blah. And if you do file a jeer issue here, the information to really home what the problem is or what your concern is and how to tag it so that it gets our attention directly. So tag me, sign it to me and Diane. And if you have permissions to label through the kind documentation label and that will get our immediate attention. Excellent. It's great work. And I'm assuming if people want to create a PR, I'm assuming they know how to do that and they know how to fork the repo. Sure. It might be helpful. Yeah, if we maybe just one link to there's got to be a document out there that's like some basic, you know, how to do pull requests, whatever, you know, so. Yeah, I'm sure we have something in our training docs that I can grab and throw in here. I'm even a link to some external resource. Yeah, I'm guessing this is eventually going to end upon okd.io. Yeah. That's pretty much it. Very cool. Any other feedback for Michael. No, just thank you. I think it's needed that documentation is what we need. Right. Excellent. All right. Create a build doc outline for Vadim. Brian and I have not had any communication about that. We'll do that this coming week. I've been just really overwhelmed with other stuff, but I'm being able a little more time to break away from that. And then so Brian and I are going to create sort of a set of questions and things that will form the outline that we want Vadim to fill in the blanks on or to point us to filling in the blanks on it. Well, I think we should actually combine that with the name and scope of install and read me. Yeah, some of that is some information already and some of it's filling in the blanks from there. So I think I think these two things go together very well. Yeah, I will do that in the agenda and go. And that actually brings us to we have any new businesses or anything else that's popped up that folks want to talk about in terms of docs anything else you've noticed that needs to be addressed or you'd like to see addressed or anything else that we should know about. I guess is just make sure that the C or C stuff is recorded. I'm hoping to apply, but I've got social plans on Friday evening and I may have to leave that C of C thing early if it goes on for the full two hours. Because I'm guessing again we want to write that up and get that into okd.io. The outcome of that. And again if somebody wants to do that, if not, I'll do that after the fact that if somebody wanted to document and write that up during the event and. But I just think we need to make sure that we do have an action to convert that video session into useful documentation going forward. And then as we do the automation post that event again that's then fully documented and yeah. Yeah, and I think it would be nice if we created a page that is a listing of all of these external events that we've had as opposed to hoping that someone sees it in the all of the listing of blog posts. It'd be nice to have something that's, you know, like, I don't know what we would call it, but something that has links to the videos for all of these things we've been doing, you know, for the past year and a half or whatever. I mean ideally we want to we want to YouTube group or whatever wherever we actually put them and actually have a playlist so we can point people at the playlist. So we do have an OK D playlist on the open shift. Diane gave me access so I actually have access to that's all the OK D meetings are under that OK D playlist so we can put our recordings under that. It'd be nice if we had another one specifically for somebody doesn't want to wade through the weekly. Good point. Like, why don't I change that then the OK D work group meetings and then just OK D like general stuff right just OK D OK D work group meetings and OK. Yeah, because that means we can then have like a resources page or a resources link. And then we can point at that that YouTube playlist. And then they can go and self discover all of the events that we've actually recorded. Perfect, I like it. Right, I will add that as an item for myself to do. Business. Change playlist name. The group. I think there is a group and create new playlist. And OK D. All right. Anything else anything else that we need to cover. We've got 15 minutes left. If there's nothing else then we can break early sounds like we're good. Let me know if you can't make the next meeting. Since we're running a little bit thin, I don't I don't want to get less than like. 3 people at a meeting, you know what I mean so if folks can't make it. Let me know ahead of time because then maybe we can reschedule or skip or something like that. Just we don't have everyone or 2 or 3 people sitting here waiting. You know, if we don't have a or basically it should be like, I guess, for people. This is probably the smallest we would want it. Yeah, I'm OK for the next stocks 1 I've got. A big academic kickoff meeting. Next week. So I'm going to see I don't know if I can come to the regular working group meeting but depends on if I can bug out of the other one. There you go. Oh, and Brian we are going to be recording the CRC and I'm hoping it only takes an hour. There's really. I don't know that you could take 2 hours with it because it is pretty basic, but Diane did carve out the time in case it does go. Yeah, I mean, if it's an hour, I can stay but. I am going to have to sort of after an hour drop out so. Yeah, I'm quite looking forward to that one. I think the interesting thing is. How do we actually. I've not really seen how we actually do work. Outside of the meetings, what is the mechanism of actually collaborating outside the meetings. Because we actually want to create an automation sort of project. As a result of this one, so I'm quite interested to see how that pans out how much interest and also how we're actually going to organize it. Yeah, yeah, I think it will probably be. I don't know. We'll see. It'll be interesting. So, but I'm definitely doing interested in helping with the automation. I know a couple folks are. I know you are so let's. Yeah, we'll probably tackle that probably at the main meeting the next main meeting. So probably next week's main. Probably talk about that with the demons. All right. Well, thank you everyone for showing up. I'm going to go ahead and stop recording here. All right, folks, I'll talk to you next time.