 So, I will be speaking about the mobile, which is our operating system, which is developed commonly or only in community. We are developing it on the Pine phone, which I have here. We are developing it on the Utie Pie. And yeah, let's look how it looks like. So we have tested the system also on Pine phone Pro, which I don't have, but the other guy, Sergei have Pine phone Pro. There is Vola phone, which is developed by German company Vola. And one guy from Ukraine, if I remember correctly, Luca Panio, developed adaptation for Vola phone, which is based on Hallyum, so basically it is using Android kernel, and it works somehow. We are still in very early phases of development, I would say, I'm doing that about one year. And there is more features, which doesn't work than which works. You can also port your own device. And if you want to do so, I will try to help you with that. So what works and what doesn't? Well, main features are working, so user interface, keyboard, Wi-Fi, it mostly works. Also the phone calls work somehow. It's connected, but the audio is not transmitted or not going to the speaker. So I can send those devices if you want to feel the experience. So the QTPi, the tablet is a Raspberry Pi-based tablet. Main issue with Raspberry Pi is that it doesn't have power management, so the power button and the battery charging is made extra, and it's not supported well by standard drivers. So it doesn't show the level of battery, and you are not able to turn it off simply by clicking on battery. Those devices are in presentation mode, so it doesn't go into sleep mode right now. The Nemo Mobile was originally based on Sailfish OS or on Mare Project. The Mare Project is me, you're resurrected, if I remember correctly, and the Mare Project had pretty old components, and it was very tightly built with Sailfish OS, or the Sailfish OS was using the project and maintaining it similar, like Red Hat is working on Fedora, and the Red Hat mainly decided what direction the Fedora be, so in case of Sailfish OS and Mare Project it was similar, and finally the Sailfish OS guys decided to take the components from Mare Project and to maintain it inside its own distribution. There are some differences, so we decided not to maintain some components, we decided to go to new version of QT, we decided to leave their security model, so there is a sale jail, there is some MDM machine device manager, if I remember correctly. So we are trying to make it simple, and we moved to Manjaro because we don't want to maintain GCC and those things, we just want to make the mobile operating system, so I personally want to work only on UI and phone-related stack, but not how-to tools, for example. So how it looks like, this is overview of the components or applications you can see in them on devices, and the user experience is, let's say, poor, but we are working on it, we are still using all QT quick controls, we want to migrate to QT quick controls 2 and QT 6, we want to reuse KDE PIM stack instead of QT PIM, because we don't want to maintain QT PIM, we want to return all our changes to upstream, so we don't want to maintain more than we really need. We want to keep compatibility with other distros, if possible, so it would be great if we can run applications from Sailfish OS, but the Celica API is closed source, but it can be re-implemented, and actually there are some experiments with that, so if you want, I can point to the right repository and you can improve the port of Celica, and for sure we can be compatible with Plasma Mobile or Ubuntu Touch. So how you can start with the NeoMobile, we have pretty nice web page where everything is described. Basically I started with installation of Manjaro on desktop, I have installed all the packages, there is some command which selects all packages from certain repository, and you end up with this kind of system where you just run lipstick command and you have the basic user environment from the mobile phone. Then you can start some application and debug it, develop it, whatever. You can also start the application independently in Qt Creator for sure, and then you can debug your application. The architecture is pretty much similar to Sailfish OS one, so all the communication with hardware is done through some middleware, so for Modem it is Ophono. We are considering migration to Modem manager, but Ophono works for us somehow so far, and the communication with those middlewares are done usually through the bus. So those are applications. So you can install it in this way in your virtual machine and do it like that. Who have PinePhone here? I have one. Okay, you can install it on PinePhone very easily, so just grab the image and use DD or maybe also Fedora Media Writer and you have a bootable system, but right now you should either take the virtual machine or you can try to port it to some Android device. We have those Qt quick controls which are used for basic user environment. Everything could be visible on our website, so it looks like that, so you can use those progress bars, et cetera. Then you have the home screen which is built on Lipstick and Glacier Home, so Lipstick is the compositor, Wayland compositor, and there you have those three home screens, one with a list of applications, one is the task switcher, and the third one is event feed, and this is lock screen, and then you can see all the applications with some screenshots which we are trying to update sometime. So I will be happy if you contribute or if you at least try it. You can contribute with documentation, as you can hear my English isn't perfect, so I will be happy if you fix documentation. I will be happy if you make some pull request on our reportatories. So most of things are on GitHub, and we are building it on top of Manjaro, so those aren't RPM spec files, but it's pretty similar. So this repository is like main place to know where to start, where to look for some component. So if you want to change dialer, you will see that it's Glacier dialer up, and here is a URL which is constructed by some variables. You can see also dependencies and everything, so this is like good place to start with code. I have linked all the repositories from GitHub, or the main repositories from GitHub to trans effects, so if you speak other language then check. There are plenty of work, and it's very easy if you don't know how to write a code, then you can probably translate, and in my opinion the translation is very good, starting point also for developers. When you translate part of project, then you know at least about its features, so it's a good way to start to understand how the project is built and what it consists of. Yeah, we are trying to do some nice user experience. The Nemo mobile is fully open source alternative mainly to Sailfish OS, but also to Migo Harmaton, so the user experience tries to be similar, and we are looking for someone who can make some mock up, who can draw some behavior which will be nice, user friendly, and we will try to implement that. For sure, if you are testing the device, you can give us the feedback, which is very important, you can tell us which parts are broken the most, and we will try to fix that. If you are happy with that, or if you like it, we will be also happy, let us know that you like our project. For sure, you can give us some money. That tablet I planned to buy from donation, but the guy from company was faster than me, and he sent it to me for free, so thank you. When you are trying to contribute with code, I am writing some summary report for project every month, and I am trying to summarize also bugs, and I am also trying to find some bug which will be somehow interesting, usually somehow different, so there is back to start with section in those blog posts, and the good way is to try to update your package and to build your own image and try it on your own device, and that's it. I hope there will be a lot of questions. The question is how to add third-party application to Nemo Mobile. It depends, so we are building it on top of Manjaro, so it depends if the application is native for Nemo Mobile. If it's not, then you probably can consider to package it for Manjaro, and it could be installed. By the way, if you are speaking about Moderna, which is your application, I already have packaging for it, and we can maybe try to install it, and you will see the experience on the device. If you are speaking about, let's say, native Nemo Mobile user experience, then you should start on your GitHub, and we will create some repository in our group, and we will merge your changes in that repository. Is that one answer on your question? Great. Some other questions? So, what do you think about devices? If you don't have questions, I have. Personally, I think one of the most important devices is, I think, still the pine for most likely, because that's something that's quite easily available, even though, like, the hardware is not perfect. I think it's important that you can still get it quite easily, as well as making the applications and the system run just on your computer, like, that lowers the entry barriers a lot, in my opinion. Yes, yes, I agree. Well, and it is good that PinePhone is running with more or less upstream kernel, so it's better than porting changes to some Android kernel and adapting the kernel to run with standard Linux tools. So, yes, the PinePhone is really, really devised to choose if you want to develop, like, open source alternatives.