Hi, As Richard declined my request #864095 and I got some comments on my earlier request #863654 I would like to sent an email now with the reasoning of my request. (also added beforehand as a comment on the build page for the patterns-microos [1]). Thanks for pointing me in the direction of how to get my changes approved. First of all, I am NOT a developer, I am merely a guy who understands computers as a hobby and is really into the idea of an immutable OS for desktop usage. This was my very first commit to something on build.opensuse.org and my second on an openSUSE project [2] (and in general). I was not aware that we first need to discuss a few package additions via the Mailing List + add the change to the changes file + re-add my previous comments on my old request and comment on the main build page. I was just thinking that I would help out by trying to do these changes by myself so it would safe you some time. As I have installed MicroOS on my laptop several times now (been using it since Dario created his blogpost with how he got it up and running), installed it on my family's computers and have helped numerous people with their setup of MicroOS as a desktop install. Some of these people are experienced linux users, some are not. My request for nano is based on my personal history of linux as almost all manuals on the internet (that I have used in the past) talk about using nano and nano is actually understandable from a beginner level on how to safe and exit the program, vim on the other hand is NOT. Also making changes to files inside the transactional-update shell can only be done from the terminal. I understand MicroOS desktop is sharing a base with MicroOS as a server and Kubic. I would assume more knowledgeable users install MicroOS as server or actually have a use-case for Kubic. Desktop users (and especially beginners) are different, they follow manuals online and need help in getting stuff done. MicroOS Desktop, for me, is not a minimal install with an additional layer of difficulty of installing packages and making it usable. For me it is an extra stable installation where the root file system can't be changed during boot, so doing an upgrade it will not harm my current system and if something failed it automatically boots into the previous snapshot. This is for me a very reassuring idea as I use this laptop for work and don't like to hotfix trouble with an upgrade, while I do like upgrading everything when there is a new release. My MicroOS install ,with 1,397 packages (of which 1,339 (rpm), 49 (flatpak) and 9 (snap)), has for example snapd + a few other repos from OBS and Firefox installed as a RPM with Packman enabled, as I do not think Flatpaks are the answer for everything and I do not feel comfortable using Toolbox for everything else. (for Firefox for example downloading kept going wrong on my Firefox flatpak and I had to restart every download and then it would work; plus a rpm install of Firefox is usable for installing extensions, I did try it with Chromium, but about 4 out of 10 times that I go to extensions.gnome.org, Chromium crashes.. And I also don't enjoy installing chromium for just that use-case) As such I am proposing the following: Include these packages in patterns-microos-desktop-common: - nano; explained above, it is a beginner friendly text editor; - bash-completion; I prefer the completion to make sure I type the commands correctly plus it safes time; - unzip; moved from gnome-pattern as it is also usable for KDE (or future different desktop environments); - wget; moved from gnome-pattern as it is also usable for KDE (or future different desktop environments); - nfs-client; I'm sure other people want to automount usb drives too; - autofs; I'm sure other people want to automount usb drives too Also to remove kdeconnect-kde from the desktop-kde pattern as i don't think it is necessary for every install + if someone wants it they can install it easily themselves. I understand this email got quite a bit longer than I first anticipated, but I just want to make my self clear that even though MicroOS for desktops is still in an Alpha state, I want to bring this project further and make it actually usable for most users, including those that do not understand linux in the same way that you (the developers) do. Thanks, Syds [1] https://build.opensuse.org/package/show/devel:kubic/patterns-microos [2] https://github.com/openSUSE/openSUSE-docs-revamped/blob/dev/project/docs/mic...