 Hi, can you hear me? Yes, I can hear you fine. Are you ready to go? I think so. Okay, then I think there's nothing stopping us, then go ahead. Okay, welcome to my talk and well, let's see how statistics also look in this field. I want to talk a little bit about SPDX license markers and reuse statements. Before I show you statistics, I will recall what they are. Let's start with what is a license? Whenever you contribute anything to KDE, you do some creative work. You own the right that this is only yours. That is good and fine, but in open source software we say it's good that other people have the right to use it, to study it, to share it, to improve it, and by default they are not allowed to do that. And to allow those people, those other people to do something like that, we have to grant them licenses and they are different free open source licenses. Most prominently in KDE, that's GPL, LGPL, MIT, BSD and some more. And you have to grant them in a legal, correct way to ensure that others are able to use what we are doing. When you are doing that, you usually have something like that. This is some arbitrary license header I took from our code base. It's typically a comment at the head of file. At the top you see a list of the copyright holders. So the people who own the create right to that contribution. And then we have a lengthy text, this one is about three paragraphs and simply explains this code is under the GPL 2.0 or any later version. And the problem with these long text is if you create another source code file and copy the license header because it's already there and then you decide, well, it's maybe not the GPL but the LGPL and you start to modify a little bit and replace the general by a lesser and then maybe forget also replacing that one, then we already have a problem to see, well, what does that mean, is it GPL or LGPL? And such problems occur often, really, really often. And it's hard to figure out by automatic tooling, what do we have for licenses. And that's the reason why we discussed one and a half years ago to go with reuse compatible license statements. This is mostly the same at the top. We simply replace copyright by this SBDX file copyright text. And the important part is that we replace the long license header text by a machine-readable identifier. And that's easier to read, it's harder to make errors and it allows to make automatic tests and also create statistics of what we have here. And during that time, a lot of things happened and many, many people helped. Before I show that, if you want to read more and know more about how this framework is working, this SBDX framework, there's a really good website, the reuse.software website, even with a small three-minute video that explains everything to you, there's all the legal documentation if you want to go into that. And of course, we have our wiki page with how-to's and guidelines, how we are doing that in KDE. In a nutshell, it's quite simple. If you create a new file, you have to add a license identifier tag. You have to create a copyright tag. And for the license that you are using, you have to add the license into a specific subfolder. It's all documented here and it's actually really hard to do it wrong. And there are even tools that check for you that you are doing it right. And during the last one and a half years, we started to replacing the old existing license headers by these shorter expressions. That's not always that simple. We have automatic tooling for that. It's also documented at the wiki page if you want to convert it because we have to match exactly what license we have. We must not change the license by doing that because we only want to make it machine readable, but we must not change it. And I will look in some areas where a lot of progress happened. This is frameworks, for example, and there we are actually done. Here, you can see the number of files we have that are about close to 9,000 files we have at the moment. And there's a small gap between the files that are converted to SPDX and those are not. And those are the files that are replicated. These are modules that will be done with KF6 and so we didn't spend time for it. So at that point with about KF573, we were done with the whole progress. And you see nicely that for all new files, there's a small upward trend. So people are still, well, are using it for new files, which is really good and important. Another area where we currently can see a lot of progress is Plasma. It's extremely nice because I didn't do anything and people started doing the conversions there and occasionally added me to prerequisites. So you see I did statistics about two weeks ago before the release, but it's on a really good track and I just did a review on a prerequest. So we are probably right here at the moment in one or two days. And if we look at the overall list, it looks actually not that bad. Let's start at the top. I did a small calculation of all the source code files. I could check out with KDE source build and simply looked at the CPP and header files, which is not completely accurate, but goes a really good impression and it's easy to calculate. And we have about, well, closely to 7,000 files and close to 40,000 files we have converted, which is really cool. And you see frameworks that are done or mostly done, well, PIM, I completely forgot, they are simply done. They did an impressive job and it's all converted. Frameworks are done essentially, Plasma will be done soon. We have a few smaller modules that probably will not that hard to convert and I think that's the area where we have some work to do, but it's looking really good and it's so nice to see a lot of different people doing the work. And if we do something like adding such markers to the files, we can do a lot of tooling and that's something I just tried out yesterday. I did a check out of all the source code I could get and, well, I grabbed for our license markers and did some statistics, which license statements do we have in our code base? So we can see and I must go to closer because it's really small for me. We have the majority with GPL 2 or later. Then we have the really big area with LGPL 2 or later and this is the combination of 2 or 3 or accepted by the KDEV. And so on, you see it's a good trend. I think that's expected to be the majority. What we probably should look into in the future is, well, we have a lot of different statements. I made it cut at all statements that were used at most 10 times and there are a lot of different interesting licenses we have at a few occasions, but we can audit later. Now we have an overview of what we have here and that's actually it. If you are interested, go to the website, go to the RIKI. It's easy to do conversions. Just ping me on IRC or on metrics and many, many thanks to other people who are involved and making this work. Okay. Thanks a lot. I think time is mostly done. Just ping me on metrics. Thank you very much, Andreas, for that. As you said, questions for the later talks, we refer to the metrics chat. So catch Andreas there and I'm sure he'll be happy to answer some of those. Thanks.