 Hello, everyone. We are starting our next talk. Please settle down at the back. Okay. So please welcome our next speakers, Effie Maloney. I tried and Akash Devdhar. Okay. I'm brilliant at that one. So the topic is state of community applications and infrastructure. Thank you, everybody. All the best. Clapping before we begin. Excellent. So I'm not Effie, I'm Eva, but it's close enough. People have called me worse. Welcome to the talk on the... Actually, question, because we like quizzes here. So can anybody tell me what team takes care of the community apps, services and infrastructure for the centers and for our projects? And if you're a member of that team, you are not allowed to answer. I'm not a member of that team. Yeah, Nick got in there first. Go first. Community... Correct. You get a prize. This is called instant karma. Yeah. Prizes will be thrown. Yeah, so community platform engineering team. This is a discussion just around the overview of the team, what we do, and Akash is going to go into a bit more detail then on the applications and services that the team actually supports, maintains, etc. So like I said, about us, we're a Red Hat sponsor team. We are all paid by Red Hat to take care of the Fedora and Sendos communities. And it is a very nice team to be in because everybody who's in that team really does care about that project, those projects. And it's nice that we get paid for that. We cover a lot of ground on the team. We have operations, day-to-day stuff. We do some development into apps and services that may either fall into a little bit of disrepair. And we also then maintain lots of apps and services. Like I said, we cover a lot of ground. We have a couple of little teams in a bigger team that we all make up together. We have the Fedora infrastructure team. We have a Sentos infrastructure team of one Fabian. We have our release engineering team. And then we have the initiatives team that spring up if we decide to action any pieces of development work. We have some cool stats to share with you as well today. And the presentation put together by Akash is all very cool laid out with lots of data and metrics and things. So this is the first in-person flock since 2019. It has been a long time since everybody came together for the Thora project. So it's nice to be back. It's my first flock, so it's nice to be experiencing it. This time you've chosen to come to Ireland. So thanks. Three years, 11 months, 25 days, too long to be together. But we are, and that's the main thing. In the Fedora infrastructure team, Kevin, there's a lot of work that gets done. This is just a very quick overview of the amount of work that the team actually powers through. So there's been over 3,000 tickets closed from last flock to this. That's averaging about $1,000 a year. Crazy numbers. But that just proves how dedicated the team is and how determined they are and helpful with Fedora to support the infrastructure that it's built on. Out of that, we do have 16 tickets that came through as requests that actually ended up turning into the initiatives, that they were much bigger than actually one or two people for a week, et cetera. So they got passed to me. In our census infra, so for one man band, he's getting through over 1,000 tickets in a year, which is good going. I'm sure there's more, but there's a lot of work that gets through. And from there, we have four tickets that ended up being initiatives as well. Release engineering. Again, these teams are like, we're talking single digits for people. There's no double digits. The team itself is made up of double digits. I think we're 20 odds strong. When we're talking about Fedora in for a census in for release engineering, et cetera, it's a much smaller subset of people. So to see them in the thousands and the ticket closures is pretty impressive. What does it all good mean? So, you know, a bunch of times the things get reported, right? And by the time we look into it, we just discovered, oh, it's recorded by itself. Magic sometimes exists in the real world. We had 146 magic stuff happening. You know issues that fixed themselves over the course of the last three years from the last 10-person plug to this one. So that's what it means. Thank you. Yeah, and finally, then we have the initiatives teams. So since I joined CPE about three odd years ago, we've managed to get through 14 initiatives, which is pretty good going. But we are always open for people who if they'd like to submit an idea for work that we could potentially do, you can submit it in, there's a repo on pager. And we always proof the initiatives before we started, and you can find that on the Read the Docs they're called Fedora Arc Team. We won't dwell too long on it. Do you want to talk to the projects part? Yep. Thanks, Ifa. So these are the projects that the community makes use of and the community of contributors that we're talking about. Sure, we do provide our offerings via our websites, but there's a bunch of things that goes into it, right? So things like building the packages, or well, we were just discussing with Justin outside, the kernel test app to begin with. So these are some projects that we undertake, we plan on undertaking or we plan on maintaining, let's just say. So we maintain a total number of 74 projects out of which 52 of them are used only by Fedora Project, nine of them by CentOS Project only, and 13 of them by both the communities. Right, so we would like to, you know, divide these projects into certain categories, and that's how we are able to understand how important these projects are to look into. Say if they are very important, and we might as well lose our sleep fixing it, or if they're not important at all, maybe we'll come back on Monday and fix it, right? So four classes, critical one, these are the application and service that we developed a code for, and we maintain our infrastructure, really, really important for Fedora Linux to be built and distributed like the way it is, right? Anything happens to them for a longer period of time? Oh boy, we don't have Fedora Linux distributed the way it is right now. Then critical two, these are the ones that we don't write the code for, but it's maintained in our infrastructure. We deploy it, we really want to make sure that it has as much uptime as we can make it. Then the standard ones are the ones that we developed the code for, we maintain our infrastructure, but yeah, maybe it's not as important as the other ones, and finally ecosystem ones. These are the ones that, well, they enhance the quality of life for the contributors, but they are, well, let's just say not as important. So critical first class, 20 projects, 12 of which by Fedora Project only, three of them by CentOS, and five of them used by both the communities, and well, like I said, most important, and well, these projects make use of Python, JavaScript, and C. So if you want to participate in maintaining these projects, by all means come, we can use all the hands we can get, and well, if you are aware of these technologies, then, well, I'll say that we will make a great team. Right, so which projects do you think would fall under critical first class? Like what the hell would be so darn important that people can't live without it? We have one hand raised. Come again? Well, let's find it out. Oh, both is actually on, let's say. Awesome. Yeah, we could throw it, but we don't know if it's going to make it to you. Right, so we have these applications that are used by only Fedora Project, the list that's only used by CentOS, and then the ones that are used by both the communities. Go ahead. Come again? Sorry? Oh, okay, right. Cool. Wow, I mean, let's just say that it probably includes both of them. Right? Yeah. Like just to listen to and not to results DB, so I think it should include the both of them. Go ahead. Yeah, Kojic might come into critical too, I think. It's an approximate. Yeah, how can we push stuff out there, right? Where does the updates come from? Unless the updates are coming from somewhere else that we don't know of. Right, so these are the statistics for the technology that we consider for applications. If they have test cases, how many of them have them? Messaging schemas, how many of these have documentation? And as you can see that the numbers are something that could use some assistance. So if you are really looking forward to contribute, I mean, not just in the code base, but in documentation as well, you're totally welcome to say. Right, so question time. What is the purpose of Fedora messaging? Does it help Fedora project contributors to communicate with each other? Or for them to communicate with Linux users? Or for them to keep track of the important contributions that the community members make? And finally, to assist each other to send messages when they are really thankful about it. So let's see some hands if anyone knows about it. Go ahead. Let's find it out. It does indeed see. That's one good thing. Right, so it does see. Moving on to the critical applications too. And yeah, 21 in total, 10 of them use Fedora project only, four of them only use presenters project, and 10 of them used by both the communities. Right, so is Koji going to make the list? I wonder. Right, any guesses? Which project do you think would fall under this critical second class category? Let's find it out. Any more guesses by the way in the meanwhile? Go ahead. Free IP. Okay, Koji and free IP. Let's... Yeah, it better be. Hmm, is it? I don't think so. Koji is actually used by both the communities. Look at the bottom of the list. Yeah, so Koji is there. And IPS, well, it's my fault. We kind of have to award them both. That's fine. I have to. Yeah. We could actually throw them, right? There you go. Perfect. Right, so these are the applications that we constrain critical to. These are the ones used in Fedora project and Centres project as well as both the communities. Right, so now that we are speaking too much about Koji, is it used for making Koji and comfortable homes by the KD contributors? Is it what it's used for? Or is it used to make fermented rice pastries for Fedora project contributors? Or is it used to make RPM packages from the source specification that's fed by the packages? Or finally, is it the official build system of the Fedora project and all the downstream communities? What answer is the most fitting for the purpose of Koji? Anyone? Come again? D. Right. Is it D? Yes, it is. Right, great. I mean, this was a little twist because both C and D are pretty much the neighboring options, but Koji does a lot more than just RPM packages. It can build OSMHs, a bunch more stuff. D it is. Right, now we're coming down to something that's a lot less important, standard applications. These are the ones that the team write the code base for, and they also maintain it in infrastructure, but let's just say that they are not as important as the critical first class, critical second class R. 17 projects in total, 14 of which are used by Fedora project, two of which are used by CentOS project and one used by both of them. Sorry. Just because the importance is lowered. Okay, we'll allow you to make a guess. What's not so important but very important? Efferman? Yep, let's find it out. Hmm, do we see Efferman in the list? I have no glasses, so I can't see it. Yeah. No, it's not. You'll have to give us something. Yeah, we could have waited for some other time, and again, these are the list of applications that are in the standard category, and yeah, you see that these are the ones maintained by the Fedora project, used by the Fedora project, and the ones that are used by CentOS as well as both the communities. Well, what's the use of Fedora plan, and now that we maintained, well, mentioned of it in the standard first class, is it like to, you know, official fork of Pandora, but Pandora is an official keyword, so we can't quite use that name no more. Go ahead. Right? This is a truck running people over, and then we get teleported to Fedora planet. Fedora planet. Fedora planet. Okay, just to be clear, we don't endorse getting run over by a truck. Yeah, which one is it? A. A? Let's see some hands. We can't just echo in A, right? We don't have that many swags. Oh, you had the opportunity. We won't let you get another one. Yeah, anyone else? Hey, it's one through? That's wrong. That's wrong. Well, let's just say that we have one's back for you. Oh, yeah, back in the day. We used to have our own. Well, no, but we're complaining before that. Yeah, no, it's definitely not B. Yeah, it's A. Yeah, that's the correct answer. Say one for Samantha. There you go. Say the last part is the ecosystem applications then rich the quality of life for the for the contributors. It seems like CentOS project contributors are so motivated. They're so motivated. They don't need those apps no more. All right. Yeah, let's hear it. Go ahead. Let's find it out. Okay, let's have some more answers before we move on to the next slide. Badges? Okay, so you mean to say it's not important, is it? All apps are important. Right, there you go. Good. Well, let's hope. So, do we see badges here? No, we should. Oh, we see that as well. And sorry, what did he say? Open QA. Oh, we don't see it here, do we? Let's just take that as an outcome for this talk, right? Yeah, so we get one for Nick and one for Sandro. Oh, Nick got one. Yeah, nothing for him. Right. So those are the ecosystem application, right? Say, what's the purpose of meatbot logs? Do you get some artificially oak logs, you know, cut it into small pieces and print the, I don't know, the artwork of sword bot? Is that what it's used for? You know. Yeah, I'm going to let you make that pull request. Right. Or is it for people to catch up on their recordings? Because, well, we like to have meetings and video calls. Is that what it's for? Or finally for people to catch up when meetings happen exactly in midnight. Not a minute before, not a minute after. Let's see some hands. Good. Is it B? Let's find it out. It is indeed B. Right, cool. Awesome. What was C? Let's find it out. Yeah, I mean, look. Well, they are recordings of some kinds, but maybe I had the video recordings in my mind when I wrote that. But yeah, that was all about it from our side. Thank you so much for being here. And do you have any questions? Oh, Sandro has one. Go ahead. The question depends a bit on who made the slides, but I suppose it was a contribution or a collaboration between the two of you. But the question is for Akash. What happened to the footnotes? You know, the internet connection is slow here, so we are still waiting for the footnotes to load. Trust me, it's here. I don't see it because it's not loaded yet. Right, any more questions? Go ahead. I just wanted to kind of put in a plug for Kevin's talk or workshop on Friday. Is it? Fedora infrastructure is not just CPE. There is community, people from the community can be involved too. I've been involved with infrastructure for a long time, since Mike McGrath did it. Which, what? That's been a while now. So where there's going to be a infrastructure onboarding workshop on Friday afternoon, I believe it is. So I just wanted to mention that if anybody's interested in getting involved, come join us. Most definitely, yeah. So that session is something that you really want to join if you work for Fedora infrastructure or you are looking forward to working with them. Any more questions, comments? Good. Alright, where are we with getting rid of some old things? We still have the old message burst. What was the other one? We still have PDC. So how are we doing with getting rid of things? Careful, Kevin. Right, so we are getting rid of things. We are doing it silently so that no one knows who got rid of it. Right, but one of those things that we took care of the last month was nuance here. It's the supplemental wallpaper voting thing. We had it around for a while, but we just figured it out. No one used it since 32, I guess. Correct me if I'm mistaken. So we decided to ask folks who predominantly use it, design team and other folks, if they want to use it, they wanted their things back. So we are trying to get rid of stuff slowly. Yeah, we are getting there. I think one of the things that we are really trying to get rid of is FEDMessage. Certain applications make use of it like badges, so we are really trying to build it to not use it. We'll get there. Actually, on that note, there is Fedora messaging schemas available if you are an application maintainer and you're still dependent on FEDMessage. I would encourage you to make use of those schemas, import them into your application. Then you can go up into the new FMN service that's available that the team worked very hard on and is now live. That will actually allow us to close off the older Fedora messaging notification service too. Plug for Fed message or Fedora messaging schemas. If you are using Fedora messaging or if you plan on using Fedora messaging, please write schema. All you need to know would be really happy. I don't think we have any more questions than I think we are at the top of the hour right now. So thank you folks for joining again. Thank you.