 I am actually very worried about the feature of LATEDOCK. If you don't know what LATEDOCK is, it's like this dock that you can use in KD Plasma or any other desktop and it's a dock, so you can use it like a panel or with your apps on it. Check it out. It's very nice, but I'm worried about this feature. And the reason for that is, first of all, this blog post, the author of LATEDOCK, which, again, I should pronounce, but I'm not able to. And actually, it's a person that helped me a lot develop features for the panel in KD Plasma. So it's a developer that actually helped me a lot. So I'm going to say thank you a lot. And unlikely due to personal reasons, such as I think it's like lack of time and motivation these kind of things sadly happen, he won't be developing LATEDOCK anymore. And what does this mean for the project? Let's try to understand that. One very important thing is that he hoped to release LATEDOCK version 11, but he didn't, meaning that the latest version of LATEDOCK currently is version 10, which is not Gitmaster. Gitmaster is currently a work in progress of version 11, which he didn't publish because he wouldn't be able to actually maintain it. So I'll talk about version 11, because this is important. But first of all, let's address a question that I got asked a lot, which is, couldn't the KD team pick up lead development or make similar features native? So let's always remember that LATEDOCK is a project from KD, is a KD project in everything. It's hosted on KD. So technically PSYFIDOTOS was the maintainer, but it's a project from KD. And what this means is that, yes, there will be some interest from other KD developers to make sure that LATEDOCK continues to work. But I'll get to that. Another question is making similar features native, that is bringing those features to the plasma panel, which is the one that I brought some features from LATEDOCK to the plasma panel. So how that works is that in theory, you could imagine it as taking the code from LATEDOCK, copy pasting it to the plasma panel and everything works. Of course, that's not how it works. It doesn't work. And if you want to implement something in the plasma panel, it's very, very, very, very, very likely that you have to writing from scratch, which I did. I implemented floating panels for the latest version of KD plasma. And that is a feature that LATEDOCK has. And in the past, you had to use LATEDOCK to use floating panels now, no more. But LATEDOCK has a lot of features, like a lot of them. If you actually go see its code, which is here, and well, it's hidden in these folders. But as soon as you get to the right one, you realize how much code is in LATEDOCK. And you can just go into its settings to really see how many feature LATEDOCK has. So only LATEDOCK can be LATEDOCK, because we cannot have a panel out of the box that has so many settings, so many functionalities, and necessarily more bugs than before. Because if you add so many things together, it's going to be bugger compared to that if you have less features. That's necessarily true, sadly. So no, we cannot just make sure that all LATEDOCK features are available natively. That's simply impossible to make that happen. Now, one very important thing about LATEDOCK version 11. So when Plasma 5.25 was announced, LATEDOCK version 10, which is the latest version, didn't quite work on it. It had too many bugs. And sadly, this is still the case. If you download stable LATEDOCK and use it on the latest version of KD Plasma, it just won't work. It will work with too many bugs. So so many bugs that, again, the maintainer, which now stepped back, actually asked not to use that version of LATEDOCK in KD Plasma 5.25 at all. So it says if you are using Plasma 5.25, you should switch to LATEDOCK version as soon as possible. And let's remember that he also said that is not going to be able to release LATEDOCK 11, which means that this will remain a Git version. And you have to install the Git version and not the stable version, which means that, of course, a person won't know this. So they will install LATEDOCK, which is the stable version is version 11. And it's going to be buggy. So currently we are in a very bad situation already, because the stable version of LATEDOCK is super buggy due to KD Plasma. This is not fault in LATEDOCK. It's due to KD Plasma. And why is that? Well, LATEDOCK actually uses a lot of APIs from Plasma. And not all of those are stable. They can change between releases. So every release of Plasma, we should make sure that LATEDOCK actually works in the latest version of KD Plasma. And in this case, Plasma 5.25 birth enough changes for LATEDOCK to require some bug fixing. And this will have to happen for each Plasma release from now on. Now we are already lucky that LATEDOCK version 11 has the bug fixes, even if it's not released, but at least it has the bug fixes for Plasma 5.25. I think most of it or at least, but Plasma 5.26, 27, 28, who knows. So at this point, it is up to us, KD Plasma developers, to make sure that LATEDOCK still works for each version. And that's not easy because LATEDOCK is a very big project. But luckily, there's a lot of people on the Plasma project, and many people that are way more skilled than me. So hopefully that can happen. But if you were thinking about, I don't know, new features coming to LATEDOCK, that's simply not going to happen, I'm afraid, because that would add even more burden to the maintainer, which we currently don't even have. So this means that it's not like we can just stick LATEDOCK and expect the features of LATEDOCK to continue working at infinity. We actually need to work for each KD Plasma version to make sure that LATEDOCK doesn't fall behind. And in theory, LATEDOCK 11 should be published sooner or later. We can't just tell people to use the Git version. They're going to use the stable one for the most part. So somebody has to publish them. I don't know who's that going to be. Surely not me, because I'm not able to do that. I have no knowledge in that sense. So I am a bit worried, and all of that has to happen for LATEDOCK to continue existing or without bugs in the future. So we need to step up and work on it. I'll try my best for each Plasma version to actually test this kind of bugs, but only so much I can do. So hopefully I've seen already interest from other KD Plasma developers. So hopefully that's going to be enough. And if not, I am a bit scared. I have to just say that.