 Okay, so hello everybody, welcome, and we are talking about bringing Plasma to something different, some other stuff. If you are here, it means that you are either working on developing or using or even just interested to much of the work that KD does as a community. Big part of this work, even though not all of it by any extent, is all the software that we write on top of the Qt library starting from those very useful extensions, which are the KD frameworks to all the applications that we write on top of them, write to having a whole desktop offering in the form of Plasma desktop and even having a reference packaging of all of it in the form of KD Neon. Of course there is much more than that, a lot of documentation work, graphical work and website work, which is also very important for us, but let's get back in the topic. We offer full desktop experience over the last 20 years, which have become really, really good, one of the best out there, but I would say, but I'm biased so what I can say. But yet it's still mostly that desktop offering, even if we are now starting to double on mobile application development, which is very good and very important, because right now desktop software is just a small part of the computing that people do with a vast array of devices. Mainly mouse and keyboard is an assumption that it's starting to become not completely true even for laptops that people are buying, which can be transformable or can have some weird way of user input that we were still not expecting. A big challenge of adapting also comes from hardware vendors, it also comes from actually making free software work at all of some weird hardware. So I will pass the voice to our resident hardware god, Bhushan. So, as Marco mentioned, the computing is no longer the desktop devices or laptop devices. Computing has evolved into this whole new set of devices like smartwatch, smart speakers or even the car info entertainment system which you can use to watch, listen to music or navigate or basically read your emails. So the question is, are we as a plasma or are we as a PD community, are we ready for this entirely new subset of devices or do we want to reach out to this user or do we want to make use of our KD software on these devices? So the answer to this question is largely, we are ready for it but not there yet. So to explain my answer, well, these devices, every device has their own user interaction method, user interaction method. For example, some devices will have a touch screen, some devices will be just, will be just a basic monitor, basic display where and you will be interacting with voice or other commands or remote devices, for example, in case of smart television. Also these devices will have a different range of hardware or actual computer inside it. So it means, well, every device is totally different. And to make plasma or well, as Mark was mentioned to make free software work on these devices, there are several challenges like vendor lock. These devices might be vendor locked in. This device will have no way of installing custom software on it apart from what is provided by vendor. There are still systems out there in market which are running end of life system software like kernel and people are still buying it. So I at least know two or three devices which are running 3.10 or 3.18 kernels and yeah. And also each devices have their own set of bugs or problems which I generally deal with like there is graphic drivers are not working, display subsystems is not working or even well you will have some kind of overheating problem or thermal issues or performance issues. So each device is totally complicated. So on the desktop generally it's a case of everything works and we have a small subset of bugs but here it's totally different. We have problems right from the start. And also solving this problem is not easy because most of this hardware is closed down, vendors doesn't provide any kind of hardware design or schematics or information to properly run the free software on these devices. Well, leaving aside problems, I'm going to talk about some of the solutions we in the KDE community are working on. So one thing we are working on is KDE frameworks. KDE frameworks is a set of KDE extensions. So Qt is already quite cross-platform and we also provide some set of the libraries and libraries for using on top of Qt. KDE frameworks is also cross-platform so you can use it on any hardware possible. We also have Queenwell and as a compositor which provides various rendering backends like DRM kernel mode setting which can be used on supported or fairly mainline devices. We also provide HW compositor backend which can be used on Android only devices where there is no way to get a DRM or KMS working. And we also provide a minimal frame buffer backend which is quite not so performant so it's not too much recommended. We also have some hardware specifics, features included right now in the Queenwell which is a DMA buff support. It is required for some specific new devices like Purism Sleeper 5 phone which is going to use IMX based parts so it will need a DMA buff. And while we provide the solutions, we also provide solutions to ship this to the wider community like we have a Yachter project recipes which I think Walker will talk about in his talk. I'm not sure. We also have a KDE Neon build infrastructure which builds for ARM HF and ARM64 so you can basically put it on top of open to ARM. And we also have a community efforts like PostMarket OS which provides packaging solutions for KDE software. So here you can see KDE Neon. This is actually desktop. It's running on Pinebook. It's a $99 single board computer. We have KDE Neon running with Plasma Mobile running on Nexus 5X. We have PostMarket OS running Plasma Mobile on the Pine64 phone. We also have a Yachter project page Raspberry Pi. And apart from just generally apart from just KDE software solution there are also some external companies, external communities which are working for making this whole process easier. Like there is a graphics driver community, there is a kernel development and mainlining communities which work on making this software much more open. There are several other companies like Pine64 and Purism which work on providing hardware as much as open as possible. And well, some people say there is new hardware which will fix it. Yes, it's a risky hardware which is supposed to fix all of the hardware problems but we are yet to see in the practice. So anyway, I will hand over to Marco who will talk about Plasma side of things. So when to actually decide I want to use Plasma in my embedded hardware project of course different hardware and different use cases are very different from one another both on a side of performance of the particular hardware will it be powerful enough to run what I need or also on a side of user experience. Does my hardware only need to show ever one single screen? Is it like a stupid sold-out vending machine or is it something more complicated? Many times even in very simple things you do have some concept in some way of applications even if they are really applications but just different functionality of the system that you need to start to switch among and to terminate then you need something that in some way acts as a primary user interface as a point of entry for the user. Also many times you will need things like notifications for things like a status area for things like the battery charge or the network connectivity and also having some UI to be able to configure that network connectivity for instance just a simple login to a Wi-Fi network which is very common for all those problems. Plasma has a completely great infrastructure has an excellent notification system has good wrappers on top of phone on a network manager that makes the developer that wants to do an interface on top of them actually not painful which is a lot. But you say Plasma is a complete desktop experience I don't want that in my embedded device my embedded device is something completely different and much smaller but what Plasma Shell actually is and in this context I am strictly referring to the Plasma Shell executable it's kind of a glorified QML viewer which is by itself quite tiny, quite light and doesn't have any UI by itself. All the UI that loads is what in the end the developer says to load in the form of first the Shell package and then the containers and then the widgets I will define all of that starting with the Shell package which is the lower level things that it loads in the form of QML files and configuration files it defines the behavior of the target system starting, we already have several of them we have the most known and used which is the desktop but the phone on Plasma Mobile has a completely different one even Plasma Viewer which is just a small testing utility it's a whole different Shell package by itself and lately we are working on a new one called Plasma Nano which is targeted explicitly for embedded devices here there are some examples of course Plasma Desktop that we all know and love then Plasma Mobile running on a phone which is a quite different Shell but yet kind of familiar on the bottom row there are three prototypes based on the new tiny Plasma Nano Shell they are all prototypes of complete UIs based around Mycroft which is a free software voice assistant with the other targets that shouldn't have Google listening to everything you say to it which is really nice the one on the left is Mycroft Mark II which hopefully you will be actually able to buy and it will hopefully become a real product in the middle a prototype for a larger screen version on the right an automotive prototype which Aditya will have a talk about it so everyone is invited to see that here comes the wall of text just being very quickly those are the various components that defines various customizations for instance a configuration dialogue of things can vary a lot between Shells here is the desktop Shell it has an appearance here is in the Nano Shell looks differently but also behaves differently on the desktop it has the Apply OK Apply Cancel button instead on Plasma Nano is everything is instant Apply same thing for Widget Explorer with Plasma Desktop and Plasma Nano things like that Shell could also say I don't want any of that in my Shell I want to be simpler you can also define that behavior of the main views a desktop is a desktop, a panel is a panel is a panel but on the phone the panel works differently it becomes a scroll down drawer kind of like Android and also the desktop behaves differently horizontal swipe becomes activity switcher which is all defined in the desktop package as I said all the new prototypes with smaller devices we are doing with Plasma Nano even Plasma Mobile will be based on Plasma Nano because one Shell package can kind of inherit from another one then the main UI that is loaded is Containments which is on the desktop the kind of file manager UI that is icon on desktops and on the phone is the main launcher you can also customize more with the look and feel package which is just cosmetic stuff and very, very, very, very quickly because we are running out of time this is the Minecraft Mark II package which I talked about this is a very early prototype the final version we have a nice case you talk to the device and the device answer is to you with voice and with a graphical representation of the answer all of that is in a Plasma Shell and it also has a top-down panel for configuring network for controlling sound volume and things like that if you want to know more there will be a above session on Tuesday everyone is invited I hope to see many of you I don't know if we still have time for questions