- User Since
- Jun 10 2019, 12:57 PM (36 w, 4 d)
Aug 3 2019
I updated the goal and developed the ideas a bit more extensively. I am unable to take leadership and push forward the acceptance of this goal in the KDE ecosystem (not programmer/developer; just humble user).
Jul 1 2019
Moved to discussion workboard to have further input !
Jun 28 2019
I would like to receive feedback and suggestion to complement and finalize this draft. Some parts still feels sketchy and may need more work. Feel free to correct spelling also, as English is not my native language.
This is essentially a rewrite and merge with T7050. I didn't put the same list of "willing" and "interested" people as I can't assume responsibility for them; they will have to make a stand if they wish to support this goal as they did with T7050.
Reverted to old. Changes where put in T11075
Jun 25 2019
In progress of merging with T7050
I did a big overhaul of the description and added my ideas. Any suggestions/changes ? Waiting for feedback.
Jun 21 2019
By kde-izing, I mean that it could be possible to do it partially. Like writing a module to access KDE account/identity api. I don't see the value to rewrite all UI components to Qt, but some parts can check if running in KDE and access certain features. I do like plasma-browser-integration, so it could work both way.
Also, I raised some issues in T11069 about the security of some KDE application. @dvratil wrote about certain applications running on legacy code and in my vocabulary, that mean unmaintained and dangerous.
I do know that CVE- are important for many business/organisation and quick response to CVE might be a important deciding factor.
While thinking about security, I just checked CVE details for KDE.
Personally, I prefer using KDE apps as packages of my system. They are up-to-date that way. I tend to forget to upgrade flatpak and snaps. Flatpak and snaps should be more of a sandbox and I use it for unsecured/closed source applications. I see no reason to leave distribution's repo for other store.
Jun 20 2019
I'm not too familiar with massive deployment. What features do others OS/Desktop provide, is there a list ? Is LDAP the most important part missing ?
Linux is already tailored for massive deployment, it could become a solid candidate.
Would it be possible to do a list of what's already in place (system side/kde side) and what's missing ?
What about security, usually there is a mandatory antivirus and prohibition from running any not authorized application (like running a .exe from USB or installing an application). Can this slow KDE piecing the corporate market ?
Jun 18 2019
Also, should KDE review it's default key mapping ? I end up having to configure switch desktop up/down/left/right to crtl+alt+arrow. Are there many other default mapping that could be added ? also never found what was : alt+shift+backtab ...
Jun 17 2019
The way I wrote it, it's more about the relation between the user community and the developers than the prioritizing. It's not about how we should prioritize, but how to organize the information so the developers can have a global vision of what are the needs of the users as well as which bugs are affecting them and if possible in what proportion and gravity.
Jun 15 2019
I agree, the title needs to be reviewed.
I changed the task description and put it less specific and more general. This is so it can address the underlying situations that possibly leaded to stagnating bugs/problems lingering for many years.
Jun 14 2019
Also, I believe KDE settings are not saved in a consistent way in the .kde & .local directories.
Easy import/export of KDE configuration could enable more seamless integration instead of just sharing a /home folder.
Jun 11 2019
Jun 10 2019
I do believe that this requires immediate attention. I tend to end on forums of distributions (like many others) for kde related things because of the state it is currently in. Searchability and aggregation of information must be easy.