 Okay, we are top of the hour where we get going just in the interest of given time for Q&A at the end. A very helpful tip, if you double click on the presentation, it makes it the primary kind of screen just in case you're struggling to read what's on it. So this is something that we are very happy to do, happy to share the CPE weekly report, but this is the live version of it, which is going to encompass the kind of F-34 cycle, as well as just give an update on what CPE are working on and what's coming up in the future for us. My name is Lee Griffin and I have the privilege of being the manager that's over the CPE team. Eva, I'll leave you to introduce yourself. Hi everyone, so in case you haven't met me before, I am Lady Who swears during the quizzes. I have been voted best beard twice, but I'm also the CPE product owner as well. So I generally tend to keep an eye on the projects and the work that the CPE team does on a planned quarterly basis. Awesome, thanks Eva. So we'll get into it. So look, very, very first slide is always the definition of what CPE is. It stands for Community Platform Engineering. We look after two very large and very important communities, the Fedora and the CentOS communities, and we're effectively there to help with the infrastructure and the services that support the development, the building and the releasing of those platforms, their artifacts and their deliverables. We're effectively a team for hire as well. So if you have any great ideas for services that would make Fedora a more welcoming and wonderful place, Eva is the person you reach out to and we engage with the team and we have a slide on that later on from the process perspective. You see our vision and you see our mission. You should hopefully see this linked in every one of our outbound mails and it's something we're constantly evolving, right? So we do these exercises very frequently because the environment changes, people change and so on. So if you want us to consider something new or if you feel there's a gap in our mission or vision, absolutely reach out. We love that kind of interaction. Eva. So that we are the CPE team. We are 26 people strong, although arguably four to five of us don't really do any real work, but the remaining ones, the remaining ones do. They go from system administrators to developers to ops. We even have interns and we do have the managers who keep the show on the road and then there's me and Sarah who fit in the middle there and do all the fun admin stuff. But then we go all the way from, I think our farthest member is in Brisbane, Australia, right to Portland, Oregon. And we not only have people all over the globe, we also run two projects. We both have CentOS and Fedora under our team unit. Okay. I just want to talk a little bit about the future of CPE. The first thing is we're hiring. We're going to enter a hiring phase pretty soon. I'm going to send a blog post out probably early next week on to both the Fedora and CentOS blogs, letting people know what kind of roles we're looking for, the GEOs in particular. And we're planning on dedicating that head count as much as possible to Fedora. So we're doing a slight little internal shuffle, which you'll see in a future CPE weekly update. But the net result for Fedora is that we'll be in a position to service two initiative teams each quarter. The initiative teams are the teams that build out the funky new services and offerings that we really love doing. That is in addition to the lights on work that we have. So this is going to enable us to add more value to the Fedora ecosystem. So in turn, it allows you to submit more ideas for consideration. Part of the reason that this hiring is happening is we're saying a sad goodbye to three of our community stalwarts in Pierre-Yves Chabon or Pingu, as he's more affectionately knowing, Steven Smoojin or Smooj and Leonardo Rossetti or Leo. Everyone has a shortened name, which is great for the team. The guys are all moving to an internal initiative within Red Hat that's looking at automotive and edge. And you'll see a lot of publicity and news about that in the coming weeks. The good news is that Pierre and Leo in particular are staying within the CPE banner as the CENTOS SIG enablement project is kick-starting. So effectively, we're going to help build out the SIG environment within CENTOS and help form new and exciting communities around that area. And the first product or customer community, depending on what part of the company you talk to will be automotive. So we're going to help under that banner. But the result of that is the three guys will not be actively working in Fedora on a day-to-day basis. That is not saying they're abandoning the project or leaving the community. I don't think that will ever be the case, just knowing the three people involved. But we do want to flag this. And it means the responsiveness that you might have been used to with those guys is definitely going to drop. And obviously with the new hires coming on board, it's a chance for new people to join the team and build up that trust and work for the Fedora community day in, day out. So a quick virtual round of applause for the three guys and thanking them for their service. And hopefully we'll get those jobs up soon. And if anyone on this call happens to be interested, we'll have our contact details at the end by all means reach out. So well done to the three guys and some fantastic service there. So going onwards and always with the community in mind, we have been sending out two surveys over the last number of months around what the community feedback would be on the CPE engagement. And we wanted to share some of the statistics with you today because we actually have a comparison. And it was very interesting. And overall, we were really pleased that the engagement that you feel that we're giving you has always been positive. And in fact, it increased the second time that we sent the survey. So thank you very much for all of your kind words and support. The comments are all read and they are all really appreciated. So thank you again for that. The interesting thing about it is that we had a Tiger Board in operation and people weren't really engaging with us. They didn't know about it. The hell I didn't even use it myself. And I should have. So we made some changes in response to that. We moved our initiative repo to over to Pagier. And we've seen a lot more traction on that as well. We also had some office hours on IRC too. But they were fine. But again, they started to drop off. So I dropped them. Nobody noticed. So we took that as, yeah, probably not needed. A lot of people did make a comment that they would love to see more blog posts from the team, not just from management, but from everybody as well. So that was really valuable information to get. We're definitely working on that. And by far and above, the weekly emails, which you have now live, was the most favorite part of how we communicate and engage with you. So thanks. I do that. That's great for me. But thank you very much for all of your feedback. And we will be looking to send another one of these surveys as well later this year. We might even try and get two in. And sincere thank you to Vipple and Mikhail who's been driving these surveys as well behind the scenes too. And to Ant and Sarah as well, who've been helping. We also will have a live poll running in Hopin, which I'll tell you a little bit more about that towards the end of the project. Our presentation, I should say. Excellent. And just from around the community fields aspect, I just want to do a very quick shout out to Ella Daniels, who was an intern in the Fedora project working with Marie, who helped produce these absolutely wonderful trading card kind of pictures for our team. And they're a great addition. They're a great little marketing kind of collateral for the team. And everyone really deeply appreciates it. And it's just another great example of how the community interaction is happening within our team and the Fedora community. So well done on that really well, really much appreciated from the team. Okay, just to talk about the Fedora connection. And I put 34 in brackets because we do this for every single release, right? Not just this particular Fedora release. 34% of the CPE team work exclusively on the Fedora releases and the lights on manner are directly contributing through all of these really exciting areas from release engineering, who look after our mass branching and the DRC and beta composers that we go through. We have Petter in the technical writer corner looking after the release notes for every release and every other small important change that often goes unnoticed, but it's Trojan work that's still done by the team. We then have a fantastic CIS admin main group who look after all of the lights on the infrastructure, getting everything patched before the beta freezes and working hand in hand with the community to try and debug and work through some of the issues to get us to stable release day and more importantly, get your packages over the line. And then of course, we have some of our development teams that help around the packaging, the testing, but more importantly, they're fixing some of the problems and issues in the tool chains that we use that ultimately go ahead and produce Fedora as a release. Some interesting stats is since January, we've closed 57% of the release engineering tickets that were raised. So we're on a mission to try and close more than we open, which is problematic when you release every six months. You get a lot of release engineering tickets coming into you and 77% of Fedora packages were built for the F-34 release, which is a phenomenal number that we've assisted and drove through. So just to break down our initiative process very quickly for you all and actually speaking of interns in the design team and Ella and Marie, we actually have a really cool infographic on our initiative process that walks you through step by step, but it doesn't fit properly on one of these presentations. So I just had to get a little creative and make it a three step process for the interest of time, but it will be published to the CPE Wiki page as well very soon. But in case anybody needs a little refresher on it or hasn't heard of our process, what we tend to do every quarter when we're doing some planning is that we would ask that initiative an idea that requires a number of people for a number of weeks possibly even months is briefed into me. You can file a ticket in our initiative repo on Pagger, and then I'll take it in and review it with the team. It goes against our mission statement to make sure that it meets that criteria that we've already set and if it does, then it goes into phase two. If we don't accept your initiative, it's not that we don't think it's a good idea, it's just that we just don't have the resources, the time to be able to put to it and we don't want to just leave it linger in our backlog either. So I will always communicate that to you that if we can take on your project, we are very sorry, we hope we do see it land in Fedor, but there is usually a genuine reason why we can't do it. Those that we can do it goes into a scoping process. So it's reviewed by the wider CPE team. We also have some of our team members running in a subdivision called ARC. It is the Advanced Reconnaissance Crew, or Angry Rabbits Committee, whichever you wouldn't want to call them on any given day. And that team primarily looks at initiatives that need proof of concept or technical design document put to them and they will go through them a little bit over a number of weeks and come back and then that initiative is ready for quarterly planning. It goes through the quarterly planning scoping with the stakeholders with the original requesters and we make sure that the information that we're gathering meets what the person who asked us to do the work wants out of the project and that we can and we can fit it into a time box and we can plan it. Then it moves into the final phase which is the actual quarterly planning phase and that is just a further refinement on the initiative that was briefed in, more targeted conversations with our stakeholder groups and then eventually it ends up in a priority slider exercise for our quarterly planning call where all of our stakeholder groups engage in a discussion and they rank whatever projects that we have ready for quarterly planning in a priority queue and then based on how many people the team has available to work in that quarter the top one, two or three depending on size and time gets chosen for work. Anything then that isn't chosen in the capacity of one, two or three just gets moved back into the backlog and it's ready to go into the next quarterly planning cycle. Fun, huh? That is, it is, it is very fun. Stakeholder's time to back me up on that. But some of our recent work that we have completed over the last three to six months is that in case you haven't heard we use a new Fedora account system. A couple of the main bullet points is that we've upgraded the aging old fast two software to a brand new custom free IPA fast plug-in on the front and free IPA backed on the back and a huge thank you to the free IPA team, namely Christian and all the rest of the guys who have been locked up with us throughout the deployment and all the community members as well who got that over the line, sincerest thank you to you all for that. It means now that we have a loving new system, we have a CentOS account merge as well because of it. Group sponsors have permissions to just add people to their groups and when you log in, if you have an account and if you're in groups in both the CentOS project and the Fedora project, you can see your accounts on your profile page, which is really cool. We also had OSBS for Arch64 delivered back in December and it was enabling ARM64 architecture for varying container images and so we now have two supported architectures doing this, which is pretty cool. The other two pieces of work were community driven, but CPE team had assisted mainly our assist admins, our fantastic assist admins, were able to provide some resources which meant that we now have a flat pack index or service and debug info d running in Fedora too, which is really cool. And that's only the work that we got done and arguably software has never done, but we do have some current project work as well, that's worth a call out. Again, in case you don't know, we have CentOS stream being built through CPE. Already, we have the Stream9 package sources in GitLab. You can see the build system as it's running through packages. We have compose infrastructure available. They are test composers, but you can still go and visit composes.centos.org. We have contributor documentation published as well. Please bear with us. It is our first draft out. There's a lot of edits to be made as we go through the process, and we really appreciate the feedback that we're getting from the community on steps that need changing. And then we also have some module build incoming soon in CentOS stream, which is really cool. We also have the RPM Autospec project underway as well. The guys have already removed the Git tagging feature that was in the previous versions, and they're going to be looking at doing the change log generation, making that functional, making sure RPM Autospec supports non-official builds like scratch builds and local builds. And then we want to take it to everybody for testing in staging as well for performance issues, tuning, until we start looking at production deployment later in June. So, they're actively happening, but on the site, as I mentioned, we have an ARC division, and they are running a PDC investigation. You may have seen Adam Salo reaching out on the developer and info list asking for use cases for the project. So, he's more or less collected as much as they can. The end goal of this is to look at how we can make PDC more sustainable, longer term. And at the moment, the guys are looking into investigating if we incorporate PDC in existing applications to make one less, or possibly simplifying the current version of it as well. So once we have a little bit more of an idea of which of those options is the best choice, we'll communicate straight out to you. So, that's happening. I'm on a call. They're also not on news. Yeah, all right. We're going to talk a little bit about GitLab now. So, this was something that we worked through last year. We went through a rather long and protractive requirements gathering exercise, and CentOS was our first project to move in that direction. So, if you just mentioned the CentOS stream work that we've been doing, that's now the front door to relevant development. And the team, because they've engaged so heavily here, we've learned a lot about the GitLab stream instance and how it's set up and configured. And we're after requesting a development instance from GitLab to start exploring some of the fiscal feedback that we received to see where our gaps are, see where our opportunities are. And our aim is to come back to the community with our analysis and chart a path forward in Q2. I know there's been a SIG formed around source Git, which was formed in the last couple of weeks, I believe. I was following it on the mailing lists. And we're going to try and engage Tridac Group as well, just to get more people looking at it, to explore through the feedback and just see what our next steps are here. This will be done transparently. It will be done in tandem. And we thank everyone for their patience on it. It has been a long project, but as you've seen by the volume of work that IFA has just described that we've been working through, it's hard to give the time and headspace to multiple large initiatives at once. But the good news is we're coming up for air and we're going to come back and revisit this coming quarter. Okay, that is the end of our weekly update. So if you get one email off this week, feel free to reach out to any of us with questions or comments. Both of our mails are there. We're both on Twitter as well. I'm Matt Leigh Griffin and at IFA Miloni 4, there's three other better IFA Milonis out there. We just haven't found them and hired them yet. So you're in luck that you're number four on it. And we have a CPE channel on FreeNode, which is Red Hat-CPE. Yeah, we also have, you can learn a lot more about our team on the docstaffforourproject.org page that we have. It gives you a breakdown of those lovely initiative processes that I outlined, but it also gives you a timetable and what we do, what our initial statement is, and all that fun stuff. And I mentioned earlier with our community field section that we will have a live poll in Huffin. We want to know how, if you want more engagement from us, and how best to give you that engagement. So our lovely assistant Vipple, who we'd be lost without, is going to have that live poll off on Huffin that you can please take a minute or two to answer that. And the feedback then will be sent to us so we can look at how to actually incorporate that. And again, just on behalf of both Lee and I and the wider CPE team, thank you all for your continued support and your engagement with our team throughout our work. It genuinely would not be possible without the support of the communities that we serve at all. So thank you sincerely. Okay, that is us. We're happy to take out the questions that people might have for us. We got a couple of minutes before the session is officially over. And just to echo Ifa's tanks on behalf of the team. We're only two people out of the large team that could come and chat to you today. But I know the support, the contributions, and the camaraderie really that's in the community is certainly appreciated by everyone. I'm just going to scroll to see do we have any questions? Feel free to ask whatever brings to mind. We're generally just getting some nice comments, which is always good. Lack of swearing, but I was warned. Yeah, thank you very much, guys. It's really appreciated. I did see some chatter about posting the job links and so on. We will have them up on a blog post. We're just finalizing with our internal talent team, some of the specifics and details. So we'll share the blog post more publicly. The draft is in place already. It should be good to go Monday or Tuesday of next week and watch out for Twitter and other social accounts. We're going to hopefully get the Fedora accounts to propagate it out as well. And we do take internships. So if someone is interested in an internship, you can reach out to anyone in the team. We do it in different phases, depending on budget, depending on funding and so on. They might not necessarily be advertised right now, and we can keep your request on file for when we do get an actual funded amount moving forward. Ages we do the internships at. So it is a college driven internship. So college age. I won't even dare guess what that might be for some people in the world, but effectively you have to be affiliated with a formal college because a lot of the funding comes from early talent programs, which can link in with those colleges and universities. That's a kind of corporate requirement from my understanding. We do work though very closely with Outreachee and Google Summer of Code and some of the other internship programs out there, which don't have those kind of restrictions on it. I think we even worked with the secondary school, the second level or high school students, and was it Google's call for code? I can't remember that the acronym for Vipple might remind me of it because he helped me out on that side of it. So we do work with teenagers, but for the formal employment side of it, it would be people in formal education. Yeah, there's the comment around linking the Twitter blog posts. Yeah, we do use the Fedora community Twitter accounts. We don't have our own, but there's never been an issue with the Fedora project or Center West project retweeting anything that we personally may tweet on behalf of the team. So always do check either one of those or both. We tend to be across the two and the blogs generally go off on the community blog for Fedora projects. Our personal accounts share them as well. Grayson had a question, our internships directly code related. They aren't directly code related, sorry. In general, we can only support an internship if we have the skills within the team. So if you look at the slide we had up here, we had Release Engineering, System Administration, Technical Writing, as well as Software Engineering both back in the front end. That kind of covers the whole gambit. The only gap I'd say we have is quality assurance or quality engineering from a kind of day job, but even then we have some folks that have great experience in that area. Design and maybe websites are probably the two that we'd have the minimal amount of experience from a supporting perspective. Edward has a question. Where can I direct an official invitation for this Fedora podcast? Email if I know you on it. Our mails were on the last slide, but I'll type them into this chat here just so you have it. Thanks, Fingal. No, sometimes I second don't. The spec isn't a curse. Yes, he is sure, Mark. I don't always swear. Okay, any final questions? If not, we might wrap it there and thank everyone once again. Yeah, it's always a pleasure talking out at Fedora-driven events. They're really good fun. So thank you again for everybody. We'll hope to see you at flock slash nest, whatever the next major one is. If not, the F-35 Release Party. Yeah. It is nest, yeah. I was being optimistic. It could have been flock. Next year. Thanks, everybody. Have a great rest of your day wherever you are. And congrats again on getting F-34 out the door. And a big thanks to Marie for the invite for us to come today and just for the general organization around us. Yeah. She does serious magic on these things. All right, take care. Bye-bye. See you all. Bye.