 Hello everyone, I'm Vipal and I have Ann here with me who is a manager in community platform engineering. It's a team from Red Hat who works on, wait, we have a slide for that. So who is CPE? Yeah, I'm Vipal, I'm a software engineer in CPE and I leave on Ann to start and then we'll continue. I'm Ann and I'm an associate manager. So yeah, first of all, who are we? So we're the Red Hat dedicated team looking after the Fedora and CentOS projects when it comes to infrastructure and release engineering. As you can see on the slide, we have three main parts. So we have the CIS admin infrastructure release engineering. We have our initiatives and our teams and we have our applications maintenance and we'll talk more about those as we as we go on. I don't even have to say slide. Nice one. So our CIS admin infrastructure release engineer folks, they're there to ensure that the community can access the different systems and infrastructure that's needed and to manage the releases. And we've got our initiative and our teams. We consist of dedicated engineers and admins for set periods of time to work on the initiatives and the projects that have been deemed beneficial and important to the communities that we're part of. So there's normally sort of like three month periods for initiatives that we've had longer and two week periods for the ARC team and Vipal will be covering more of that a little bit later. And our application maintenance folks are the ones that look after bug fixes, new feature requests, community development for the apps that CPE are responsible for. So keeping everything running is no small feat. Over to you Vipal. Yeah, it's always confusing on how to change the slide sorry about that. So, and did mention our team which is advanced reconnaissance crew. The idea of our team. So the team works on streamlining the initiative before being taken as an initiative. We have some very big tasks and we often don't know if this things are achievable in certain times. So this team is to ensure there are no major blockers and the work can be realistically achieved. This process also allows us to scope work and try to get the most of our time when choosing our developers and sysadmin and who will be working on which project so that we dedicate the people according to their interest and skills. Main focus has been to reduce the likelihood of the project not being completed as the issues can be flagged before the main work starts. The way we do is before the initiatives are decided our prioritized we do it in a two weeks workflow for two weeks. Some people depending on your interest and what they want to work on. They take the task, and they do a proof of concept. And it can be a full flash proof of concept or in terms of recommendation suggestions and finding out the issues. And they work with stakeholders and provide initiative teams with guidelines on how to proceed with these things. As I said, the main task is to identify the major blockers and see if it can be achieved in time or not. And so far our team has looked into data nominal data gripper and different monitoring and metric solutions on what we could use. Also, we worked on PDC replacement research. It was a huge project and we wanted to see what is the best way to dissect it or keep it upgraded federal messaging notification replacement research has also been done by that and the latest one is improving the liability of mirrors count me script, which gives stats if you see Matthew's state of federal project and it has all these graphs. It's come from there so our team also undertook that. So, yeah, you see the our team does the investigation work on the initiative proposed to see the team. Cool. So, the, the early life cycle of an initiative kind of looks like this. And bear in mind, obviously, we only have a half hour right so this is the TLDR version. We've included a link and the bottom right hand side of the slide there. If you want to look at it and get more specifics and more information. So once a ticket's been filed into the repo is reviewed by project owner and the team against our mission statement. Kind of tease have been cross and these have been dotted it moves to the arc team and for their investigation. So just like people were saying a couple of slides ago. And what's it's got the thumbs up from them and moves to wider team for technical requirements, establishing what deliverables that can be and then feedback back to the stakeholders in terms of what the team can achieve for them. Perfect. So, usually we have eight initiatives from the backlog that get taken into the quarterly planning where the following stakeholders are present. And so they discuss and vote on what work to take on based on the information gathered for each initiative by, you know, the previous and our process. So we've got both the Fedora and CentOS community representatives. We've got the CPE team itself. Obviously, we have the CPE management and we'll have the rail business unit representatives in there as well. And you can also see there are some of the initiatives and projects and stuff both completed by the team in the last six months and stuff that we're currently working on. So the bottom three are the, the current ones, the metrics for apps that are not my data gripper and then the DNF counting improvements. I'll do the infrastructure and release engineering parts and mentioned about we have new initiatives and we have application maintenance and there's infrastructure and release engineering. We have a lot of infrastructure. As you can see, Fedora has physical systems, virtual systems, CentOS has some more of it. We constantly get more donations or we keep on boarding new ones for requirements and they all require some work. So infrastructure and release engineering are your go-to person where community interacts with them. If you have any issues, you notice infrastructure and you want to talk to us. These are the people who will be solving those and will be discussing day-to-day trying to keep the fires down. And we do regular maintenance, patches, security updates, making sure all the applications are working in good state and something recently we are trying to work on are many initiatives. We have small amount of work. They are not full-fledged initiative as in they won't require three months of time and not five developers and three sysadmins but are important and they can also be from backlogs or documentation fixes. So we are trying to work on many initiatives as part of infrastructure and release engineering team where they can come and they can work on these things either on Fridays in their own, well, not in their own time, but on certain time where we have, but not all CPE team members work on the initiative. They get so certain time to work on their own thing. Or they stop to their managers and book a time slot, a sprint of a week or two to finish those things. So these many initiatives are really exciting. And infrastructure and release engineering, as I said, they mainly work on the tickets that community members open on. You can see it on pageo.io slash federal infrastructure for federal focus things, CentOS infra on CentOS related things and relinch for release engineering work. And on average every week, I just glanced over it and this is a rough number, 22 issues per week are being solved by infrared relinch team. So, we are everywhere, almost. So we've got a CPE team member on nearly every continent. Each pin doesn't represent a specific person, but rather a location where there's at least one person. You can see there we've got people from the West Coast of the US, all across the East. We've got Brazil, we've got Ireland, Belgium, France, Spain, Germany, Czech Republic, Poland, I'll be hung if I'm after forgetting anybody. Down to Pune and Bengaluru in India, and then across to Japan and one person down under on the East Coast of Australia. Shout out to Vipple, by the way, for the nice upside down pin. It was a good touch. So that's Ryan. So in the last six months, we've had seven new additions to the team across a combination of interns, full time engineers. And on Monday this week we had our newest manager join so shout out to Julia. That brings a total to 36 members today and with more to join soon. So make sure you keep an eye out for for updates and stuff on those openings as well. And here I see a lot of people asking for employees in Africa. So if you know someone and if you can refer them, just let us know when we have the opening because we'll have we'll obviously update the community places of things. It would be great if you can let us know and I'm sure managers will be happy to see that. Absolutely. Yeah, and how do you communicate with us. What a segue. So on IRC on liberal chat, we are on red hat CPE if you want to talk to management side of things and how the team interacts, how the team performs our workflows things like that. But if you want to talk specific to Fedora infrastructure. It would be federal admin where we are available and federal apps for our applications things. So you can talk to us on IRC and we have if you want to propose new initiatives as I said, community members propose an initiative we take it we prioritize it we do some research on it and depending on how important we think and if it fits our mission statement. We take those initiatives on you can propose initiatives on the link there for your IOCPE initiative proposal and infrastructure issues can be filed on federal infrastructure. It's difficult for us because of time zones and we are working on certain things people keep changing different initiatives and things so if you see any issue in infrastructure we always recommend opening a ticket. That way we can track or someone else can help if the major person you think would be able to solve it are busy. And for center is related things it sent us in front and something new that I'm very excited to share we are about to coming. We are coming next week is monthly social hours with CPE. I know I love to get on the call with if I'm sure a lot of community members do. And pub quizzes are always the thing but this is a place where you can come and talk to CPE management ask questions on how we perform and just discuss what's our future how do we are how are you going to handle certain projects. And this will be a little bit technical side of our federal social arts that we have generally, and this will be stock to your CP engineers and product owners and management side of things. Not everyone will join but depending on requirement and interest and time zones you'll see different phases from CPE there. More about it it's again it's an informal place where everyone is welcome to discuss what's new in CPE more infrastructure and applications. One thing that I have seen a lot specially website and application, the new objective that we have in council. There's a lot of historical knowledge in CPE, all time federal members who have worked on this application that are untouched for quite a long time. So if you want to discuss those, you are more than welcome there. And what are the initiatives that are upcoming and how are we going to prioritize it can get to know things there. And generally just see because CPE is also part of federal community who happens to work as their day job, you also get to meet everyone from there. The first one we are thinking of is at 1600 UTC on August 10 at the link that you see on slide. Look out for updates we'll post it on discussions.fp.federaproject.org also probably mailing list for the first time. And we have a federal event already created that I'll share after this slide. Sorry after this talk. So do join us there and it will be fun to talk and so that you get to know more of us. And, and up to you this month. Yes. So you may have seen my email on the devil lists the other day with the link to the feedback survey. So we've changed the cadence on it to once every six months. And so also just want to take this opportunity to encourage everybody to complete the survey if you've had sort of any sort of interactions with the CPE team. It can be from just reading the updates the whole way through filing tickets are speaking directly with us. And the feedback is both hugely valuable and appreciated because it allows us to keep improving where where you want this to. And you see the link to the survey on that slide as well. And on the next slide, I'll show you one of the specific examples of where we used the feedback to make a change with positive effect. So in Q2 last year, we had some good scores in terms of engagement and whether or not you guys felt that the team was doing a good job. And we also knew that we could improve and wanted to improve for all of you guys. So specifically around communication. We looked at where you said you wanted to get your information from us or you wanted to get more information from us. So as you can see there, vast majority of people were already reading the emails or wanted emails a little less in terms of blog posts but still solid percentage all the way down to the PO office servers and the Tiger board which came in dead last. So we pretty much stopped the Tiger board immediately. We reduced the PO office hours and so that we could then put more time effort and information into the weekly emails and the blogs. And then you can see six months later, there's nearly a 5% increase in both the engagement and the job well done scores and without the feedback from that survey. It wouldn't have been possible to redirect our efforts like as cleanly as we did. And I think the results there obviously speak for themselves. So this is one last shameless plug. Please, please do the survey again this time around, or if you've not done it before, please, please do it this time. That's it in terms of the presentation. So yeah, thanks for joining us today and hopefully gave you a better insight and understanding into the CPE team, sort of who we are, what we do and how you can continue helping us to be successful both with and for you. Yeah, and I have shared the link to survey in chat there to go ahead and take it if you know who CPA is and if you have a little bit of relation to development and infrastructure side of things you are our audience, we want to know how you feel that. And if you have any questions feel free to ask in the chat or Q&A and we are here for next five to 10 minutes we are lightning quick. So, if you have any questions you'd love to answer that. It's almost like we might have practiced our presentation ahead of time might have. Yeah, we did think that it would be better to interact more if you have any questions because this was just in half and a half an hour talk. And my neighbors are also very excited about this talk if you can hear them. I'm not sure. I was I knew the language nails. So, oh yeah, they're very noisy Julia if you want to hire our neighbors and I'm sure they'll go to every meeting. It's almost like Wipple, but more powerful version in terms of decreasing outcome of a meeting. Wipple can't move his, his neighbors I normally have a noisy person in the room with me which is my cockatiel, who has been strategically placed in another room for the duration of this presentation. Because whether you find me interesting or not him screaming over me less interesting. The team already get enough of that without everybody else exposed to it as well. Since no one is asking questions. Oh, there are some given I was about to highlight one thing. You can go and see when our CPE the URL there. And you can see a lot of people I'm sure there are some new people that I need we need to add on the website there but you can see how many time zones and where we are at what time. You can see all of us there and again, there are these links there if you want to go and read more about infrastructure and these engineering or initiatives. You can go on these links to read more of them. And, oh, we have a question how to get started in in development in federal that's a great question and I love to answer these. This is not really in scope of CPE but I would recommend go to federal join or bring me once I'm done with this presentation and I can help you I can give you some of the resources. Federal joining this great special interest group who help newcomers to federal start contributing. And yeah, we would love to help you with that. But this is not CPE specific so I won't go into that right now.