 So the speech went up and we talked about our previous year's programmes, what went wrong, how can we learn from our mistakes. We are as well known for Season of Killing 2016 and how we can select students, beggars and do our selection process and make them into programmes. We talked about all this. Yeah, that's it. I'm not ready. How to make them more effective? The mission, like I said, the mission works as a protocol. As a protocol, really doesn't matter. Yes, indeed there is a protocol. It was useful to organise the pre-school programme. We just took a mission draft and looked at what the results of the survey were and tried to edit it based on the survey results. And then some doubts came up about whether the KDE mission should have any aspects in it which relate to the products or should only be about what KDE provides in the form of infrastructure, support, social things, whatever. And so we now basically have one. This is not IIC. So we talked a lot of stuff, among them being the notion to have whale and body fought in the Unstable which is essentially the version that is tracking master. Which should hopefully be happening within the next couple of months. We also did talk about making SNAPs, that is one of the fun formats, more accessible from within Neon. And we also decided to move forward with a thing called Offline Updates. Offline Updates is essentially installing updates at start-up rather than during run-time. This is how I was able to do for the user edition. So basically the release software that is meant to be stable. I think that's more than it. We also did a bit of cleanup on how we're going to do. Discussing a lot of topics there. That's about it. That was good. Thank you. So basically we made a point of what is currently the status of KDE. We discussed what was missing, what should be implemented yet. And yeah, basically it's that. So I have no work now. It's good. So I have a question of Peketuna desktop client. I showed some features of it, like what it can do. But said to implement it and how to get involved with it. We also discussed some ideas about the design. And how to use Kirigami UI with it. So it's going to be interesting to have other ideas. Thank you. We discussed what the need was, what if it was really needed. If what feature it should have to be relevant and what we should process. So basically we have almost a plan which is already good. We'll see what happens. Here is the GPL licensing. And then we discussed, started discussing how we could also add a GPL code to KDE. And afterwards we started discussing the future of the FLA licensing. And the FLA licensing policy. And we're going to continue this discussion just after the work. Mostly about discussing technical aspects and going through the mock-ups that we have one by one. And see where we are, see where things should be changed. One of them was a new framework coming up. The K-20 that is being ready for being a framework. Then we talked about, LACMA wants to make an LTS release for what? That's an MTS release for one year. And we agreed that this means there is a version of framework probably after the 6th. Which will also be kind of an LTS. Because we have to basically do security fixes for it. We don't want to have a branch where everyone can contribute lots and lots of changes. We just open the possibility to have very severe bug fixes or security fixes that are no branch. I can do that with cherry picking. And then we discussed issues with the CI when we push version changes to 70 frameworks. And the CI shouts for help. And then we discussed a lot of things we forgot. We talked about killing, we wanted to kill in KHTML and KJS for security reasons. We can't yet do that because there are still views in a few places. So if your code is using KHTML, go and fix it. It's actually not that much. Probably just three or four places in the whole code that we have. And then we finished with Sebast's desire to revive the plugin loader cache. To make the plugin loading faster. And so it's going to look into that again. It's work that we started a year ago. Which might actually come to completion one day, maybe possibly. Thanks. Thank you very much. Recent release and what's missing there. And what we really need to fix urgently before the next release. Which is hopefully coming up in like two weeks. So like a patch release. Then we talked about outstanding stuff we need to work on. Like, especially in our client integration. And ideas on how to fix that and improve everything. By the way, modules is the new thing. Everyone should use modules. What else was there? Windows is basically done. There's one or two debots related deadlocks in cubed upstream. Which need to be fixed first. Then what else? Oh yeah, we talked a bit about UI related things. Workflow related things. How we could possibly fix them. But mostly this is like, we are still aware of them. We still have no time to fix them. And hopefully we'll be able to do this eventually now. And yeah, I think that's pretty much it, right? Yeah, thanks.