 Well, KDE is all about the apps. It's been our goal for the last year. It's worth checking out what's happened in the last year, how we can improve it for the next year, how we can control the site. First, we're reminding ourselves why we picked this goal last year. Perhaps we're always part of the KDE story. It was always part of the plan from day one when Mateus and the other one started it. It was to create, not just the desktop but a suite of applications that went with it. A suite of applications that worked well together, looked good together, had the same usability, looked and feel. And that was a great goal. And we achieved that along with the desktop. We achieved that within a few years and we've improved it ever since. But the tech world moved on. It turns out, somebody rejected patch from somebody else and then another desktop got started and a whole bunch of other desktops got started. And that's freedom for you. And well, we never did monoplyze the world in the way that Microsoft did. And that's probably not a bad thing. So other desktops came along, other application suites came along, other form factors came along. Of course, there were networks and web apps and smartphones. And other platforms came along. People either used to be people who stood on Swarchforge or KDE or a similar project. But now you just start a project and get that or GitHub or something. So there's no shortage of competition for people who want to make a pre-software open source app. No shortage of places they can do it. No shortage of communities that they can work with. And that's been fabulous for the open source resource as well. But it's meant that we've been stuck a little bit in our niche a little bit. A little bit too focused on our apps being for KDE. And even when KDE became the community and even when KDE became the people and the plasma brand that separated out, there was still this mindset, both within our community and in the broader computing world, that these apps were for KDE and if you weren't using plasma, then they probably weren't that interesting too. And that means we missed out. And of course, then the other change in the computing ecosystem is the coming along of AppStores. So we've now got AppStores for Linux. And there's also AppStores for Windows and Mac and Android and maybe iPhone. And because of changes in the licenses, cute, we can take advantage of this. But we've had a bit of an attitude problem with our AppStore. As I say, we're too stuck in this mindset. Not just us, but people out there and people within KDE and everybody within KDE are not playing in particular, but that mindset exists that we think are for KDE because that was the original vision 20-odd years ago. Even though that restricts us to a niche of a niche, it doesn't allow us to promote our applications on their own terms. And it means that we get a bit too much weather to the idea that we must be separate from the distributions and we can't ship our own software because we've depended upon them as distributions for a long time and they've done a big service to us and continue and always will. But it means we haven't taken control of our own applications too much. And we've been too scared that Mac and Windows are a bit evil and a bit not to be touched. And I've had long and passionate arguments with people within the KDE community where we did a release of KDE applications and I was told not to promote the AppStores that our apps are on. I was told not to promote the channels that we have to ship our apps directly because they weren't quite complete at the reveal. There's some bugs in it or maybe we're a bit too scared of doing the security updates or a bit too scared of those new responsibilities that come along with shipping our stuff directly or we don't want to offend the distributions or so forth. And again, that means we've missed those opportunities. We're a bit too nervous. And also the attitude exists that packaging shouldn't be part of the application project. It can be a KDE project but it should be a separate project and that limits how it is for those applications to be able to take control of their own destiny. So we picked the goal. All about the apps. We're going to focus the market on KDE's applications and the way that we have done for Plasma and Plasma now stands low in its own brand and it's got a lot of recognition amongst Linux users that it's a great product and it brings us back to being a leading desktop, lightweight, feature-ful, simple, indeed powerful, so mighty powerful when needed. But the apps in our marketing got a bit left behind and in our effort to push them out to users and get those communities. So what have we done last year with KDE is all about the app school. We had KDE applications as a name for the three-month, four-month release. But then that duplicates that name, that branding is just a bit duplicated with the general concept of applications in KDE. If you want to talk about KDE applications, which one are you talking about? So we de-branded that because it shouldn't matter how it gets released for the end user, even for distributions, people don't care who makes those release tarbles. People care when there's a new version out and what those features are. So we de-branded that. It's now just a release service and it dumps tarbles every four months. And it means that changes can be made like here on the KDE.org front page. Carl and others redesigned that to highlight some of our top applications and some of those are part of that bundle, some of them are not. It doesn't matter. What matters is that we're promoting those now directly on our front page of KDE.org. And you can see some of our flagship apps here across pre-sale. Everybody talks about KDE. Live is wonderful. Contact is classic and beautiful and full of potential and KDevelop is for the never side there and works great. And you can see from the screenshot that we have these great apps and users don't care how those go out. And also on KDE.org we tied up the applications pages. We now list all the applications that the pages made automatically. It's got a few bugs you can see in there so that needs a bit of quality assurance. But we download those from the metadata files and AppStream means that we can control our metadata. This is pretty basic stuff but it was a long time coming where we say here's a description, here's an icon that goes along with it, here's a screenshot and here's when the release is up. So within these application pages we've now changed that website or improved that website. So it now has an install on limits button. You go there on Linux, it says install on Linux. You go on a different platform, it says install on Windows or whatever. That's using the AppStream URL. We were the first people to use that I think and it's not even a URL right so the specification is buggy so we had a few pictures to make there. But then you can just click on that and it'll open up Discover or Knome Software Center or whatever, open your application. And that application will pick the best method to install. And we as coders don't just have a strong opinion about what that method to install is. That's where the user can decide what sort of packages or container age formats are best for them. So you can see here on Krita underneath it, it has options to install on Linux and that uses the AppStream URL but also on the Microsoft Store and Google Play Store. But you can also see further down, it has release text. So when there's a new release, they can add it to that AppStream file that then appears on this website and it can appear anywhere else that can automate that and suck it away. It also shows how you download, do a direct download of AppStream files for Mac OS or Windows or get the source. So for the first time now, if someone goes, oh, there's a new release of Krita out, how do I get that? They can go to our website and they can get it. And while I'm using this as an example, they don't want to put a user's Krita as an example because it's a thankshift app and it does everything right but it nicely gives a smooth experience to the user. Along with the de-branding of the KDE applications, we did the monthly app updates. So we are actually doing some promotion of our apps. What's happened in the last month? One of these 200 new titles are being released today. Those are synced with the release service releases. But they're not being pushed up. They come from anywhere within KDE, self-released. Again, with de-branded, the idea of extra gear is just self-release application. It shouldn't matter how the release happens, but it matters what the shiny new features are. So we're promoting DigiCam, picking your release 7, Dolphin, and not only does it promote the application, but it promotes how you get those applications. So it says you can download this app image, you can install it from stats, you can install it on Windows and so forth. And I've also included the occasional review of app stores or interview with somebody who's worked on the app store just to promote the idea that these channels are out there and they're a great way to get our apps. So to review all the channels out there and a great way to get our apps, and we've kind of spent my time doing about 10 minutes and 15 minutes. Q&A will sound before we go on. One minute to Q&A. What? I thought I had nothing out here. Well, so we've got the snap store here that's made by KDE Neon mostly, our stuff. But also other people have accounts there, and they've got a nice feature, coming up on Monday, and that has most of the applications in KDE. You can see where those packages come from, and you can see metrics on them. So that's one of the nice changes that you get from this stuff. So Krita has 42,000-dollar installs, Ocula has also 42,000-dollar. Color Paint, 15,000 installs. Flat Pack, you've got a load of applications there, and that's made by... They've got a talk later today, so go and see that. And in FlatHub, app images by nature doesn't really have the store, but a lot of applications use that as a way to say, here's a trivial way to get our application, and they can take full control of that, so that's been quite popular with the number of them. Not just Linux app stores, but also package managers on Windows. Chocolate is a package manager on Windows, and people who manage lots of Windows machines have to be sitting there early. They use that as a good way to get their software. We've got three or four applications for you to sit here on that store, and that's a good way to do some work. Do I need to stop now? Is there some Q&A now? If you'd like to start Q&A, I can start reading you the questions. Go for it. One question to go. All right, so first question says, in the beginning, you mentioned iOS as a possible target for apps. There is some interest in that target in the Maui project, IARC, and also in Cayden. Do we already have a system that could be reused for iOS, for example, Kraft, or is something new? iOS is difficult. I don't know. Homebrew on macOS has worked quite well. That's a desktop application, so you're asking about mobile stuff. We brought Homebrew into KDE, so there's another package manager for Mac, mostly, and that's now been successfully integrated into KDE. Mac, we've got a number of stuff made for macOS, so if you look on Binary Factory, there's quite a few made there, and those are listed on the download pages. I've got a slide in here, a bag, Apple's App Store, no results. Possibly because it just smells bad, maybe you can't put GPL stuff there. I don't know, maybe nobody's had a strong interest. I did notice that Lever Office is there twice, so it must be possible to put free software stuff there, and I'm pretty sure it's the same on the iOS iPhone App Store. We've got nothing there, but there must be ways to do it. I'm afraid I don't know if Crafts can build successfully on those. I defer to Hannah and the others who do Crafts for that. Is there another question? Yes, so next question. Is it possible to have links to Android Play Store slash Freud on the website, for example, for itinerary or KDE Connect? So Android Play Store is another store that we should take advantage of, and we have a little bit. We've got a dozen apps on there, and it's interesting because it also allows commercialization. It allows for apps to have money next to them if they need it, and it's stupidly popular, of course, but it does need your app to be reconfigured for mobile. Is it possible to have links in the store? Yeah, I think it is. I think that's why I showed up pre-tact. Did that happen? Yeah, so on KDE Door applications, that's got a link to the Google Play Store, and I encourage anybody who has an app to put it into Google Play and get that in their AppStream file and then appear. But I had in my not quite success slide, FDroid, which is another app store for Android, free software, so it goes on for ideals, but so far we've only got two things there that I can find, and it would be great to have more things on FDroid. Is there another question? Next question is KDE Apps and the whole Linux itself. I'm not so sure about that, in quotes. Still are not friendly with some graphic drivers, like NVIDIA, sorry, not pronounced NVIDIA, or something, which makes users have to install lots of things. So what do developers do to fix and improve this? Well, the developers do fix NVIDIA, it must have run away in my experience. That's difficult, of course, because it's a long stack that graphics is on top of, and if something doesn't work, it'll go down, especially if NVIDIA is a limited matter that we can do. On the NVIDIA laptop that I have, I tend to just use the Intel chip on it, unfortunately. One of the failures of just the whole Linux ecosystem is that we're not always so integrated all the way down the stack, and it would be great if we were mostly talk to the Quinn developers, because they're the ones who know about graphics. That's all. No question? We've got a few more questions. Go for it. All right, so next one. As a developer, how do I reproduce the magic of packaging if I need to debug packaging slash builds or platform-specific bugs slash issues with my app? Example, KD Android SDK helps for Android. What else is there? Building stuff, you can build a lot of stuff with the craft tool which is exactly built on different platforms. Whenever I've built on a different platform, you have to have that platform with you or a virtual machine. I know for Windows, you can download virtual machines from Microsoft, which run on VirtualBox, and those are free to anybody to try. So if you're developing your app on Windows, then anybody can try that. I don't know enough Android to know the equivalent systems from Android, but they should be out there. All right, next question. Does promoting to make changes in their approach to de-emphasize the bundle or is the rebranding successful in meeting that goal? Is the rebranding successful of KD apps stuff? I don't know, because that's up to the people who have seen it. It doesn't make sense. It's still not quite perfect, but it's the only set-up that we could agree on. I like to think that in creating those monthly app updates that we've mostly successfully moved away from the idea that here's a bundle that's released today and gone into the idea that it's everything that's been released on this week, the other problem I have with those is stuff that gets put into distros and various forms in private repositories, maybe. And so people think they're available, even if they haven't been fully released to the stable one. It's tempting to say, oh, this is out now because we know there are a few people out there using that. And we're very keen in all about the apps, but also with my neon hat on to make the point that stuff needs to be released from KDE properly. And, yeah, occasionally, you get the odd maintainer who works for them, but so they don't want to make it atarable or they don't want to make a release and a tag. And that's the nice thing about the KDE community course is if you don't want to do some particular part of it, there's probably a team out there that will pick up the slack and help out. So we can certainly do that on more of the apps. I've done a number of releases. And the other side of that is incubators bring stuff into KDE, which is also part of the goal because the whole point is to make KDE an attractive ecosystem for an attractive place to develop your app. So it's an important part of the goal also is to bring stuff from outside KDE into KDE as part of that incubator process. And we've reviewed a number of ones this year. I think Raleigh Stream is particularly interesting and fun. It's a virtual role-playing, virtual tabletop software dedicated to pin-in paper role-playing games. And that's bringing in a whole new community that was there, new discussion channels even with Discord and whatnot who want to be part of our community. And that's just great to see. All right. Well, we have a minute to go and there are four more questions, but I will ask you the most important question of the hour. Who is the KDE baby? Who is the KDE baby? You want to introduce yourself? Just before we're locked down, I was feeling like we should have a bit more. We should have some om-gums here and some fine friends come along to see our talk. So what are you going to do with this one? Yeah, just letting you live up to it. Yeah, you will be a developer coming in soon. So we do like to help some projects through the incubator. Very cute. Jonathan, I will send you the remaining questions and you can do the questions in the Academy question or however you'd like. I'm sorry, I missed that. I will send you the remaining questions and answer those in the attendance chat or however else you'd like. Yep, attend these chat rooms. Okay, well, thank you so much, Jonathan.