In T17370#310581, @vivekanandanks wrote:

Not quite what u would expect/prefer but still want to put this suggestion up:

1. Rebasing KDE to an Immutable Distro will get the job done?🤔
2. Using a declarative OS like Nix will solve the issues when something messes up ?

In T17396#307765, @ngraham wrote:

...
I do think it's good to have more 3rd-party apps, though. Oftentimes we absorb 3rd-party apps so they become first-party apps, and the result is better integration — but I think this is not ideal. You shouldn't have to formally become a part of KDE to integrate properly within a Plasma environment.

Definitely +1 for more touchpad gestures. Especially the lack of pinch to zoom in Okular has annoyed me since ages (and because I used it today: also in Skanlite).

It might be best to merge this as a subgoal into https://phabricator.kde.org/T17396 which is all about easier App creation and already has "Enable support for other languages" listed as one aspect.

I would definitely be available for testing.

Some of this seems to just boils down to better support of systemd-homed

I would also like to see some kind of rating or tier system for KDE apps and a consolidation of efforts. There should be a clear stance which apps are part of the core KDE ecosystem (e.g. Konsole, Discover) and which ones are not. Currently the https://apps.kde.org/ site is very overwhelming and I am not sure which quality/maturity to expect from the apps found there.

There is already k{read,write}config{5,6}. It would only need a switch to dump all configuration and a list of all files to dump (which is harder as they are not consistently in the same place).

I agree that the current scope is quite narrow and seems more like a feature request. However, a few other things which could be added would be support for FIDO login and in general any non-password based login method. Similarly, the scope of KDE Wallet could be expanded to support TOTP etc.

Another approach for scriptable add-ons and plasmoids would be to run them inside QJSEngine or WASM. This would still allow them to run in the same process but enables strong control over the exposed APIs