 I would say, welcome to What's Up with CPE, and today's hostess will be Ellen and myself. So you go ahead and introduce yourself, Ellen. It is first. Hi everyone, I'm Ellen. I'm an Associate Technical Project Manager on the CPE team. I've been with CPE for just over a year now. Yeah, and that's me. Julia? Cool. So yeah, I'm an Associate Manager. I joined the CPE team also pretty much a year ago and pretty much my first experience with Nest was a year ago. And that was quite interesting. It was a lot less scary than I thought too. So we thought we're going to make it a little bit of fun. And if you go to the polls section, what do you think does CPE stand for? And we have a couple of options. So A would be cool people environment because we're super cool. Coffee and pizza are essential. The community platform engineering or you just say like screw it. I hate abbreviations. So use the poll section and have fun with it. Cool. There will be a little bit more questions just to make it more fun. So obviously it's community platform engineering team. However, they're all the cool people and we do love coffee and pizza and we do stumble across our own abbreviations. So all of them kind of are true. So what do we do actually as a community platform engineering team? We are very dedicated to the Fedora community and also support the CentOS stream project. So and we have like three main categories. We'll go deep into that a little bit later. So we have the system administration infrastructure and release engineering team, which is basically focusing very much on the releases. They manage the releases for the community, what systems are being used. There are some critical apps which are like maintained by the in front relinch team. Then we have an initiatives in our team. There is the arc team mainly focusing on sourcing projects, getting a scope ready. And the initiatives team will then pick up the artwork and start continue working and for a limited time scope it and literally those initiatives are aimed to provide to benefit to the Fedora community, obviously. And then we have application and maintenance and those are picked up across the wall where we work on bugs. We fix them, we develop new features and focus on the community development. So we grow for you. And this is the next poll. Our newest addition to our CPE team is what? So the options are a Kermit and Miss Piggy. If you say it's you, select the community design team or hang on, I'm still counting from the first slide. Just go to the poll section and submit your responses. Have fun with it. I really would love to know those four people's who would be the newest addition to the team. Shout out to them. It's a community design team, which has been kind of adopted by the CPE team. And if you look at our team from a very holistic point of view, we have obviously our newest addition to the community design team and pretty much everyone has possibly touched base with them because they are responsible for the logos, the artwork, swag designs, websites, the wallpapers on Fodoros. So shout out to them. And then we have the CentOS and Emerging Vowel and I particularly split them up because we have some legacy with CentOS 7, but it's also combined together as the CentOS Strain team, which will focus on the next version of Vowel. So if you're contributing to the CentOS Strain community, you're also designing the new vetted enterprise Linux system. Then we have the Apple folks. I'm pretty sure most of you are familiar with them. These are, I like to call it the kind of play store for Fedora, Alma Linux, Rocky, and so on and so forth, for a noob and a non-technical person, but they basically maintain packages. And if you want to work as a maintainer or how it works in general, I recommend to join called session tomorrow. And we have the Arc team, which is basically the joint team of the in-front relinch team and the Fedora team. So we build a little group who focus on your ideas, which you bring to the table, source them, scope them, who should be involved, what kind of resources would be involved to hand them basically over to the initiatives team, who can then work jointly on an initiative to ensure that this idea actually becomes true. And once they are completed, they're going to hand it over to the in-front relinch team, then maintain it, do hand-holding, monitor it, and so on and so forth. On top of that, recently we became an intern incubator, so we have a lot of interns who are spread throughout the emerging operating system team, and all onboard within the CPE team and got hands-on experience with the Fedora. Now that being said, we also like to connect to you. And as a shout-out, we would love to get involved and collaborate with you as a community per se, and we hope we can win you over to join our Fedora badges project because that's where we are a little bit short on resources and would love to actually have a close engagement with you. So, you heard about the team, you know what they are doing. If you take wild gas on how many kilometers or miles, do you need to cover to at least to see all of us? How many would that be? So either we are just a call away, you would need to travel to the Moon and back. It could be somewhere around 236 pizza deliveries and maybe a soda, a.k.a. forever, or approximately 44,000 kilometers or 37,340 miles. Go to the poll section and vote your options. Okay, it's approximately 44,000 kilometers, it might be a little bit more because some of us are quite remote and we couldn't really define each single mile to go that way, but it should be around 44,000, which is quite a bit. So, where do we all sit? If you follow all those points, that would account for 44,000. So far, we are 39 team members, 11 interns who are not all sitting with us, but also moves on to other teams. In summary, we are 10 women in the team, so we're quite strong on that part. We cover approximately eight time zones in 12 countries and speak around 14 languages. There might be a little bit more, which we aren't that proficient yet, but we're working on it. Unfortunately, we haven't yet covered the African continent, but yeah, if you have anyone who's interested, point them out away. And with that, I'm going to hand over to Ellen. Thanks, Julia. So another poll question, how to get in touch with us? So, you can A, chat with us, email us, put in a ticket, so there's lots of options. B, you could send a smoke signal. C, you might not want to get in touch at all, who knows. And D, you could send a postcard. And I welcome anyone to send us a postcard. We would love to get your postcards. We should make that a thing. Totally. We should initiate a fedora postcard exchange. Take to the poll and see what the answers are. Something we could put forward for the future. The majority was actually correct. But seven will try to fill out some signs. Yes. And again, with the postcards, definitely welcoming postcards. Yeah, so you guys can chat with us, email us. You can put in some tickets. These are some clickable links, so we will share our slides with you afterwards. Just some of the options. IRC, you can send in a proposal. You can flag an issue or you can get in touch through community updates and keep in touch and see what we're up to. Great. One other poll question. How many tickets did we close in the last 12 months, so since the last nest? Too many to count. What even is a ticket? We didn't close any. Were we closed on the house in 796? I actually do agree with the people who say too many to count it because they wanted to figure it out. Yes. So, yeah, very well done to everybody who guessed D. Thankfully it's not C and none, or we would all be in big trouble. Yeah. So just some statistics then to back up this answer. So yeah, just a quick, even before we do that, just what are we doing with your tickets? So when your tickets come in, they're reviewed by the team. They're categorized twice daily. They're assigned to team members, or if there's more details required or more effort that needs to be put into finding out what we need to do, we do so, and then we close those tickets once again. So just some facts on that. So yeah, again 100, sorry, 1,796 tickets have been closed since last year. That's approximately 4.92 tickets a day, or 34.44 a week. Six of those have ended up on our initiatives board, which we'll explain in a little bit more detail in a few minutes. And 1,426 days was the long list of ticket was opened and then closed. Perfect. So another question. How many initiatives did we complete then since the last nest? So another 12 months. You guys can take to the polls and guess. What's an initiative? So yep, there's that. E7, C1. D, I'm still celebrating all the tickets. Okay, so brain job guys. Anybody who guessed B? I think this might actually be a bit of a trick question because I actually think the answer is actually 8 if we go to the next slide because I may have forgotten one. Yeah, so with initiatives, who we consult for initiatives or who's involved is the door community, our central community, our CPE team members, our CPE management and our business unit. So on the right hand side, there is a list of projects that have been completed since last nest. DNF and FMN replacement were both scoped by ARC. So there are additional tickets or additional initiatives. And that's currently then in progress with CPE is FMN replacement, community shift badges and kernel test app are currently being investigated by our ARC team. Great. So just a quick synopsis of what happens in the initiative process for anybody who's not familiar with it. So tickets come into our repo as we discussed. They are then reviewed by our product owner and she takes a look at those tickets and compares them to our mission and value statement as part of CPE. And then with quarterly planning, every project is investigated by ARC, our advanced reconnaissance crew. So they do a little bit of digging, a little bit of scoping and seeing what is entailed with the ticket. And once they give it a seal of approval, it gets put into our backlog. So then every quarter we do a backlog prioritization, which takes place with all of those stakeholders that we just mentioned a moment ago. And then they are put forward for a vote against the deliverables based on the ARC team and also expectations from stakeholders. And yep, they run on a quarterly cycle. So four quarters a year. So potentially one of our last questions, how do you feel about CPE now? Do you know how to distinguish between a toad and a frog? Clickable links. Maybe you're already chatting with us and maybe you have some more questions. Did we vote? Yes. So basically for, can I distinguish between a toad and a frog? Well done. Two, I'm very eager to look at the links. And then we have like some of them already chatting with us. Even better. Good, great. And we have three questions and we come to that in a second. But nevertheless, whatever you click, you all are pros. You will have the slides. So yeah, feel free to reach out to us at any time and literally pester us with questions. And this is just like a final coin case. You missed it at the beginning. We really look out for you to collaborate with us. We're looking from particular entertainers on the Fedora badges, which is a huge thing for the Fedora community. And this will be one of our pilots where we really going to work hand in hand together to move things forward and which is driven by you as a community. So thank you very much. Reach out to us if you have any questions. I think Vipple was the kind and shared the link to the presentation. So you can click all the links. They find all information. I think we have a couple of questions from Matthew. First question related to the other ones. Are there tickets non-CPE people can take on? What's the process? I think if the tickets are in progress, everyone basically has access to those tickets. I know that you need specific permissions and people will get back from the Info and Reliance team to each and every tickle holder who commented on that. So they really go through detailed comments. And depending on the permissions, I'm pretty sure people can actually access or help with certain tickets. Does that answer your question Matthew? And this will go. Awesome, cool. Otherwise reach out to us at any time. And your second question. There's more work we could do to improve Fedora or keep what we have running. Then CPE can possibly take on directly. How can CPE act more as a catalyst, as I will, to help the community scale to take on more as we grow? That's a very good question. We would love to collaborate better with the community from a CPE perspective going forward. And I think this badges initiative could be the deal breaker and just like show us the way how we can improve those things. Move forward. And we hope for a lot of collaborators on that one. It's very dear to you and to us. And we would love to help you out, guide you through it and mentor you along the way. Awesome. Any other questions? Shout them out. I just noticed one or two just in the chat. James and Matthew both asked a similar question to find complete or what is your definition of done? So that is kind of a rolling process. So the first kind of initial stage of establishing a definition of done starts with the ARC investigation. So they will look at what is going to be required to successfully improve whatever it is they are investigating. We take those recommendations and then once the initiative has gone through prioritization and has been picked, we sit down as a team and look at it with our technical lead and our engineers and look at it with our PO as well and establish some requirements and set some goals. And those goals lead towards our final definition of done. So what we establish from a technical perspective and managerial perspective to be our definition of done, what is really, really needed to be taking this initiative over the line and making it better within our scope and our requirements. That's kind of when that gets established as well. It's something we keep an eye on the whole way through a project. Sometimes it changes a little bit through course once we maybe find out different things or it goes in a different direction but for the most part it's established in the first initial kickoff phase and carries through to the end of the project. So I hope that helps. Was there any questions we missed or does anybody have any other questions that they would like to ask? Well, Max will ask like what kind of wrappers we used in the count and how we're so kind to answer that. It was Rallenge, Fedora, Infra and Centres Infra. So thanks, Mojave, for providing those numbers. Thank you. Anything else you would like to know from us? I just noticed one here. It says Vipple equals Rockstar. Yes. Thank you, Vipple. Very, very much for helping us with our poll today. And yes, just always being a phenomenal help with things like this. So thank you, Vipple. Definitely. Close one. Then I guess we're done. Thanks so much for your attendance. Thanks to everyone. We hope you had a good bit of fun. We hope you learned loads about CPE and you'll reach out and join us and have a look at some tickets and maybe contribute to badges if you would be so inclined. Awesome. Bye, guys. Thanks, everyone. Speak to you soon.