 Okay, so, yeah, we're going to talk about Fedora Kinoite, which has just been released and it's the Fedora Certified Release Party. So it's the right time to talk about that. So quick agenda, I'll discuss where we are, what's coming like real soon, like in the next few months and then coming next, although the next releases and things like that. Okay, so a quick reminder for Zoos that haven't been following and for newcomers, it's always fine to get our minds updated. What's Fedora Kinoite? So essentially, Fedora Kinoite is a variant of Fedora. So it's just Fedora, but packaged in a little bit different way. So it's attached to the Kidi SIG, the Special Interest Group, which maintains essentially all the Kidi packages in Fedora. So it's 100% from Fedora RPM packages. So what's in Kinoite? What's in Fedora? There is no changes. The basics ID behind this is that you are trying to create an immutable desktop operating system. So immutable does not mean that it does not change, but means that you control or it changes. It's just like the words we use for, for example, in infrastructure, when you say immutable infrastructure, you do not say that your infrastructure would not change. You say that you control precisely how it changes. And that's the same idea here. We wanna make a desktop variant of Fedora with the Kidi desktop where we have a great control of all the desktop change. So yeah, as I've said, we're featuring the Kidi Plasma desktop environment in this full glory. And we are now officially released as part of Fedora certified. So it's body time. Okay, so what comes with Fedora? So initially, this is titled Why Fedora? Because outside of Fedora, folks might wonder why we want to base this on Fedora. And but here it's more about, okay, what's in Fedora right now in Kidi Fedora that we take advantage of? And well, okay, we'll know that Fedora gives us a stable and up-to-date software stack. And in Fedora, we've enabled Wayland by default, Piper by default, system to user sessions for Kidi sessions. So all that comes in and it's even been available for one release right now. So it's all in Fedora certified. We as the Kidi Seag Special Interest Group, we try to follow the latest upstream release of all Kidi. So if anything is out of date, if it's not there already in raw hide, it's in a sense it's a bug. So it should be there. And we try to make sure we update on time. We are very active, we are active and we meet all weekly on Monday. So feel free to drop by if you wanna to work with us. All right, so what makes it different from a classic Fedora workstation installation or the like that? Well, we're based on RPM history to manage the system. So we'll see what this implies, but essentially it's replacing the classic DNF way of doing things and the way of managing packages by RPM history. We use flatback to manage applications. So most of the time you will want to use flatbacks because it's a better user experience. And finally you get containers with potman, just like you would get on a regular workstation installation. But here it's much more emphasized because as the system by itself is more control regarding changes, you will want to run most of your tools, development environment, and the like that in containers via potman. So in a sense, we are very, very close siblings, sibling of Fedora Silver Blue, which is based on the same technologies. Okay, so yeah, the end goal of all of that is to make sure that we provide an easy dissatisfaction for users. So RPM history manages the system and makes updates of the system basically a non-event. So when you update, everything happens in the background. You just reboot into the new version and that's it. You don't have package conflicts or things like that or broken systems or partial updates, none of that happens without RPM history. It's just like either it's there or it's not there. And you know the errors, the conflicts before hand, you can resolve them quite frankly at your own pace on the common line or anything like that. And you just reboot and there you go, you're into the new version. So the database are atomic. It's like they work as a single image. You can still modify a little bit of things in there, but essentially that's the idea. On top of that, we use flatback. So flatbacks makes installing application really easy for users because they don't conflict with anything on a system. It's just essentially they are independent and you can get that from several sources. You either get them from federality, you've got pure open source software from there and you can get a mix of proprietary or free and open source software from flatback too, which makes this really useful. And finally, you get toolbox. So toolbox builds on top of Podman and you get to install any packages that are already in Fedora or any other distribution for that matter. And you run them in toolboxes and you get all the packages directly onto this. And it's a great way to work around the current limitations of the system. So the other thing we're gonna do is make things great for testers and early adopters. So all of those who wants to try the new version, try a new package, trade bugfix, or even a regular user, which for example, might wanna try the bugfix of a specific package that has been made by developer and provided as a flatback. And for that, you can do two things. So with our industry, you can try new versions very easily because you just rebase your new version if things don't work or if you just wanna go back, you can easily go back to the previous one and that's it. And with flatbacks, you can do the same. You can install several versions at the same time in parallel and there's no issue. You can even test like versions from PROS, for example, for those that have set up to get a version example here. And finally, we wanna make this a very safe environment for developers. So the idea is when you have our industry, I can even maybe show this if I have time in demo. You control all the system gets changed. So you control or you wanna do development or change specific packages for development. And this makes really easy because if you screw up anything or if you just wanna go back to stable version, you just reboot essentially your system and that's it. Yeah, and you get the same experience with flatbacks because as flatback don't mess up your own system, don't touch your system directly. You can just install any version of any library or any framework, even outdated ones when you need it for some applications. And that's fine, you don't have restrictions, you can use anything that's available. Okay, so that's like the safe right now, what we have. And yeah, I'll make a short demo right after and just for that, I wanna talk about what like the biggest things we have missing right now and we will work on focusing on work right now. To make this coming hopefully before Fedora 36. So the first thing, the first item is the latest Plasma the new version of Plasma, which has been released a little bit while ago, like a couple of weeks ago, short to approximately a month now. And as the KDC, we follow the upstream releases. And so the latest version has already been in Rohit for a while, we made the essentially the releases as soon as they were available in Rohit. But for Fedora 34, 35 right now, we're still on the Plasma 22 because of an unfortunate timing between the release cycles for Fedora and the recycle focus for the KDC Plasma desktop. So essentially they're a little bit hard to think. So we had to block, essentially we had to say, okay, we don't wanna block the release, we'll skip this one and we'll do this right after. And that's fine. So essentially it will come as an update really, really soon, so in the coming weeks. And we'll do that very soon. So we will come for Fedora 35 first and then for Fedora 34 next. And of course, as Fedora Kinoai is Fedora, don't forget it, we'll just get the dates like everybody else when it gets released to Fedora 35. All right, so we have a couple of known issues and I'll try and focus on that in the coming months. They all tracked into the Fedora KDC tracker which is linked there and you can find it easily from the KDC patch. Essentially they are not like big issues. Well, some of them are blocking for some users and understand that but essentially it's mostly like paper cuts. So things that impact the user experience and makes it not great to use the system. And sometimes you, most of the time we have got work rounds to make sure that things work, still work. So yeah, the general idea is, yeah, we don't have a gris for everything right now and you still need to use the command line. So that's something good to know if you wanna try a Kinoai. So first, the flatbacks. We don't have yet Kili flatbacks available. We'll talk about that every soon, just after. We're missing our PMO Street supporting Discover. It's still in progress, there's still some bugs. And we've got a big bug if you use UTC time zone. It creates havox on the desktop. So please don't use UTC time zone for now. Just switch and switch back later. Okay, so our PMO Street supporting Discover. It's the initial support was made as part of the season of KDE by a student by an Egyptian students. And she did a great work to get this started but unfortunately we still have like one big bug that's there and I haven't been able to track it down. So it's still in progress, upstream is linked here, the work and well, the command line, you can still use a command line. It's not great, but it works perfectly from the command line. So what would it look like? So essentially you get this kind of things that when you open this Google when I fix this last bug, you will get the older versions of Fedora can write your install in system, the packages you've layered on top and you can just get updates directly and apply them from Discover. So this should work once the bug is fixed. Flatbacks, so essentially we are flatback support building and we just don't have any KDE application built on the Fedora infrastructure. So you've got already all the non-KDE application that are available in Fedora. You can install all of those and they just work but the KDE apps themselves, they are not yet available in as Fedora flatbacks. So we're still working on that. I hope and I think I've got good hope that we should be able to bring that during the Fedora certified release. It's not breaking change. So it's just adding packages into the remote. So it's fine. Once we've got figured out the few bugs that are blocking us here, things should progress much more quickly because we already have a lot of KDE apps available. But that's not really blocking right now. If you're comfortable with using flatbacks from FlatHub, you can just install Zeus. You've got a lot of non-KDE applications too from FlatHub. You can do everything. And we're quickly trying to bring a lot of KDE applications to FlatHub and essentially what I try to do when I package applications is do FlatHub first, make sure they work well, push the fixes upstream and when everything is upstream and updated and then I work on the one in Fedora. So this is mostly, most probably what we often makes for applications. And FlatHub is also a great place to fix application close to upstream because it's really close. It's using later installables and everything. So usually it makes it easy to develop and fix on things. Yeah, there's another easy task. If you wanna get started with either flatback, KDE development or packaging, it's quite easy to get started in low effort, low involvement. I would say the fixing a bug sometimes takes is difficult, but to get started, it's rather easy and doesn't need to be and can get you started with both KDE development, flatback packaging and things like that. All right, so that's what's coming like really, really soon and then I'll get a brief discussion about what's coming like in the future. So long, more long-term future, maybe if it were such a six, we don't have a specific timeline with just things we're working on. So the main plans are that we wanna make this best platform to try the next version of either KDE Plasma, KDE Plasma or the application. So for that, we have to make sure that we wanna bring like the latest, either the latest get these branches directly as packages, as something built and available as a remote in Fedora Kinoi so that you could try daily builds of the KDE Plasma desktop directly on your system without having any issues. So if you like hit a major one, you can just robot the previous version and keep working. And at the same time, we wanna make this better for KDE applications to bring them from upstream development, likely builds as flatbacks directly on your desktop too so that you can try them and keep their stable ones installed as well. So that you keep all the stable ones, you have the nightly ones on the side and you can try them, report bugs, develop everything. Yeah, so to make that, we wanna do is make a different stream of Kinoi. So right now we have one stream per major Fedora release. So one branch per Fedora release and we'll probably create a new one, which would be based on stable Fedora, but with the latest KDE stuff. So you will get like both things, the benefits of both like trying new Fedora, new KDE with the stable Fedora base so that we don't shift everything at the same time, just like roll height essentially shifts a lot of things at the same time. So it's sometimes difficult to track and difficult to use for testing just a single part of the system. And this would be interesting because you would have just like KDE Plasma being in stable in a sense and the base keep being Fedora stable classic. And yeah, this would be very interesting for early adopters. So here it is. So one last thing we're missing is logo. We still don't have a logo. So if you have any art skills, feel free to join and feel free to drop by. We would really appreciate that. And feel free to join us. So at the KDC, we made on Mondays on 18 Android UTC and we track all the issues in the KDE SIG tracker. We have a website now, which is nice. Thanks to Carl and some docs which did a little bit of love. Even if they are like should be functional right now. And yeah, and that's about it for the demo. And are there any questions right now? Otherwise, well, not for the moon. That's it for the presentation. Now I can do a demo and there are questions. I don't see questions. Did I miss something? Thanks. Okay, so let's share my screen and let's see what I can share. Oopsie, yay. All right. So right now, this is my laptop running Federico Knight. So if I go there and type RPM or S3 status, which is the classic way of using RPM and S3 to get the system. So you don't see my pointer. It's a shame. Oh, you can see the highlight at least. So yeah, so essentially we're running Fedora and there is release of Fedora 35 here. You've got the version there and I've got. So I said that RPM S3 manages the system as an image. So essentially when you update the system, it updates the whole system, a whole set of packages as an image and then you move from version to version. So that's the version number you've got there here. And on top of that image, you can still install packages. So you're not locked into the image and you can change things. You can either remove packages or add new packages and which is what I've done here. So I have a bunch of layered packages here on top, which are used frequently. So I've added them to the image directly to be able to do certain things. And yeah, the common two-studies. And then you've got the rollback deployment as we call it. So essentially you usually have always two versions of the system available at once on the system. So it's just like Fedora CID VABU. You get two when you update the previous one, the latest one gets cleaned up garbage collected. And the one you were running gets pulled back at the previous deployment. And so if I do an update, essentially I will get a new deployment here. So if I go ahead and type sudo rpm3grade, yep, essentially I will be pulling the new version and deploy it right. So that should be fairly rather quick. We'll see. If it's too long. Yes, well, it's the wrong, let's keep moving on. So yeah, rpm3 status. What can I show you next? So yeah, so for those who are not familiar with all rpm3 system work, essentially, yes, I don't have to use sudo with rpm3 for all the operations that I'm used to doing that. Sometimes I forget. Yeah, the file system is laid out a little bit different. So maybe not as the key to this one. So essentially we'll have slash user being read only here and the system slash here being still read only, but it's planning to date that to be read write, but planning to date that to be read only. And slash boot is still read write right now, but hopefully we'll make it read only too, just like slash boot UEFI should be read only. And that's the main difference. So you know, it's still running. So yeah, I've got a bunch of flatbacks installed. So if you look at the flatbacks I have right now and so my systems, I got a good chunk of them. I've got the GNOME builder, the game, boxes, I think that's like a lot of things. Other key applications, most of them are for a Flap Hub because right now most of them are available there. Okay, how are we going to do the date? So yeah, so I'm looking at the date and this is both at the same time, if dating is a system and dating all the packages that I've overlaid. So this takes a little bit of time. It's much faster when you only have just the image because it doesn't, our industry doesn't have to do all the work for you and you can just move to new ones, but here I've got both the image and packages. So it has to do both and reduce it and need drawing first and either that. So it takes a while. Do I still have questions? Yeah, I do have questions. Okay, if I had to pick one thing that I need help with right now, what would it be? I would say a Flat Pax because right now what we're missing the most on the system is Flat Pax. So we don't have Flat Pax as built by Federal Infra and it's needed a little bit of debugging to figure out why they don't build as Flat Pax. And any help, any application that you like, that you wanna see be in Fedora via the Flat Pax either in Flat Hub or in Fedora, feel free to reach out and try to work on it because like packaging, key application from Flat Hub is not difficult usually. And what's like missing usually is like a little bit of tweaking or some fixes, small fixes in upstream packaging, in upstream sources to make this work better with Flat Pax. And that's where we would really benefit from the help. So the other question is, what's this question? Yes, you can do, yeah, so you can either, if you wanna run the key application right now, you can either, you have three options essentially, you can either get them from Flat Hub if they are there, you can install them into a box and run them directly from the outside from the toolbox it should work mostly because the toolbox essentially has access to all the things usually some Flat Pax application have, even more, most of the time. And the third option is directly overlaying them on the system using RPMO history installed. So it's just fine. You will just get an overlay packages on top and just like a classic Fedora KD installation, you will get the application and it will be available. So when I should use a package as a layout package versus toolbox, so it depends on the, it very much depends on what the application do. So sometimes if you wanna have the application modify things, access things on the host or thing like that, you will have to use them as a overlay packages. But most of the time you can run them from toolbox and they will work just fine. And which is like not really nice, not fully there yet, but it just works. And that solves most of the issues, especially the availability right now. But yeah, I'll say try toolbox first and if things break, add them as an overlay package because it's much faster. One thing to note is so right now I've finished your date right now here. And so if they did a bunch of packages, I won't reboot because this will leave me out of here. So I don't want that to happen. But yeah, if I go and see the status, you will see we have got three versions now and the next one is just right here waiting for me to reboot to get into it. Yeah, it's usually it's better to try with toolbox because running them in toolbox is just free. Essentially, you don't get any issues. But as you can see here, we've got a bunch of application there and most of the kitty applications aren't really special so you can just overlay them and it will be fine. So overlaying packages is fully supported. It's just not always as convenient. And one thing I want to point out is that you can do art industry install and then dash dash live, dash dash apply live, apply live like this and use specific packages. So let's say I wanna add a straight and what this will do is it will install a package and switch the currently running version of the system with the version with this package temporarily. So you will get this in the next reboot and in the current boot. So you don't have to reboot every time you install one package. You can do that live now. It's a new feature in our industry. Keyboard mappings or macros. So essentially what's in slash home. So it's VAR home on our chemistry systems is untouched by our chemistry. So anything you have in slash VAR home, so all your home directory is completely untouched by our chemistry and you won't get anything change. If you want to move from, let's say, Libreface configuration that you have right now into the one used by a flatback, you will have to copy to import it into the right places because this won't get auto-imported. All right, I'm meeting the mark for this session. So thanks everyone. I hope this was a nice, gives you a nice introduction of what we've done here. And yeah, see you shortly and see you in the key to meetings if you want to help. Thanks everyone.