 All right, for those of you who are joining us online and around the world and those of us here at Flock today, welcome back. I'm glad that you're here to continue with the Fedora-leading Linux distribution development track. It's my pleasure to introduce Michael Cornetchi. Cornetchi. Cornetchi, ah, almost there. And I will hand it over to you for a talk today about what's new in the land of releasemonitoring.org 2023 edition. Thank you. I was already introduced. So this talk is about what's new in the land of releasemonitoring.org. This is the 2023 edition. As you can see, I adjust the Fabio slides. My name is Michael Cornetchi and I'm mage from releasemonitoring.org. That is not my official role, don't think about it. So, first thing first, where is my magic hat? Oh, here it is, okay. And, but how we can get it from the slides? Let's see. Oh, it's gone. Where it is? Oh, dear. Okay, found it. So, now I'm the mage. And let's start with a story. So, one day I was going to my magic tower. As you can see, it was nice day, everything sunny. It was like in some kind of paradise, plenty of flowers. And then I got inside and I found a stairs. So I get up and when going up, I was thinking if what I can see? As you can see, there is a balcony in there. And what do you think I could see from it? Okay, so if nobody knows, it was actually the World Release Monitoring.org. It's world real. And what it is, actually? So, there are two parts of the release monitoring.org. It's the Anitya and the New Hotness. The Anitya, I will show you first because it's just easy to show, easier to show. Let me just find it. Oh, let me fight with it for a moment. Oh, let me open it. It will be easier. Okay, so here is how it looks. This is the Anitya itself. The Anitya is a front-end for watching for the releases of your favorite projects as you can already read. And this is how it looks. And let's go back to the slides. And what it allows, allows users to add projects to watch for new releases. This will allow you to actually see what projects, what versions are available, what version is the newest, and it will allow you plenty of customization for the projects. It automatically checks for new releases of the upstream projects. You can see what is happening there. You can see hope when the version actually came out and it sends federal messages to the message bus when the new version is retrieved. So all of this is actually done in the front-end. This is what you can see mostly in the land of ferrismointing.org. But there is the other, the new hotness. The new hotness is kind of somewhere inside of the ferrismointing.org, but let's say it's floating island above. And what it does, it's listening to messages emitted by Anitya, creates or updates Paxilla when new release is built, font, and it can start scratch builds configured. This is what you will get if you are a packageer and you get notification on Paxilla. It is the issue created by the new hotness. And now we have some magic numbers, who doesn't like numbers, for Anitya first. So it will be in this format. I will show you how it was the number in the previous nest and year later. And what this is for between the last nest and the new flock. So we will do it a little more interactive. So we had two releases of Anitya two, one year ago, or to the next, to the previous nest. So how many releases do you think we had? It was more, less, more. Okay, yeah, you will be right. So next we have 266 commits. So do you think we had less commits or more? Less, okay, yeah, it's less. And it's less because we actually change how the dependencies are solved. So we don't get that much dependency updates than we get before. So plenty of tools were created by both before. And we had 13 contributors before. How many do you think this year? More, no, it's less. But I would say that this is because in the last statistic I probably included the both accounts and those are removed. So the number would be same. And how many issues? Less, less issues. No, it's more. But this means more people are actually using the release monitoring.org, which is great. Okay, and closed issues. Yeah, it's much more than last year and almost the same number as the created issues, which is nice. And the last version that I presented here was 1.4.1. So how many versions do you think was before? We know that it was six, but what is the version number? It is definitely bigger. So, to that, oh, no. 1.1, we had one hot fix and few mineral releases. There wasn't any major change, at least not in the backend. There was some changes in the front end that were actually really big. And how many projects we worked? We had 216,314 last year. So how many? We have no. More. Yeah, definitely more. So 309,000. And how many of those are Federa packages? We have 20,600 last year. It's close. We didn't get that much new, but I'm not sure right now how many Federa packages are actually out there, how many Federa packages are actually packaged and maintained right now. So not sure if the number could go that much up. Okay. And now look at what goblins delivered, so what new features we have. So you will now see the goblins that are delivering things. Those are actually DICE goblins, but this doesn't matter. Let's say that those are the goblins that are working on RISMO and TERi.org and trying to deliver things. I'm one of them. So we had one new thing is that we have sort of the list of distribution in the project view. I can actually show that when I switch to the correct tab. Oh no, okay, here it is. Okay, so if you saw the project previously and see any mappings, it was just how people created them. So we have no way that you can see them alphabetically. So it's much easier to find what you are looking for. And okay, so let's go to the next one. Let me just switch the slideshow. And the next big thing is migrating to bootstrap five. The previous where previously it was in bootstrap three and it took a great amount to actually migrate it, but the new front end looks much more clear, much more clean, much more modern. So it took the work actually was good and satisfying to see that the outcome is actually something we can look at and we can show the people. The next thing that was related to it and why the migrating actually started was we actually had dependency watching for JavaScript packages. And this was actually one of the things that was found in this that we have really old bootstrap version. Great, source has back end. If you know how the Anintia works or if you don't, there is plenty of back ends you can choose from. I will open the guide. As you can see, there are plenty of them. Those are actually all the Gitforges or sources you can watch for. We added the source hat, that was one of the newest one. And one of them is made custom so you can create your own regex that is actually trying to parse the page and trying to find the version based on regex. Okay, so let's go back. We have configuration for this trainings. Oh, I will show that because that is really nice feature. If you go to any project, let me just go back. And you can see that there are links in the package names and if you click on them, you will get redirected to the repository in the distribution. This was originally created just for few distributions and those few distribution where just having it hard coded in the web page. So the change is that it is no configurable. There is in Anita configuration you can actually set distribution and the link. And it just adds the name of the package that is specified in the package name. So you can use it for anything. You can see here is a Fedora. So let's just look at the Fedora one. And it will show you where it is, how it looks. And it's working for the FlatHub as well. So yeah, it's usable if you just want to know what distribution are actually using it. You must take in account that all of these are actually edited by somebody. There is no automation that is creating the package mappings. So if anybody from the distribution wants to update, it's on you to actually add the correct project. Okay, so let's continue. And we have another bagend. This is the CGIT bagend. Just add, I think, as the last one. And the GOGS bagend. And now we will look into the crystal ball and we will see what the future holds. So one of the things that we, that is actually wanted by plenty of people, I closed plenty of duplicates for this one, is to have some kind of replacement rules for versions. If you get a version right now, only thing you can do is to remove prefix from the version. And there are some, let's say projects that are actually creating really strange version strings. And this is to help them to actually just find the version in it. So kind of regex that will just, you will set, here is the major version, where's the minor, where's the what fix version or something like that. And the rest will be just thrown out. So the versions are much clearer. Support for different version streams. This is something that is related to both Anidya and Newhotness. The different version streams means that we will have, we will watch separate later versions for zero, 1.0 release via 2.0 release and so on. Because plenty of people actually wanted to get notifications about the older versions, even if there is a newer. So this will help with that. A new authentication backend. This is ongoing work. This is already being done partially. We will go from the Flask OIDC to Outlib. And we already have some work done for Google and GitHub, but we need to add the Outlib support for Fedora. Just the Flask OIDC is using deprecated authentication number, which is not great. But yeah, this is something I need to look into and didn't get to it. And the next is RSS feeds for projects. So if you just want to watch one project, we would like to have option for you just to add it as RSS feed and it will notify you when there is a new version. And automatic filling of project details and creating a new project. This is something, if you are familiar with ProtonDB, for example, if you just put there the ID of the game and it will show you all the things that needs to be filled in. So it will just prefill it. And I would like to have something like this for Anitya. You will just put it the URL of the project and it will prefill most of the things for the project. And now some magic numbers for the new hotness. So make it interactive again. So we had four RSS till last nest for the new hotness. Who many do think there was this year? Less or more? More. More? No, it is actually less. And who many commits? Less, more? More. More? No, it's much less. The reason for that is like I said in case of Anitya, we changed how the dependencies are resolved. That is one of the things. And the second thing that is actually bank here is that we actually don't have that much issues on the new hotness. Which is another thing. How many contributors do you think we have for the new hotness? We had five. Less? Yeah, we have three. But as I said, this could be the both accounts. I forgot to remove on the last year. Issues created. We had 62 last year. 24. And how many closed issues? More or less? It was less. But because we didn't have that much open issues. So. And version. Do you think the version is bigger or less? More or less? More or less? More or less? I don't think it's the same. No, more. Could you want to actually guess what version do we have right now? It's fine 2.24. 1.2.4. And the 4.1 is, this is actually because there was only a few hot fixes that needed to be done. And otherwise I didn't need to touch it. There are a few feature requests, but they are not high priority feature request. And for the issues, it's actually, when the issue is reported, it is closed really soon because it is much better to maintain it and much more stable. It's easier to find what is causing it and fixing it. There are a few that we didn't actually found out what is causing them. But this is something like Heisenbach, so it's hard to find. And what features? Okay, I will ask. How many features do you think there was delivered in the new hotness? Okay, yeah, it's zero. We didn't have any new features. But as I said, it looks like the new hotness is right now stable. There are a few features I'm still waiting for Bagur update to happen for the diskit. For the diskit to actually be useful because I already have in new hotness option to watch for all new releases, not looking only at the new best one, and option to watch only for the stable releases. But both of those options are dependent on diskit to have new version of Bagur, which didn't happen yet. And what is the future? So I would like to have support for flood packs for Fedora flood packs. So we will just create new bugs in the Fedora flood pack namespace. Same for Apple. And that is actually all. So any questions? Any questions about head? I don't know. I'll just give him the microphone, so. I know, I just wanted to say your head is fascinating. I need, do we have any more pins in a flock? This year? Cause I would like some pins on the head. I think that they do have some pins for giveaways later. So if you're in some of the social nights, I think they have some Fedora pins, but. Okay, that sounds great. Okay, so the question was where did I get it? So I ordered it from some eShop. I don't remember. And I liked that the colors are actually in Fedora, white and blue, so it's nice. And any other question? So forgive me if I'm just oblivious. I don't think there's anything in it for like CVE tracking separate from just actual updates. Have you considered being able to like look for CVE fixes and stuff as well? Oh, yeah. That is one of the things the CVE fixes are not part of the Anitya. Anitya is just watching for new releases. It doesn't know what they seem to release. In case of GitHub, you can look at the commit that is related to release, so this could be used. You can look at the upstream, but you need to look at the logs of the project to actually see the patches. Yeah, I was more or less just asking, is that a feature that's been considered for the future is just automating some of that? At least flagging saying, hey, there's a CVE on this. You might wanna go look for fixes. Yeah, okay. In case of Anitya, Anitya doesn't look for this. I'm not sure if we, Planet Earth Switch, I don't know if we even have issue for it. Let's just kind of go basically. Yeah. Okay. Just right now, it's just looking for new releases and the new hotness is the one that is creating the bugs. So it would need this information from somewhere and right now we don't have it, especially for some of the baggants that don't actually share it. You have custom baggants, it's usually just parsing some sites so we don't know what is on the site. Just looking for the version that is new. Okay, so here are some links. I'm not sure where I can share the slides, actually. You can put it on the sketch page. Ah, okay. Okay, so I will put it there and yeah, you can look at those. There is blog post. Oh, okay. Well, it's really a personal interest question because I put in an issue about supporting certain source for projects that release like different streams of artifacts that are tracked independently, they versioned independently. So they like sub projects from one project because I got bitten by the lack of this feature and because the new hotness filed a bug with the incorrect version that was the default, let's say, sub-project version and not the one I was actually pointing to in this particular project. Yeah, in this case, it depends if the projects actually have the tags different for the projects that are tracked on the same repo. Because if the tags are just version, we can actually. There are sub-folders. Sub-folders, yeah, okay. Yeah, I'm not sure if we can, we don't support that and it's not that much predicted actually using this. So it's a low priority feature in this case. But yeah, it's one of the, I know that there is issue for something like this. Okay, thank you. So if there isn't anything, I will share the slides later. The blog post is something I didn't update it in a long time but it's why I actually have the head and why I'm here as a mage and you can actually read why it is like that. And there are some links to the repositories and for the messaging schemas that actually were emitted by Anitya and the new hotness. And that is all. So thank you.