Yes I am involved in the project. As for not worrying about large system upgrades, things break, no matter how much testing you do on them. For running KDE I prefer to run the latest, it has the least bugs and the newest features.
There will be at minimum 3 editions of this OS, one for developers and those who love to live on the bleeding edge, one for enthusiasts and one for general users. The one for general users will be well tested and aim to have zero showstopping bugs.
Same steps, different base, no customisation, upgrades on day 1 of release. Probably a few more things. I also ❤️ Kinoite so nothing against them.
I'm a bit the same but I tried the switching between versions and it's amazing.
The existing distro Neon has issues generally because of their choice to use Ubuntu LTS as a base. This is because KDE Plasma needs newer libraries usually than Ubuntu LTS can provide so they add newer libraries in their repository which often breaks existing apps in the Ubuntu repository. Having to patch and bring newer libraries all the time takes its toll. Basing it on Arch means they'll almost always have the latest libraries ready to go.
Ah I see it's just Lemmy failing to get the thumbnail that I was trying to fix. I guess it's just something in Lemmy's code.
I would jump into the KDE Connect Matrix room: https://go.kde.org/matrix/#/#kdeconnect:kde.org and the KDE Mac room: https://go.kde.org/matrix/#/#KDE-Mac:kde.org to discuss. Builds are now done on GitLab directly, but it may be the case that nobody has set up the CI builds.
More information: https://community.kde.org/KDEConnect/Build_Craft
This is one of the biggest annoyances I've come across with them for sure.
Generally using only a few flatpaks is where it's generally "bloaty". Adding more actually balances out the equation ans you have more apps using generally shared runtimes.
Ah yes. I used to have a GTX 1060 and was pretty pissed off when they said the new open source driver would only support from 1660 onwards (or is it 1630)...