 Yeah, so as Matthew said, I'm going to take you through what CPE has been doing for about the last six months. So we have put together a slide show today that is based on the airplane movie, if anybody's seen that. So that's our theme today as holiday season is kind of upon us and everybody's taking flights hopefully soon. So yeah, we'll just hope it will be a really fun way to kind of give you guys some updates and tell you what the teams have been up to. So as you can see here, our sections are themed for your convenience. Please note your nearest fire exit is a leave button should you wish to do so and please feel free to use the Q&A section as we go through the presentation and hopefully some of our stewards in the Q&A section there could maybe answer some of those questions as we're going through. But we will have some time for questions at the end as well if anyone has any and yeah, we really hope you enjoy the presentation. So first things first, we're going to go through arrivals. So this is kind of what we've been working on in the last kind of couple of porters and go through some of those projects. So the first of those projects is image builder. So that was worked on by Steven Cody, David Kerwin and James Richardson. So this team assisted Fedora IoT and image builder team with integrating the image builder service into Fedora IoT build pipeline. It's in the staging process right now, but because F36 is now out of freeze and freeze is over, we are ready to roll that out into production soon. So watch this space for that to come out. The second project that we're going to look at is Bodie. So Bodie was worked on in Q1 of this year, which was January, February and March. We've managed to make some very good changes to the Bodie service, including splitting it into three packages. We've moved some CI tests to GitHub Actions, which means there's a more reliable testing system. We've added some more automation and we've resolved a lot of the dependency issues in the app, such as adding poetry. We've also upgraded Bodie to use OIDC. All of these improvements will be in the next release of Bodie, which we're scheduling for about two weeks time now that F36 has been raised. And that was worked on by Aurelian, Leica and Ryan and Patrick. And the third project we're going to look at is Datagnommer, Datagrapper. So the CPE team upgraded Datagnommer Datagrapper service late last year to make the experience better for our users. So both apps now use Fedora messaging service, which means people using Datagrapper to view results or events of apps can read what the results are from the Datagrapper home page, whereas previously it was displayed as a JSON file blurb, and it wasn't very pleasant. So the big thing with this year though is that only apps that have the Fedora messaging schemas can be displayed as humanly readable through Datagrapper. So we strongly recommend app maintainers write and add a Fedora messaging schema to their apps. We even have a how-to and a cookie cutter template of the schema. So this makes it easier for you to do. It will become necessary in the months to come as we are turning our attention to revamping FMN, and I'm going to come back to that later in the presentation. So we're going to go to what's in FLYSH at the moment. So some of the projects that we're currently working on. This first one is Flask OIDC. It's currently being worked on by David Curran, Vipple and James. So this project is seeing our team tackle some of the tech debt that is accumulated in our tech stack. We're in the process of integrating the Authlib library to Flask OIDC, as the library it was using, which was Auth2Client, is depreciated and no longer maintained. This version of Authlib that we will be using is Authlib 1.0. The next project that we're working on is Automate Packaging for InfraApps. So we've undertaken this work, this quarter, as not all InfraApps are available as Orpheum packages in Fedora. And we believe that having an automated process for doing this work would make life a lot easier for developers and packages. And that's currently being worked on by Stephen, Akash Deep and Lenka. And then just to highlight some of the work that's being done by Infra and Relenge at the moment. So they keep everything going and keep the show on the road. So folks over in Infra and Relenge have gotten through a lot of work since the release of F35. They've completed a migration of Fedora docs. So all of our documentation should now live in docs.fodoreproject.org for our convenience. They also move some of the machinery around, namely adding some extra machines for our OpenShift4 cluster and OpenQA. And have moved Ansible Control Host to Ansible Core, which is making running playbooks way more efficient. As always, our release engineers on CPE assist in the mastery build and release of Fedora as well. And then we're going to go to departure. So this is some of the look at what's coming up next for CPE over the coming months. So the team is aiming to start work on a new FMN service in around July or August of this year. FMN stands for Fedora Messaging Notifications and is used throughout the projects by users as a way to receive notifications on their activity in a project. They get results from bills, results from tests or any activity that may be of interest to them. It's currently using Fedora Message and we are trying to move it away from this service to a more up-to-date version, which is using Fedora Messaging. We intend to tailor FMN to interact with Fedora Messaging only in the coming months in an effort to reduce long log times that users are currently experiencing and also improve our UI as well. So our findings and recommendations are published in the fedoraarch.readthedocs.io and an email has gone out to the various lists of what we are intending to do with it. And a huge thank you to everyone who's engaged with our team when we were trying to understand the needs of the Dora community. And we hope that the solution that has been designed will make FMN an experience that's much better for everyone. And don't forget to use your ski mask as well. So we've called a section Air Traffic Control. So we wanted to give you a quick insight into how a project goes from an idea that someone has submitted, goes into our repo and then actually becomes actioned into a project and a team is put in place for that. So we've called it Air Traffic Control because that's kind of similar to how the process is. So someone is put in place to direct the work so that there's no crashes. So first things first with this, if you have a project idea for the CPE team, you need to file a ticket in the initiative repository, outlining what your idea is about. Then the team product owner reads through it, tags it as to be scoped and then begins an initiative acceptance criteria, which is basically asking the following questions. So does this meet the team's mission statement? What value is the work to our end users and can the work be delivered technically by our team? And if yes is the answer to all of those questions, then the product owner updates the ticket with an output of accepted. And if it's no to any of those questions, the ticket will be closed and given a reason and then the requester is notified of that reason. So once the project has been accepted, the next stage is to get the work scoped for delivery and insights are gathered from different perspectives. So this is done by first assigning an Arc team to the project. The Arc team is tasked with identifying different ways of how a project could be delivered. Then they produce an outcome in the form of a technical approach recommendation or for short we call it TAO that can be applied to a project. And this pushes the outcome to readthedocs.com. And the outcome is also reviewed with the wider team and the requester. And when all extra information is gathered, the product owner creates a brief on the work, the development team. We'll consume when it's ready to work on it. So an example of what we put into a project brief can be like an initial requirement for the development of the project, the value proposition, potential risks and impacts that the team may have. And hardware requirements, skill sets needed, team sizing and a delivery time frame as well. And then finally, once it's all been scoped and there's a TAO, it is added to the backlog and in a ready state. And it's then staffed by the CPE team when we have a free development team cycle and an email goes out to the team and our stakeholders. And a blog post comes out from our community comms team, outlining what our teams plans are for that quarter. And we're at our passenger service desk. So if there are questions, I will just go back to the Q&A section. Okay. So if anybody has any questions, please feel free to add them in there. We basically just got airplane jokes there from. Could you explain a little bit about each of the different infrastructure projects like what Bode is and those things? I think some of the people in our audience are kind of newer to the Fedora infrastructure are coming as Fedora users and might not kind of know the ins and outs. I think that would be helpful. And I'm going to drop back off the screen after that. No worries. Let me just try and go back in presentation slides to just kidding. Sorry. So I think the last question, if there wasn't a question in the meantime is about the Bode service. So Bode is an app. It manages updates in Fedora. It's heavily used within the Infra and Relengine team. And then the updates have been to make it more simple to use and have a lot more testing coverage. So I hope that answers that question. If there's any more questions? Anyone? Yeah. Oh, Fedora messaging service. Yeah. So Fedora messaging service is literally how communication comes in through some of the Fedora apps notifications. Yeah. Yeah. Communication. It is for notifications from applications specifically, right? It's not like it's not related to chat or anything like that for messaging. It's just updates. And the existing system is very complicated and kind of overwhelming. So there's some work on making it so that actual human beings can use it, I think. If there's no more questions, I guess, thank you very much for this presentation. It was great. Lots of information packed in there. And the slides are really very fun. So that's appreciated. And thank you for all your work on this. Yeah. Sorry. It kind of blocked it in the middle of there. Platform, not you. And yeah. Thank you to Eva Maloney. She helped me a lot with the email. There's one more question in the Q&A. Oh, sorry. Oh, yeah. Username change and not the most requested issue. Any works going on? And I'm not sure at the moment. But I can figure that out and hopefully get that back to you. And I'm not sure if Eva is listening, but. Eva, feel free to hop on here if you know the answer. Yep. If all has answered and said no work around it at the moment. It's really difficult because it is deeply ingrained into all of Fedora services that your username string is your identity. In retrospect, the thing where you give a random hash or a number to be the actual underlying identity and the username is descriptive would have been better. But it was, you know, a lot of these things are two decades old. So it's a very big undertaking to do it in a way that maps old things to new things in a way that doesn't break everything. So it's going to be a big project. I think it's something we will want to do at some point, but it's really hard to make it get to the top of priorities. For now, the thing that can be done is file a ticket from your old account saying I'm abandoning this account or and start a new account. I know that's not ideal, but that's what we've got at this point. Yeah, exactly. Second, what Matthew said, file a ticket in the Fedora Infra tracker. It's on Paggier. I'll dig out the link somewhere. But yeah, our Infra and Releng team are handling all of the ad hoc things like that for Noggin and stuff. And if you think that we'd need a big feature overhaul, I dropped in the repo link to our initiatives. If you think it's big enough, feel free to create an issue. I'm happy to take a look at it and see then if we need to schedule a more formal project around the work. Yeah, more questions showing up here. Is the CPE team looking into fixing up badges for the new account system? Matthew, did you put that in? I did not. It's anonymous, though, so you'll never know. But yeah, I could have put that in as well. We are definitely starting to explore it. I would expect an email out from Ryan Lurch in the coming weeks. I know he's already been doing his own investigations into the back end on it as well. And yeah, similar. We're going to probably run it similar to how we have scoped FMN that's coming up. So you'll remember that both Ryan Lurch and Aurelian Bonpart has reached out to the list in the last couple of weeks. I think Ryan posted stuff on discussions. The project and Aurelian hit up the Infra lists basically asking what the Fedora users would like to see happen in FMN and how they currently use it and what they feel is important. We're going to take the same approach for badges. And at the moment Ryan is looking into how it's currently operating and then we'll start with a very generic open ended. What do you want from badges? How do you currently use it? What do you see the values of those three or four very open generic questions just so we can get a feel for how people are interacting with the things that they would like out of us? So short answer. Yes. So Joseph asks if this team is related to the websites and the websites and apps revamp. I'm going to answer that on a real fast, which is sort of. So CP, Red Hat employs a bunch of people to work on CPE, but CPE is not itself a Fedora team. It is a Red Hat team. So there are Fedora teams, Fedora Infrastructure Release Engineering websites and people at Red Hat and in CPE work on those teams in various ways as part of our project along with people who don't work at Red Hat. The Fedora teams are not exclusive to Red Hat or you can be part of Fedora Infrastructure or websites and apps without being a Red Hatter. But a lot of people at CPE are on those teams either as part of their job or not as part of their job for fun or for their kind of 20% extra side project time. That's... Did I get that all right? Yeah, we're like cousins. Okay. Let's see. Someone asks if there's a video within introduction to all of the Fedora infrastructure. I am not aware of one, but that would be a great video. I think we could do with a lot more video content. It's something we haven't really done very much of in the past decade and I think it's probably time for that to change. Video production is hard and I don't think we have a lot of people in Fedora engineering roles who have a lot of skills in that. So this is a really great way that somebody could help contribute to the project, by the way. So if you're interested in know about video stuff, talk to me or somebody else and we'll see if we can get that going. Sorry, I'm taking over your questions. No, that's perfect. Thank you, Matthew. Eva, are there ponies where you are? No, no. This is my backyard and it's pony free. I've already dealt with the ponies this morning. I was hoping I would get to see a pony here, but... For the next one, the next release party, I'll do it down in the yard and for freight off for the internet that you're going to have, you can all see it. It seems like a good trade. Just to... I know I said in chat and Ellen referenced it during this presentation, but it is extremely important if you're an app maintainer that you do take advantage of the cookie cutter template that we have for the Fedora messaging schemas. The new FNN service will only be listening to Fedora messaging notifications. So if your app is still using Fed message, by the time we roll out the new changes to FNN, your app won't be listened to. So there is a GitHub repository. I will dig out the link before I drop off here. There's a how to and a cookie cutter template. We've tried to make this as straightforward as possible for app maintainers, but our team is always on hand as well. We usually hang out in hashtag Fedora apps channel a lot. Also, we have the Fedora Infra tracker as well if you need to open a ticket to get some assistance. You do have a couple of months. We'll be starting the FNN project in the next maybe eight weeks, certainly before the summer. And we'll give plenty of advance notice before we roll out any factors in the category or drastic changes. But get your cookie cutters while they're hot. You'll be thanking us by the time it's finished. I'll dig out that repo link now for you. So the Fedora message bus is a very cool thing for people who aren't aware. It's fairly technical, but all of our infrastructure services and a bunch of other things are connected into basically a constant stream of activity like a secret back behind the scenes Twitter for the applications themselves talking about what they're doing and other applications can listen to those messages and react to them. And so it ties everything together in a really neat way and also gives us a pretty interesting trove of data about project activity over the years. It's, yeah, I think I think Pingu was one of the initial people, Pingu, probably Ralph Bean. I'm not sure who all actually started. It's been running for almost a decade in some form or another. So it's kind of ahead of its time. I know that structure for projects and for it is more and more common, but it was pretty innovative and it still makes a lot of really heavy use of it. And with that, I think we're at time here. And I think thank you, Ellen and Ifa. Ifa, thank you for letting me put you on the spot. And thank you to everybody at CPE.