 Thank you for tolerating my not being able to parallel process so I think we do we have Christians on and he is muted and unmuted and muted and Craig Robinson. Craig I saw you were going to do an OKD live stream so good on you for that. Thank you. Hello Christian. So in the chat is the link to the attendee list so if you go up the top and add your names in there that would be wonderful and so I'm going to kick it off right off the bat so I can catch my breath from the last meeting and catching up here and ask Christian to give a little update on where we're at with OCP 4.5 okay and how that impacts okay the GA etc etc and swear everybody to secrecy. All right so we we're still making progress and we're still I think on schedule with regards to releasing very shortly after the OCP 4.5 release so the OCP 4.5 release date GA for 4.5 OCP has now been set I think for the 13th if there's no no more hiccups it'll it'll be next week and then yeah one two or three days after that we will go GA with OKD as well. So yeah in the MCO the dual support has merged now one thing that's missing still is actually flipping the switch and migrating the internal state the rendered machine config to ignition spec v3.1 which is what we'll also be using for OKD that is in the making and we're not actually blocking on that because it'll it'll get merged that's that's for sure and we can just take that code and also go GA with that in case it doesn't merge before but yeah so almost all the the differences between OCP MCO and OKD MCO have been resolved which is great with the installer we will carry the fork a little bit longer but yeah as we've discussed before that's not a blocking issue we're going GA so we're all set and it looks really good wow do we want to go ahead and cut a release candidate like maybe this week for for folks that we're attempting to use beta 6 that hit a couple of the issues that have been fixed in the nightlies I know probably one of the bigger ones was anybody deploying with a mirrored registry couldn't use beta 6 they had to had to use one of the nightlies after the fix but if we go ahead and cut an RC that will give them something to to work off of before we cut the final GA it also would line up very well with how we traditionally have made you know release the weed engine like aside from Fedora who has this and even Fedora still does this like there's an RC a candidate before we go to the final and like if we're we're talking about releasing a final within two weeks right let's let's go ahead and cut an RC this week is there is there any particular reason we shouldn't no there isn't and we're actually planning on doing that so I know Vadim oh well Vadim and I and Clayton Coleman I met yesterday to discuss the the technicalities designing and everything so Vadim is going to take care of that I'm not sure if he's here he can probably say a little bit more to that but yeah we're going to be doing a an RC release right we're waiting for the change the release controller to roll out that would enable us to sign releases with a trusted signature that means you would be able to upgrade from beta 6 to RC without forcing it and another thing we're waiting for is a switch to the stable Fedora co s we will leave testing develop stream on 46 and once the and once the next machine OS content promotes we would be able to update the nightly so yeah RC suddenly happening is is um are the 4.6 nightlies uh in a state that we could start playing with those now too yes they should be they are not much different from 4.5 though uh because they're based on the newest new blood hasn't yet happened but once it does we will have them three okay okay oh yeah 4.6 isn't um is still that's the current development window so there's definitely changes happening there um I mean you can always start playing with them but I wouldn't expect um and there's no no stability promise yeah oh absolutely so in the chat um Craig Robinson's asking about um issue 167 the collect images built by Fedora and reconfigure sample operator to use those um and asking if there's a way he can help with that is that oh so like so Craig this would be so what would be super helpful is if you um join the Fedora container SIG that exists I mean Christian has the details for this I think he can share that with the with the group either in the chat or via email or whatever but like um join the Fedora container SIG which is right now kind of dormant and we can I think we Christian I talked about this before we want to revitalize that use that to build a content library um that helps support container development and container centric workloads leveraging Fedora technologies I think that's a the appropriate marketing wordage for this um and yes it's mostly lack lack of active members yeah exactly um I think you said it all um we should get going on that um rather sooner than later yeah um this is actually probably a good time to start like finding interest in people and then just getting that getting revitalizing that SIG because like the extent of what that SIG does right now is press the button to push the base container release out every every release cycle and and that's just not what that SIG was set up to do that SIG was set up to do a whole lot more and it's just um a lot of the churn in OpenShift 3 and a lot of historical friction made it so that the efforts that were planned for that which we are talking about now just never came to fruition and hopefully now with better buy-in from the OpenShift side this whole operator story and like this idea of like leveraging some of the stuff we're doing in Fedora with modularity and things like that we can we can have a much better story of leveraging Fedora content with OKD and so like I uh we should we should prioritize starting to to do that work so what I would suggest too is that maybe we do a a joint meeting with that group a working group and Fedora post the GA release and maybe you would have to say post KubeCon EU post I am being you know wiped out yeah but I well I think that's one of the things that I wanted to talk about was I wanted to post something to promote the GA around KubeCon and KubeCon always has a day zero thing and I am not hosting a gathering on day zero so I know well because they moved the date so many times I just couldn't I just couldn't that's where I did see the emails about them keep shifting everything around and it's just yeah now we're good we've got a bunch of other gatherings but I was I was thinking about how we promote the GA now and one of the things and I floated this by the group before is is to do an open open OKD working group event of something maybe on the 17th in parallel with everything else everybody's doing the day before the real KubeCon stuff happens KubeCon is the 17th of August and then the next three days after that and you know red hat will have a presence in the expo hall in the booth and a bunches of people will be talking about everything from operator framework to you know the 4.5 release of OpenShift etc etc but I was thinking that maybe and I'm trying to think of something that's a low effort thing for everybody because we're all busy but I think Joseph's put it here is that in the question here is actually what I was thinking of doing was asking people from this group to take a slot and show live live coding if you're if you're with live streaming deploying on each of the available platforms so just stagger a whole bench like here's OKD4 on GKE on EKS on AWS rather or whatever bare metal and just and Craig on your home lab whatever but just like stage a whole bunch of them at different times and have a live stream basically going the whole day that those of us who are on this call pay attention to I can moderate it and host it but basically have an open OKD working group here it is and if you want to know about it on this platform come at this time come at this time and just I and it will be fluid because demos will break and it will take longer on other people's platforms than you know different things and some things are made you may want to have a video backup for but if that's something that people are interested in what I was going to do and if you're willing to yeah and and I would put an email to the list and then just give people a sign up for what they want to demo and and you can repeat like it's up two people want to do vSphere from their different perspectives or they could collaborate and do it because there's plenty of time in the day I think depends on how long it takes but I think it's something that we could do as a way to promote OKD4 and get more eyeballs on it as well as I can capture more content but that was one thing that I wanted to do and around the GA I am going to draft finally an article or not probably not for Fedora magazine because I can't move that fast to get their deadlines in but a blog post for openship.com and I was going to ask and send a note to the mailing list of people who are using end users who are willing to or partners or whomever are using OKD to get supply a quote about you know what's great about OKD4 why they're thinking about it what you know where they think it should go kind of thing so because I need to do that bit and the other thing is yes Joseph we are getting t-shirts made with your logo on it and what I'm going to do is send around a hopefully what's going to happen is there'll be a promo code where you can go put the promo code in and pick the size and the style of the t-shirt you know if you want a women's or a baseball shirt or whatever and print it and have it drop ship to you that's what's taking long is because in Canada there are some rules about sending swag across borders and everything costs extra duty charges so I probably pay double the duty plus the t-shirt so those are the three things that I was wanted to bring up today is if people are willing I will organize a live stream on the 17th not during KubeCon official days but during the day zero event and and we can set up a schedule and people can sign up for different slots to speak and I may rejig things so that it flows a little bit better but if you're willing does anybody on this call have a talk at KubeCon coming up nobody I didn't think we did get anything in so cool there's a little gorilla marketing here so we'll see and I'm not positive who will come because there's so much going on but I think it's a good thing to run and then just promote it so I'll tie that in if we do it on the 17th to the blog post about the GA saying it's going to happen on the 17th I have to get the producer yeah okay okay not I have to make sure that the producer for the live stream is willing to produce it all day and sit there and let it run on his box but if not I may just run it live stream from my machine here on just onto youtube as opposed to twitch and everything else so that's just live there or maybe just an open blue jeans prime time I don't know we'll figure out something but and so Joseph's asking a couple of so that's that's what I wanted to put on the table I will put it on the okd working group and share the blog post with folks that way too I'll do it not in my red hat account but with my d-mail or 2001 but if you see that float through you can do that yeah Craig nobody heard back on talks from coup con so don't feel bad there were thousands and thousands of talks submitted for each of I think maybe three four hundred slot speaking slots it was insane this time and it's you couldn't well because it's all virtual now it like it's essentially easy to give to do a talk sort of it is just some people yeah it is and it isn't it's like it's a challenge it's not the challenge of it's easy for people to give a talk but even prior to going to virtual thousands of people for each slot submitted and it's just getting even more crazy but it's also there are so many other virtual events that we can hit on so if you see other virtual events that you think we ought to be speaking at let me know and I'll see what I can do to get you in there there's also I just spoke with there's an open source Fridays thing that github is doing and I was going to put this working group or this effort okay D as one of the potential projects for to showcase on that as well so Christian watch for Christian and Vadim and others watch for that and we'll see if we get a slot there but I think now is the time to just really perfect our pitch yeah so anyways don't lose track of azure support if okay d4 is GA I promise I won't Joseph okay no we will we'll be checking back on that unfortunately that's really something that the fedora infrastructure has to work out and legal oh my god it's such a mess like dude so yeah we all want to we all want to fix azure but like we literally can't we are hamstrung right now there is if any of you are red hat customers just just use that to go bug the right people because like we can't do anything fedora side I I literally can't do anything nobody can yeah it's been with red hat legal I think for a while now and at least three years at the point yeah they can't sign the the microsoft provided contract and need some changes there so it's it's it seems to be difficult to get an agreement there but yeah yeah mic it is essentially the same situation with the wsl thing as basically it's the I don't have the details because I don't work for red hat so like everything is here's the or whatever that word is it is basically neither the Microsoft people nor the red hat people can like get in a room for an hour to hammer out their differences and kumbaya and sign the damn thing without that we can't do anything nobody sings kumbaya is no longer hip uh we need uh anyways that's my generation you guys are younger hey I was hearing it when I was a kid in the 90s so like there you go there you go it never dies I think it's it's definitely stuck in legal and it's you know I think it's over all of our pay grades and we I'll nudge legal again and just to see if I can get an update but I don't I don't expect to hear anything yeah three years and running so um so in terms of the GA release circling back to that yeah um so I I think I hear the 15th of July might be around when I should have my blog post reviewed and drafted and quotes in and everything from people um so it may be on the 16th of July we would have an actual release of the GA if I'm just trying to get the timing in my head so you can nod christian if you think and vetting do you think that's about right okay so I will basically draft it in the next couple of days and share it with everybody and um yeah no vacation until GA who's getting vacation I'm at home I live in paradise so so it'll be good um all right so anything else christian vetting anyone else we need to cover off here um we had a few things but I still don't think I don't think we've gone any further with the iot conversation and I'm just going to share my screen again to make sure I didn't miss anything I'm sorry actually go ahead I was just gonna say if we got the fedora sig going that was mentioned previously would that be a place that we would do some of that arm 64 work for the iot thing um not really because that's the the the fedora iot thing actually has a working group for that um for uh but if we want to talk about okd related enablement for arm then we would probably be talking to fedora coro s sig and and doing fedora coro's working group sorry and and and deal with that there god we just need to use a consistent name for all these things yeah um I've I've actually um hooked some people inside red hat and yeah try to to start the conversation of moving fedora coro s fedora iot closer together again uh so yeah it's it's a long-term thing I don't expect anything to really happen there in the very short term but um yeah I'll definitely keep you posted on on any progress we'll make there there has been a tiny bit of interest um on arm 64 and open shift from the automotive sector folks tiny because in internal to cars and things they're they're using some oh dear yeah oh yeah I don't want to drive that car but anyway um that was on the air wasn't it um so yeah so there's there may be some customer use cases that will help push that forward christian so ping me after that and I'll see if I can you know I think that that's what it's really going to take for open shift proper do you know put any resources on it yeah yeah I definitely think so too um otherwise open shift to move that way there'll have to be some financial uh incentive yeah or it's going to be a complete open source fedora iot can join twin with fedora coro s offspring with some you know other things I mean I think the the real goal behind this at least for me would be to make fedora iot and fedora coro s essentially the same fedora iot would be the arm version of dora coro s essentially and then we could also if we were really there at that point we would also try to move fedora silver blue to that same build system but I think the discussion really is uh yeah it is still and it's in the beginning because we really need to decide on on one build system to to push for in the future and um yeah there's a few options and a few just details that that need to be worked out and because there's no coherent story about our use cases for all of them um yeah collecting use cases is probably the best thing we can do right now so I we've got one we've got mayas I think I have an automotive one that actually might have and um Maya the project that Maya was talking about is actually a number of the clients that they have are open shift users like boots and uh farm the the their pharmacies in UK and a bunch of other retailers so there actually are quite a quite a few um in their client list that are already using open shift so there's there's a connection there to a legit eventual customer story so it's just really finding you know the resources and engineering resources to free up and as I said really nothing is going to happen until 4.5 south the door post boob con and you know it might be something we can talk about you know as in the okd live stream at some point get folks to come in and reboot the fedora container sake is there anything else we need to touch on today um I know this feels like a light one but we've been there was more testing on vSphere requested did we get that done enough testing on vSphere with a release not the release beta six I think so we ran a couple of the irons and all of those past I haven't seen any box files so we consider it working and the issue that I think there may actually be an issue with regard to the bringing up of the of the network interface which may be the reason that it won't work because I think we forgot to replace the files in the registry base is that the same no that's for UPI right right and it's a reference to reform sir dan is that the same thing is this fcause network naming issue that dusty brought up yeah pretty much yeah so that hasn't been closed or or yeah it's it's a related thing so um in dora we we had the issue that we were defaulting to the old naming scheme for network interfaces while reted coro s was already using the new one which was obviously um yeah the the way it was intended and then fedora it was just a bug so that's fixed but um fedora also uses a newer version of network manager essentially and defaults to using network manager key files for configuring the network interfaces while right yet not yet not yet almost the that change has not landed yet but it is coming I like as a member of esco I don't have a reason to not approve it and I expect everyone else will be like sure whatever so it will probably land it's not there yet okay I think specifically in fedora coro s we already use it yes I'm not mistaken so um and in redhead coro s we still use if config files oh my god I feel so sorry for all of you and and that is already uh deprecated in fedora and you can't even use them anymore in fedora so that's why we uh in this vSphere UPI case um they're actually laying writing a file an if config file in the ocp installer to the bootstrap host and we had to replace that in fedora coro s um with the network manager key file obviously and um unfortunately we can't use the key file in redhead coro s yet because of some missing functionality in the in a dramfs where the interface would uh would have to be activated and that currently only works with uh if configs and not with key files so yeah it's an ongoing issue it's like it's a broader topic but um we'll resolve it eventually I'm just looking through the list of things that were opened last week so it looks like that one this one looks older than that replace the ionic ironic stub images with ironic built from rdo did that happen no we would have to punt at post the ga yeah I knew that was gonna happen bare metal that was only for bare metal api though right yep correct I expected that we were gonna have to punt that which is why I said do we really need this for ga because we weren't going to get it okay which means we can't build on rdo no it what it means is that um you we cannot launch an installer provisioned mechanism an automated provisioning mechanism for bare metal everyone has to massage it through by hand which is a crappy workflow especially for bare metal but but we don't have anything better but maybe we will in the future um mostly us skipping this and saying this is explicitly broken because of rdo like not being ready is essentially the stick I would say like can we get the act together so that from rdo side so that we can actually do this for okay d side because like that's that's basically the issue um I'm thinking I'm going to host an AMA with the rdo team on the 27th of july oh boy do with rdo team we just need to build okay these specific images across several open shift repos which includes rdo's ironic okay so it's not an rdo really issue it's it's us building those images I mean they would preferably do the work and add those container builds because they'll have to manage and maintain them as well as part of their project but we could probably do it ourselves at the files at the docker files ourselves I'd prefer the teams to really maintain that though yeah and then maintain it yeah okay so I do have a connection there and so do you Christian and Vadim so we'll see what we can do all right that's I mean that's a very short road to ga I have to say is there anything else we should cover Christian Vadim anyone else I'm not looking at the chat so I'm going to pause sharing for a minute go back in the chat um I do have a discussion topic basically okay go for it once we ga we can build releases arbitrarily and we can name them however we want to the question is how often do we want those built like a small milestones because those would be effectively promoted not likely we just need to pick a nice schedule for that and naming anyone has ideas we can discuss it in a we can discuss it today or we can file an issue well I think we should file put the issue up there um and everyone can poop on this but my preference is is that we follow wrong even if you know I would like to see something that informs us what release of ocp we're in tandem with or tied to um I don't know how that's the trick it's not tied to any release there's a parallel streams we can have the very same schedule as ocp has and the majority of the changes from ocp would be there but it's still not one to one yeah are you suggesting like our our ga release would be okd 4.5 is that what you didn't die I was I was thinking that way but I don't like the sound of it um but personally but I think release is like some I don't know I always get confused when we're out of sync with the thing that we're rebasing off of but we do that with kubernetes anyway so I think people other people are used to it I think we've burned that bridge with open shift four like in the open shift three era we tried to keep all the versions in sync and and I somebody decided that well let's not and burned it all for four so I think I think it's fine so yeah I I think what makes most sense for us is to just have this stable okd 4 stream and whatever gets tagged into that stream is essentially the stable version and it could be built off of the 4.5 branch now and later the 4.6 branch but it'll still be the okd 4 stable stream and yeah we also need to think about how often we release about the cadence whether we want to stick to ocp releases or which is what we prefer internally I think buddy may may us I probably have to say a bit more about that may do like a bi-weekly stable release all right the difference is that stable stream okd has ocp has three stable streams at any given point this is why they're we're making three releases weekly in okd we only have one and we will only have one for any for eternity meanwhile we will have parallel streams for nightlies just a matter of picking the most stable nightly every week or every two weeks and promoting it as a stable version I think weekly seems nice as Joseph is saying in the chat unless there's some security patch or something please sound nice but so far only me and Clayton can do that and apparently we're still humans we need PTOs this sounds like a buzz factor problem I think weekly is probably a little bit too high of the cadence but bi-weekly or monthly synchronize with the fedora core os releases yeah if you think if you synchronize it with the fedora core os cadence that should make things relatively straightforward for planning this is a very good point because we're based on stable fedora core os now which means we can give one week of stable fedora core os testing on okd and then promoted to stable and then into weeks do the same because the request has two weeks cadence right so we just be off by one in terms of weeks so like the alternate week would be when we push and that will that should keep us relatively in line and if something if something goes wrong we can we can we have time to deal with it before the next fedora core os snapshot release gets pushed out yeah I think that's that's great and we should discuss that with the fedora core os community as well just up at least let them know that we're planning to do it that way but I think it makes sense so christian and buddy can you open a thread on the the google group the mailing list on that and then um once we come circle back in two weeks time then can we put a note in the the read me or someplace in the documentation about that I'm fine with what everybody does oh and Larry you would ask that Larry's asking is okd sent to us out of the picture permanently nothing is permanently out of any picture I mean here's to hoping is anybody have an update on sent to us stream so there has been some or that there is some ongoing work in actually pushing the red head core os config that is used to build red head core os to to get up it resides on an internal repository right now just like the fedora core os config is is on github and as part of that that that is sort of the sent us stream core os config so sent us with the recently introduced sent us stream sent us stream is actually upstream to rel well then you know downstream's rel and then sent us is a repackaging of rel downstream to rel and way downstream of of sent us stream it's a bit complicated but so I think for us as a company it would make sense to build a sent us stream core os and build an okd with that and that's the thing we have agreed to to tackle after okd ga so I don't want to say much about it now because yeah there's other work right now but I think we should come around and and discuss that again yeah maybe next next meeting or is there a point after that is there anyone from the sent us stream group that's a point person for this that we could get to come to the next meeting or is it still just all clayton and you and conversations so I'm I'm yeah I'm not aware of I don't really know anybody from the sent us stream team like do they sent us stream know about this conversation I guess is what I'm really asking I don't know I definitely don't because Carl would be completely clueless about this conversation right now when we talk about sent us stream people there you're muted when we're talking about sent us stream people there's really only two people Carl George and Brian Stinson and I promise you they are completely utterly clueless about these conversations because nobody's talking to them about it okay who is the person that raised their hand there that seems to be muted is it Sam or you're still muted and I just put something in the chat because I don't recognize it you're Adam maybe oh open stack on fcause would be fun I want to see open stack on fedora again like that is a thing I would love to see again Nelson you you should be unmuted to to speak I don't know if there's something wrong with your sound sorry folks we're just having a technical yeah glitz and I think you've got a hardware fault in terms of your audio audio because you don't look muted oh well you get the hand wavy thing going but nothing else type it in the chat then or you could call by phone if you wanted to and have fun that way who does that anymore all right dude someone this morning the fedora workstation working group had to do that because his internet connection was so bad that he was cutting out on the audio streams all the time okay okay so gelson is saying though no cento west core west on the plan is that a statement gelson nod yes or no or is that a question oh you're part of the pos sig there's still a pos sig I love you guys pauses the acronym that will never die yep and it should so yeah maybe we should we should approach the the centos guys and yeah get that discussion started yeah you should probably talk to carl because I know brine is currently overloaded trying to fix all the infrastructure stuff so carl's usually the good community interface point for a cento stream he was the guy that did the video for red hat summit yeah oh good that's how I don't know who it is isn't rich bowen as well the centos yeah he's he's on the board I think or like the lead or something I don't know what he actually does but like he's up there um yeah so I'll reach out to rich and just touch bases with him because I know him okay um and then maybe like we're like I'm thinking we should have a joint meeting with the fedora container sake maybe what we do is have a joint meeting with the fedora with the center west pos sig and just give them an update on what's coming with ok d4 and um and pause that conversation for a minute because joseph is asking a question about samples operators let me go back up to oh hey somebody's been building stuff for openshift four and copper well then that's james james unmute yourself but again if someone answered joseph's question about the samples operator i'm just so so the samples operator is the thing that we were talking about filling with content from fedora container sick um right now what that does in ocp is that it's filled with the ubi and the language stack of the dev tool set stuff that that red hat has been doing with rel um for ocp to like backfill this like this content base for developing applications in openshift for ok d we want to have a similar thing mapped to fedora and maybe also the pass it could jump in and do some stuff with centos based containers i believe they have a a broken outdated registry that could probably be fixed and then used for for hosting this stuff um and so like maybe this is this is where where the past thing would be useful is being able to provide centos based content for that stuff especially because um we don't have a centos stream based container at all for anything and that's where a lot of the modules and extra streams and like multi version content stuff is coming in um and so maybe that's a value uh a point of of of cooperation there we'll see but like the samples operator is essentially the center of this conversation of fedora container sick and maybe also the centos pass sick i'm going to pause you there for a minute um because i not muting anybody um but james you're on here and you've been rebuilding the ocp4 srpms in col can you explain what that is and i'm just going to share that screen here and copper is fedora's um i don't know if you're familiar with the bundtus ppas but copper is the equivalent that we have in in fedora it's the community project repo system um and uh basically what james has done here is he's just taken all the serpums published by red hat and then just pushed them to be built on top of centos in in fedora copper so like he's just rebuilding them and then pushing them um yeah no it's also copper is interesting because it also has it's actually one of the few package build system infrastructures that actually has support for integrating with git supporting pr workflows um push to master automatic rebuild stuff like that well it used to stand for cool other package repo now they call it community projects which is whatever i it's just i'm gonna pause you here again so tell me um i've got i think i'm sharing my screen i am yep you are what i'm looking at here is this openshift 4.4 running on centos yes okay that's what it's rebuilt essentially all the content for ocp4 for um in copper okay and is there a movement afoot to do the same thing for okd4 just asking because well if we know where the serpums are for okd we can definitely do it i don't even know where they are so like anyone who wants to do that like doing that on on copper i think we we don't need to do it uh because fedora already provides all those dependencies for us oh that's right yes so for most of the content we don't need it because it's already in the fedora repos exactly we just so the main this is james the main use uh for this was so that i could build a centos based core os because those dependencies are not in centos they're so hence i rebuilt them so that i could use them on centos and instead of trying to rebuild the fedora packages i just rebuilt the ocp packages because those are already not to work okay thank you that's what i was trying to get to the bottom of this conversation because there's always another new acronym in every meeting all day long so and i didn't know copper before all right anything else that we should talk about today did we clean up outdated information on okd yeah of course we should not sure what is outdated which links are okay bug links to bug i thought we already cleaned this up i thought yeah we had gone through it once before but um yeah if you joseph want to take a screenshot of it and just mark up what you think is out of date um i will happily clean it up again thank you and just send it to me and here's my email address everybody if you don't have it it's pretty much on the internet's everywhere i think everything should be out of date added everything should be up to date but you know it changes so i have a crazy idea in case anybody has time next week at at this meeting time we could sort of spend an hour or two checking everything which is when we should have the rc release but well yeah we shouldn't have the rc release probably by then so maybe just like a little hack hacking hour just to i'd host it happily yeah if you send the note put it in the fedora calendar um hack on well hack on documentation any outstanding issues we we have um try to reproduce it fix it and then sort of yeah i say that and now i'm just going to look at my calendar for a second but um you don't have to have me here you can do it without me um but i think i have it yeah next next we're talking tuesday the 14th um i could host something happily um and we could just make sure that first of all all the links on okd.io are done everything in the github repo and the read me was accurate and walk through the docs and see what we messed up on and maybe also review i can come back if we can do the august 17th thing and we can work on the schedule for that and then i can create a little landing page for that event and start promoting it that would be that would be a good use of time i don't think it's a crazy idea clean up is good cool so yeah i'll send out a reminder and an email about that um i mean we we shouldn't be expecting too many issues but like yeah documentation things may they always slip so it's probably good to just really read through the docs again and everybody try their favorite platform install again and just collect any last minute bugs we find and i can just set up i can set up the blue jeans and we can you can go as long as you want in it i'll just um next week same time same place i'll let that's good christian do that and then um we can yeah diane will be here and then i will um i might have to jump out a few times for other things but you can merrily keep on and i'll just keep one machine running the the on meeting how much in advance do you think we'll know which nightly we're going to turn into the ga ready and i'm asking because if we if we knew like 24 or 48 hours in advance um those of us that had open slots in our calendars we could go ahead and run a test off of that nightly just to smoke anything out i usually just roll the dice but we can i love that we're just going to roll the dice in whichever one lands that's there we go the only thing that would have been better it's like i just throw it dark whatever whatever it lands on that that's what we go with on a serious topic we now have the option to run additional tests for a particular nightly oh good so what we could do is we will wait for the signature and stable fedora croiss release to actually produce us a new nightly we could pick any run a few tests if they pass we will mirror it and declare it an rc we could do that live this is going to take a couple of hours for this to complete if they fail we will proceed to the next one in fact sure the trance all the time and then decide cool i'm hoping tomorrow or on thursday we will finally have all the fixes landed tested and we can start using the rc sounds like a plan here's my new logo for the next i don't know if you can see this the okay d dice ah yes perfect there you go we just need to you know vectorize it up and then burn it fancy there you go t-shirts and coffee cups oh man come on this is the first word yeah no i'm the last person to do t-shirts and stickers i'm but but this one's this one's worthy um so anyways um i think we should have our own t-shirt store we probably make more money um so that's that's i think we've covered everything you actually own a seat stand string press action whoo-hoo oh man you're so tempting now you and i are going to talk i run the maker fair here i have a whole series of things so i'm jamie i don't think you expected that jamie but congratulations you've been volunteered yeah much better than much better than commercially printed stuff and made um so that's it uh we're sort of at the end of the hour and so christian year to do right away is to book that 10 o'clock next week and i will make sure i open it up yeah okay d a platform to sell swag and larry those were those results ping us on slack and we can do that so there's a couple of things larry you're you're looking for and if i go you need to air anything you can unmute yourself and talk or not just trying to find my mute button sorry like everybody else uh no i was good i just searched for the open doc issues that i had opened up and they're all closed cool all right that's a nice thing to hear at the end of a meeting all right i'm going to give everybody back five minutes of their time i will post this video in its raw form on the working group for anyone who didn't join um and we'll just motor on next week perfect thank you everybody thank you thanks bye thank you christian bye bye awesome work thanks all