 Let's get started. No update on Charter. Update in placement. I've been busy with the other stuff. The shining star of the hour, Brian, BetaSite updates. Okay, quite a lot to talk about. So I've created a, hang on, which order are we in? Do the tasks first. Do the tasks first. So I've created an issue, which I'll put a link there. It's two, two, three, just to list everything we need to do. It's a bit of a fuller list than this one. The first thing I really want to do is just check that we're not going to mess up anything internally with Red Hat. There are a couple of web hooks on the repo that are active. So I don't know where they go, what they do. And as we do things with the repo, is it going to upset people and start firing errors or issues around? So I just wanted to be idea to delete, know if I can delete them or if they'll find to be left alone. But then I've got a list of things to do, which again, if we just quickly look at them, I don't think there's anything that... You can share your screen if you want and just navigate. Why don't I see if I can do that? That would be great. Share this screen? Yeah. Hopefully you can see that. I'll just make it a bit bigger, I think. It's readable. So yeah, these are the steps. The only one that I'm not too sure about is the DNS one. Yeah. So just so you know, I reached out to Will Gordon and Jerry Fallow, who I've assigned also to this issue just in the past hour. And they are going to repoint the DNS for us. But they'll now review your thing. So I don't think any of the web hooks that are in there in the site are going to be bothered by what you do. But that's my opinion and they put the hooks in there. So I'm going to double check with them today. Jerry is on check time. He's in the Czech Republic. So we got him early hopefully today, so we'll do that. But what my hope is by next Tuesday's meeting, we will have resolved and we'll be pointing to the new site. OK, so just so everyone knows, because we've called the repo OKD.io, when it her pages creates the site, it uses the org name and then slash and the repo name. So obviously, when you just point the browser at that, it thinks that OKD.io is a file and it doesn't go and add index or HTML at the end of it. So you end up with it not found. So when we do the redirect to OKD.io, I'm hoping that even though it's redirecting here, it'll still go and work. That's my concern there. The way around it is to say OKD.io, just put a dash, OKD-io. But that means we'll be renaming the repo. And again, I don't know what points to it and what else is going to break if we have to do that. Hopefully, we won't have to do that. And everything else, I think I'm pretty OK on. And the other thing, I just wanted to take the opportunity to, we've got a lot of branches. So I was just going to hopefully take the opportunity to just get rid of all of these old branches and tidy them all up. As you can see, we've got pages of branches. So if anybody has an objection, I was just going to just close all the old branches, close all the old entrances, and close all the pull requests that relate to the old one. So, yeah, so that's that. And then the other one is the status, the beta site. So that's all working. We've had a couple of pull requests from the virtualization subgroup, which raised a couple of issues. The first one is they suggested putting in the exact steps to actually create the development environment. If we do that, do we need to actually look at all the major Linux distros and Mac OS and then the windows, given that 50% of developers are on windows, you're there, 40%, some percent are on Mac, and relatively few tend to be on Linux distros. So it's just, do we have a policy of all instructions should be to cover all developers or, because the change request that he's actually put, he literally just lists the steps on CentOS, CentOS Stream8. So these are the instructions on CentOS Stream, but that doesn't cover Ubuntu, Debian type things, it doesn't cover Mac OS, it doesn't cover Windows. So that was one question. Well, let's go question by question. So for this one, I know that in some of the other sites that I'm involved with that are sort of repo based, there are example issues that people creative, like just like how there's how to create an issue, there'll be a page of how to create a page or an issue of how to create a page, how to run it locally and whatever. There are, theoretically we could script it for like the three major OSes like, but the Linux thing, obviously you're splitting it into, you know, you're going to have yum app like, so I don't know, I mean, I'm torn between writing instructions because then you have to maintain them, creating a script for each, which then again, you have to maintain it or just giving general instructions that, which is what's on the side of the minute, what's on the side of the minute says you need to have Node.js installed, you need to have Python 3 installed assuming that you know how to do that. I've also linked to the Node homepage and the Python homepage. Can I ask a naive question because that's what most of my questions are. Is this how to build the make docs version of the site? And if so, does the make docs site itself where make docs lives, does it have documentation on how to build make doc sites that we can just link to? Yeah, so I'll take you to the documentation where this is. It is this section here. So I need to write the bit about how to use a Docker I was hoping we could use partner machine, but you can't mount a volume on portman, so it's going to have to be Docker. So I'm going to put the Docker instructions here, but on this site, this is what we've got. So it's installed Python, it's all Node. But it is, where did you get this content? Did you get it from? This is also on the MK docs site. But you should we just link to the MK docs site? Well, the problem is because you got MK docs. And then you've got these other tools like to do the link checker and the spelling, which isn't on the MK doc site. So the idea is this is the set of instructions that you need to get a volume set up. To be a split page where you link to the MK docs site and then up at the top and then provide the specifics for the add-ons at the bottom. Yeah. I'm sorry, Diane, did I cut you off? No, no, no, I was, sorry, I have too many screens open and things flying across them. Yeah. So I mean, if you do these bullet points, you get a working local environment. Yeah. But the minute MK docs does their next release and you know, it's Python three point something, you know. Yeah. You actually get it because I've actually put a requirements file in, which has all the Python stuff in. So by doing a pit install minus R, you're getting MK docs and the mockdown extensions. Okay. So the biggest issue of these two, because you've got different instructions on various Linux packages that depending on the distro, obviously, if you're on MK, you can either go and use the homebrew and again, windows, you can use chocolatey or you can go to their site and type the command that they say on the site. So I've just pointed you out like Node.js. That's Node.js homepage. Go, go install it. Yeah. I, yeah. I, we have so many other things that are not that this isn't hugely important, but installing, make docs and configuring an environment, build the docs locally. Then you, you know, you can put a, add to the install Python on your, on your system based on whatever operating system you're using. Meaning you could add a caveat to that line that you have highlighted there. But, you know, I don't know what to say other than that. Otherwise we're, you know, giving a tutorial on make docs. Yeah. Yeah. That seems sufficient actually. Brian, the only thing that I might say is if there are any version dependencies on Python, you know, like sub versions, then you should say that otherwise you don't have to. For Node.js, there's an issue whether or not you go with the long-term support version or the latest and greatest and let your hair on fire version. They both work. I like the hair on fire version personally. Yeah. They both work as long as you, as long as you're not back back in the dark ages, any modern Node works, as long as Python three, I've actually said Python three. So I know Python two has now been not in support, but people still have it about. So I've actually said Python three. And again, I've tried multiple versions and it just seems fairly to be Python three. Can we go back to something for a second here? What was the reason that we didn't want to just provide a container? Well, I'm doing it that if you want to container, if you've got Docker installed, you can do it on Docker. If you want to install it locally, you can install it locally. So I'm just giving you both options, but I'm expecting most people will use a container. If you don't want to put Docker on, I mean, the problem is now that Docker is paid for on why not, but why not pod man? Because pod won't allow you to do volume mounts on Mac and Windows. So you'd have to. Oh, they write on Mac and Windows. They don't yet. Yeah. However, we could do a container. That you. This is working within. So if you have your editors on editor on window, your ID on window, you want to be able to build and test the sites. So you've got to be able to mount the volume within the container. I'm trying to. I did look at doing the clone within the container, but then it's a pain to actually go and change the content. Yeah. Yeah. I mean, you could use, you can do it on a per page basis by piping in the file to the container, but that'd be messy. Well, to do that, you've got to point it out the source tree. All right. Well, let's, let's not spend any much. Let's not spend more time on this now. It sounds like minimal is good. I agree with Diane that let's, let's push this off to a future meeting. And so let's just stick with your generalized stuff for now. Cause right now we need to get the site over just. Yep. All right. I mean, these don't need to be done. These aren't blocking the migration. These are things that are more doc, more general documentation issues that we have to do. And this is the more tricky one. And I'm feeling a bit like the, the community police at the minute. Let's see. The media presence there. Sorry. This is the one with the social media. Yeah. So what they want to do is they want to actually put a social media panel in. And what they've done is they've, in fact, I want to say again, the source, what they've done is they've actually gone and modified the site CSS to create their own, their own sort of CSS tags and content. And then they've put a bunch of HTML at the top of their page. And again, one of the design principles was get rid of all HTML. So everything is mod down within the site. Yeah. So. So maybe what we should do is invite them to come to the docs meeting, the next one. And say, um, and just put a con con, I mean, adding a section to the page is not a, not a bad thing. It's more like, um, they need to do it within the context of make docs, as opposed to adding HTML is, is our, is, is the rule, I think that we've, we're trying to, I think that's the question. I think that's the question Brian is asking is, you know, like, is that what we're saying? Are we saying that we want folks to stick to what we have available for now, unless it's applicable across sites and doesn't break things. Is that what we all agree on? I think, I think that's what I would, I think that if they do it for their sub page, they should come back and maybe do it for the, the overall landing page too, you know, in a way that doesn't break it. Bruce, you wanted to say something. Oh, I'm on, um, like if we're, uh, okay, so what are we comparing with? We're comparing with the old OCD site. Uh, which was not terribly friendly. For outsiders to edit. And so we're this version anyway, trying this particular technology. And presumably we would have, we have something in the document, excuse me, documentation that says, this is sort of the design framework for the site. So that we could point them to if somebody's coming with a completely different, you know, you know, HTML based flavor, uh, then, you know, I would think that the thing to do would be to, uh, reject the request, point them to the design, or at least continue the discussion. Uh, otherwise you get a big hodgepodge where, you know, maybe part of it is using, uh, Ruby on Rails and part of it's using React and, uh, oh, why not JSF? It's a big disaster. Brian, would you be into writing something along those lines that lays out, like this is our philosophy for right now, and basically just reiterate we discussed what we discussed and put that as a note, maybe in the, the, in that section there for the, um, the, right, the, uh, right modifying OCD.io. Can you put something in there? So if you look there, this is effectively the changing content. These are the, the markdown features that I've sort of said that exist. So the idea is that this is a set of features that you use. So if you want to create a tab, you can create a tab. Sure. What, what I mean is something that explicitly says, Hey, there's boundaries. I mean, I totally appreciate what you did. What I'm saying is, is I think we need to have something that clearly states there are boundaries. And they encompass this here. Right. Now if I'm coming from a conciliatory hat. Okay. Because I just gave you my authoritarian hat. The conciliatory hat would say that for the cube people, we actually want to pull them in. So we want to work with them to make this transition. And certainly some of them can get their backs up. You know, at least as, as well as I can, we'd like to avoid that. Yeah. And this is really why I'm, I'm asking this question because it's. This is, this is what I, this is the way the diplomatic way that I would, would try and frame it and I will reach out to Sandro because I think he's a red hatter. I'm pretty sure he is. Yeah. Yeah. If he, what he's doing, what he's asking for is to add some, it looks like a little social media pizzazz to the, the landing page. If rather than doing it just for the overt page. Or the cube, cube, okay. Whatever. I forget the name of the page, but anyways, that page, if he would come to the docs group and talk about, see if we can figure out how to do it within the context of an HTML and. And that's what I suggested that if we're going to do that, let's make it a template, which is how I've done the home page. So if you notice the home page formatting is a little bit different because we've got the things there, but the source is still pure. Maybe do, maybe do it in two steps, right? So reach out to them and continue on the path of trying to integrate it across the site in a way that, that doesn't break things. And at the same time, write something out for future, because we have other working groups coming online and be good to solidify this as, as, as process. Yeah. And yeah, I mean, I just didn't really know. We don't really have a way of any of this written down. So I just, yeah, this was just really, what is our approach to this? And then the second one is, obviously, the last working group, the main working group, we have a conversation about should we actually have social media accounts. And that was the second part of this is accepting the, the pull request. And I meant to be validating that what they put in is, in line with agreements in the, the main working group, or is that not what the role of who it, of the documentation, whoever accepts the pull request? Because again, I was a little bit unsure of that because we sort of said that we didn't want social media. And yet this pull request is adding a subgroup, not even OKD social media to subgroup social media accounts, Twitter and things. So I didn't know whether that was an issue or not. And when we accepted document pull request, are we also vetting the content in terms of it? It's agreed content through a working group or? Well, and I think that that's a great question. So reframing the question in a way that's, that's more pointed. Do how do we want to handle subgroups creating their own social media or wanting to provide their own social media modes, right? Yeah. How does this group want to handle that? Well, I think first they need one, I really want them to come to this meeting to talk about it with us as opposed to us putting an edict down on it. And we have not and raise it to a higher level because we don't even have an OKD Twitter handle. So have the conversation be about OKD, social media presence, and then the subworking groups. And so I'd like to get just pinging Sandro. And he's not on, I think he's in Italy. So I, he is in Italy. Yeah. He's not, not responding here. But I'd rather, rather than have them go off and create their own thing and then have to rein it back in or edit it after they've built up some sort of a following, whatever, I'd like to have a bigger conversation about whether or not we should have an OKD presence and how we're going to manage that. And who is going to manage that? Because as I said at one of the last meetings, I think the last main group meeting, I already manage OpenShift Commons and have access to OpenShift as Twitter handles to get stuff retweeted on. And I've never opened up the can of worms of managing yet another Twitter handle. It may be time to do that. So I'm not adverse to it, but I'd like to have that as a bigger conversation about how we resource managing it, who has access to it and that. And then if we can do something with the overt stuff, then Groovy. I keep saying overt, so I probably shouldn't be at the OKD virtualization. Cubert stuff. I'm stuck on overt this morning. Apologies to everybody. Rather than us giving them an edict saying no or whatever. But what I want to get them is more involved in the OKD working group discussion of social media and how we should do outreach. Because, you know, Jamie and the other chairs and everybody should have access to that Twitter handle. But maybe we have a social media manager for the community that just does promotions and stuff and books that and, you know. All right. So you're going to give them an official. I had already invited them, but if you give them another invite to this meeting, that would be great. And then we can go from. Yeah, so so once that's resolved, I say we have a pull request to actually pull their site in, which is the other link in this subgroup work content session. So that is the pull request. But at the minute, it actually does break the page, but we also have the questions of social media and and adding it correctly. So that's that one. And yeah, so that's me decide. So as soon as I get an official sort of comment that yeah, the way books are important, I can actually stop doing the changes and yeah, hopefully it'll take only sort of half an hour to get everything sorted and switch over. It should be. And so I'm just asking, yeah, so I'm going to go on one phone one here and here and over there. I'm just going to ask Jerry to double check and look at that issue today. And hopefully we can get that done today. All right. Let's move on here. We're about halfway through the meeting. Name and scope of install and read me. We agreed that it needs to be done reworking. We'll begin after the beta site goes to prod lots of stuff here is beta site goes to prod inclusive language. Same thing. Just an update there. I've actually put most of the install and read me stuff already into the site. We just read to verify that it's good and then change what's in the OCD repo. Right. Vadim was, Vadim wanted to make sure that that stuff didn't change in the repo until the other stuff was actually public and at the main URL. So, okay, cool. But inclusive language that's going to be addressed and then we're going to do a regular, maybe we'll do like a quarterly check in or something like that just to make sure that anything. If you want to, we can add that to the automation. Yeah, if you could, that would be awesome if you could do that. We could add that to the automation if you want to block publishing based on that. I can look into that. Brian, would this be something that once you've added it to the automation that you can put this, we need a document that basically says this is what is in there. This is what's set up so that, you know, if you need to share tasks or you need to hand it off at some point or anything that we know what is in there and how it works and whatnot. Yeah, okay. I mean, it is sort of outlined in the beta side, but yeah, I can actually be more explicit, yeah. That would be awesome. Upgrade path, notations. Vadim was talking about upgrade stuff and upgrade path. He came up with a 4.7 to 4.8, but it's unclear. There's some issues that people are having with it. So I think we'll shelve that until we get some clarity from Vadim. Yeah, it's only from one particular 4.7. And that's tricky. So you have to do like a simple grade. So like I've got my production 4.7 is running an older version. And I did actually upgrade my test one because the 4.7 September, something or other, actually successfully upgraded the previous older versions, and that's the one that will successfully upgrade to 4.8. So it's a little bit of a minefield, but it's all documented in the sort of release website. If you actually, well, if you look sort of behind the initial link into the footnotes, as it were. And of course, if you get there, then you have the wrong Kubernetes version. But who knows how Vadim is going to handle that? I mean, it works. It works fine so far. But I don't have a whole lot of usage on my test cluster. I'm mainly just trying to install things and do upgrades and things with it. So I think once Vadim gets a little bit of clarity on where things are going, by the way, I don't know if anyone saw that Christian added some comments to a couple of those tickets in conversation with other folks, as pointed out, that they're going to try to pull OKD back into the OpenShift repo and out of Vadim's private repo. So I think that's going to change things a little bit in terms of... It's going to change things a little bit. So I think we'll have to shelve this until we get more clarity from Vadim and we see sort of where things are going in terms of resources. I accidentally glossed over Create Docs Process document. So everyone has signed off on Michael's document. Does someone want to add that into the beta site? Or is it? Oh, is it? Great. All right, so that's done. Excellent. You've been doing some great work, Brian. Thank you so much. And thank you, Michael, as well. So that's done. Create Path Docs. OK. Next, OKD Office Hour. We need to do some promotion for this because it's like next week and we haven't really posted anything about it. Diane, is there an official page somewhere? Yeah, there is a landing page. I will grab it and throw it in the chat. And it is listed and the powers that be at Red Hat are promoting our presence at KubeCon, so it will get promoted as part of that slipstream. Probably we should send a note to the OKD Google Group and that would be personally sufficient marketing from our point of view. Putting in the Kubernetes user Slack channel as well. That's what I was going to say as well and in the dev because there's still people that are in the dev that are just chilling and stuff. Yeah. And then I can put one in my Slack channel for OpenShift Commons as well. But yeah, I'm just grabbing the landing page. Hang on a second. I will find it. And I also tend to spam the OpenShift in Facebook, the OpenShift users and you can post that there and people actually respond to some. Not Google. All right, well, while she's doing that Code of Conduct, there's an issue there for Code of Conduct that Diane created and Michael is added to. We're going to be added to. And this is basically an Ansible Code of Conduct page lift it and shift it into our Code of Conduct. So let's look this over and then at the next meeting like agree to it. I don't want to lift and shift until people have actually read it in this group. Yeah. So what I'm hoping and this is why I'm really thrilled that Michael Burke is here is if you look where the Ansible folks tucked it. I'm going to go right into the docs. And I know OpenShift doesn't have that in the docs right now for like docs.OpenShift.com or whatever the site is and we don't have it there. But I wouldn't I would really like to have it live in the docs. And then link to it from the site that Brian has created, which means that the cut and paste and search and replace for Ansible and tweaks that we want to would be moved into the docs and it would be maintained over time and partially because I know the Ansible folks got their stuff all nicely reviewed by Red Hat Legal and I kind of like their Code of Conduct. I know other people have other opinions about Codes of Conduct and that sort of stuff too. But I wanted to get it out there and see if Michael if that was okay with you to move it there and that way then Brian basically all you have to do is link to it and if legal or Red Hat or the community decides to change it they change it in the docs with the help from Michael Burke and the Red Hat docs team that manages that. I think that way it will live on a lot longer and get a lot more readership than the landing page itself. And that's just my opinion. So I'll stop talking and hopefully everybody will read this issue in the link and see if there's any objection. Okay so be prepared at the next meeting to provide feedback on this. One thing I would suggest is that we actually use this as I like in other words I like what CNCF does for all of their like streams and event streams and even their meeting streams and stuff this is a CNCF event and as such it falls under our code of conduct and they might link to it or whatever and I would be totally fine if we did that at the beginning of all of our meetings. Some people know it's out there. Yeah one of the things that and I'm on a bunch of CNCF things they have is at the beginning of every meeting and it might be a meeting etiquette thing that we do we don't tend to use slides or anything visual but they have one slide that they open the meeting with that it says what the meeting is what the date is and then the next slide is usually at least most of the meetings that I go to is a link with a blurb about the code of conduct and then they go into that so on every recording you have that as well. There is sort of the opening act for every meeting. That actually leads me to a question are we free to use the little mascot in our slides like for the intro to the videos? I mean no offense to what you did with the gray and red thing a couple of years ago but It would be nice to have like a white friend with the mascot and then the text for the meeting at the beginning of each one and I'd be happy to create that in my video software if I can get a copy of the mascot graphic. The graphics are all in the repo hiding somewhere in some image file and if not I will send you an upload. They should Okd.io repo? Because they're on the homepage. They're all in the open Joseph Myers did a rework of them at one point, another guy inside of Red Hat did one. That panda has been not as much as the Github Octo cat but it should be and I think we should all have our own variations. People keep sending me stickers with different panda like things with OpenShift logos incorporated in them that they've done for their local meetups and things so feel free to dance away with that and use it as you wish. Graphic skills, I keep saying this to people are from MS Paint so I have no I'm very Buddhist about my attachment to the website as you found out Brian and to any graphical things. So I will add that to the beginning of the video and I'll create a new flash screen at the beginning and it will feature the date and stuff like that and also the link to the code of conduct. Next up is or is there anything else on that topic before we move on? Should I for the meeting next week should I create a gist with lift and shift the so that we could make edits to it or you could do a gist or you could do a hackMD.io just like the yeah so that we as people are talking about it we can make notations on it so it's not I would suggest that meetings are not slice and dice meetings during meetings text slice and dice can sometimes be not the best so if folks maybe we have this discussion over the working group email list that might be better instead of like taking up the whole hour like sort of should this go there should you know what I mean like that getcha getcha I'll refrain from that for now and then we'll see how everybody on this group's review of it goes and there's only if you replace okd the word ansible with okd and not open shift I think we will be pretty close to going there but then I just want to make sure that everybody's on board with the content you know having that there and then everybody has an opinion about them okay this next one is directed at Michael there was an issue does anyone know where this issue is someone commented and I'm doing a search and I'm not finding it was either an issue or a discussion item that there are 4.9 references now in the okd docs because it just copied everything over and obviously we're not even we're just rolling out 4.8 so what can we do to address that can it be addressed yes we'll have to stop pointing to Matt to our main branch the main branch is going to have 4.9 references in it because we're documenting 4.9 right now yeah is that troublesome to point to 4.8 technically no okay never did quite understand why we're not pointing to a specific version we're pointing to main never did quite understand the reason behind that can we start pointing to the individual versions we talked before about we talked about that I meant to talk with my DPM my project manager last night but I didn't get a chance to I will get in touch with him today okay if you could just if we could go to release and not do latest anymore that would probably like solve this just not have it be latest just people will assume that the last number in the pull down is the latest yeah and so if we could do 4.8 what did we say we wanted 3.11 to 4.8 that was 3.6 3.6 3.11 and 4 4.5 4.8 okay cool we're right down somewhere I'm not looking at the other day alright and once we find that issue we'll point it to you point you to it point you to it got it so what are the next steps next on the list is Twitter and Facebook we sort of decided I think to wait on Facebook but we did decide that we wanted to have stuff sent out through the open shift Diane do you have that as a task to do did you create a task in GitHub for me no I'll create one in the repo for you that way you've got let's try to do that for all of our tasks moving forward the Fedora Core S folks do this and it actually is really good if you create an issue and we might be able to even get Vadim to add a a tag or a type whatever those types that is like task or something like that and then anytime we have a task for someone we just put that in there and then include their name and their content or something like that and for folks that didn't catch this at the main meeting I am going to start doing a task list and what that task list will do then was just link to these individual issues in the repo that explain what it is that people are supposed to be doing because we're getting to the point where we're getting big enough where we have to actually like be accountable to each other and stuff like that so is it worthwhile using a board or something put in Zenhub on top of the Git repo and actually having sort of a proper board you mean like Trello or you know like I don't know do we want to add that layer of it's just it's then an online place that you get an immediate glance and if you say oh I know that I agreed to something at the meeting but I have no idea what it was you've got so much to go look not that that's ever happened to all of us right I don't know what folks think about like Trello is good but it's also proprietary could be any type of in principle I sort of prefer things that are sort of open source enough that you can install them locally on whatever your cluster is sure but Trello is very popular I mean does the idea in general sound good the idea I think is a potentially good idea and so in terms of specifics I'm relatively open to that like I've tried all these things over the years well what's a good one that's open I the couple of times that I've looked at I haven't actually found one okay I mean it's been a year since I've looked so you're talking about it like a Trello like thing sure sure why not it's been on my mind but at a very low level so give me a task on that and I will look for it in the board so anyway I'll see if I can find something and I'll sort of bring it to the next meeting I mean there are solutions that get built on top of Git I'm just wondering like the Git project because again that means we don't have to host anything well right and a lot of the stuff that's on like so Git is proprietary as well you know Microsoft owned last I looked GitLab is a bit more flexible but they're apparently looking at an IPO that seems to be going public but sure I mean I would look in those places preferentially I guess and if you have any suggestions just pass them on to me you're doing my work so I can't complain about that I think the task was at the bottom of this meeting thing if folks want to help me add items to it so that we actually have the other thing that I that suggestion that you made at the last meeting that I think might make sense is to discuss is whether we call this group the docs group or the communications group so that we could cover more than just maybe documentation and outreach would be so that people would get a better sense and maybe we could get more of a center of gravity for the social media and outreach and marketing of things is anyone happy with that or is there another name that would be better because I think when you just say docs no offense Michael we just get the docs.okd.io folks and not the Twitter handle wannabes which is all good and if we need to break them out into two separate subgroups like okd marketing or outreach or whatever we can do that as well later but I think we need to keep it all in one to start with and I've just pinged Sandra and other folks to see if we can get them to come here and do that and I think by calling it outreach we can get them to come here but I'm not sure if that's a task or not but yeah I think it's a task so add more tasks here I'm sure there's one you picked up but I can't remember what it is sure there is too so it will be and I have lost the link to the hackMD thing can you throw the hackMD URL back into the chat too many windows the version that's Michael oh, Twitter yeah yeah for me the lesson that I've learned over the years is that creating a Twitter handle is wonderful and easy managing it and keeping it alive and feeding it is resource heavy thing so yeah and I think that's we had a little discussion with the Kuvert folks and Diane re-inviting the Kuvert folks to this meeting yep I just did that too so yep just making sure they show up is probably that thing so yeah we did that that's everything any last minute stuff that we need to talk about Diane did you put that link you put that link in the the chat for the event right no thank you I knew there was something else I was looking for hang on a sec and I will find it and Veronica has a few seconds in the chat pretty sure this is it it's just taking a bit of time to resolve and this should be an virtual booth office hours section the okd one is there and yeah it doesn't have much more and the office hours link is here well if you could if that's getting promoted on like the OpenShift Twitter then we could then forward that tweet to our respective social medias and stuff like that and I'll post it into the OpenShift users Facebook group and then folks could share that out I'm going to tweet that now from OpenShift Commons and from Python DJ and share you can see if you go to Twitter first I'll do it for myself and that it'll be out there just shortly and you'll be able to see that all right is there anything else that we need to cover before we break for the day everyone have what they need to do their tasks well this was a very productive meeting and it's amazing that this little group gets so much done actually I appreciate everyone's hard work and we should probably focus we mentioned this at the last meeting but we should also focus on trying to recruit more people to show up so that we can distribute and get even more done give people a little bit less to do so that they have lives and stuff like that all right I think we're good we're actually ending a couple minutes early and I'll check in I'll send something out over the mailing list checking in on people's tasks and pointing you to the actual issues that I'll create I don't know I'll talk to Vadim about which way to do this but they might be discussion items that have a special like task category or something awesome all right thank you folks thank you