Jump to content

KDE Linux/Obstsalat: Difference between revisions

From KDE Community Wiki
← Older edit
Sitter (talk | contribs)
KDEDevelopers, trusted
354 edits
No edit summary
Ngraham (talk | contribs)
KDEDevelopers, Administrators, trusted
1,800 edits
m Ngraham moved page 🍌/Obstsalat to KDE Linux/Obstsalat
 
(3 intermediate revisions by 3 users not shown)
Line 8: Line 8:
** detect when kwin is no longer responsive due to load and offer a way out of it
** detect when kwin is no longer responsive due to load and offer a way out of it
** detect when memory is being hogged and offer a way out of it (notification "yo this is using lots of ram, how about we kill it")
** detect when memory is being hogged and offer a way out of it (notification "yo this is using lots of ram, how about we kill it")
** "integrity" check for desktop environment components: detect when an important process (e.g. portals, kded, powerdevil, ksystemstats) is missing because of a crash, attempt to recover
** backups: dolphin integration to roll back files
** backups: dolphin integration to roll back files
** dolphin integration shebang for google and office365 and nextcloud --- ensure we have companies in the KDE surrounding that can make sure these things are well maintained (i.e. foster a healthy eco system of KDE adjacent companies)
** dolphin integration shebang for google and office365 and nextcloud --- ensure we have companies in the KDE surrounding that can make sure these things are well maintained (i.e. foster a healthy eco system of KDE adjacent companies)
Line 16: Line 17:
** binary diff sysupdates need creating -- zsync?
** binary diff sysupdates need creating -- zsync?
** encryption: verity subvolume on btrfs?? figure out a good story that requires a single auth even with encryption
** encryption: verity subvolume on btrfs?? figure out a good story that requires a single auth even with encryption
** developer story using sysext needs figuring out and documenting
** developer story using sysext needs figuring out and documenting. Check out https://gitlab.gnome.org/tchx84/sysext-utils Might just be what we need to make things more accessible
** switching editions via updates kcm and maybe the sources list in discover
** switching editions via updates kcm and maybe the sources list in discover


Line 24: Line 25:
** explore having branded usb sticks to deliver to community members and in conferences
** explore having branded usb sticks to deliver to community members and in conferences
** talk to hardware vendors
** talk to hardware vendors
** ARM/RISC-V images?


* sandbox:
* sandbox:
Line 30: Line 32:
** KIO: needs thinking. make a daemon let it spawn workers
** KIO: needs thinking. make a daemon let it spawn workers
** anything else: sysext / toolbox for now, should minimize the rest
** anything else: sysext / toolbox for now, should minimize the rest
** Explore systemd-homed
* quality
**Automatic QA (openqa? Selenium? quicktest?)
** Human QA tracking (test case management of some sort)
** Health reporting into Sentry to identify bad releases
** Support sending non-KDE crashes to Sentry


* recoverability // never dead
* recoverability // never dead
Line 37: Line 46:


* security
* security
** Secure Boot
** CVE/security updates: there is an atom feed of fixes
** CVE/security updates: there is an atom feed of fixes
** firewall?
** firewall?
Line 48: Line 58:
* virt-manager flatpak -- maybe write a kirigami kvm client (there is https://invent.kde.org/arraybolt/karton)
* virt-manager flatpak -- maybe write a kirigami kvm client (there is https://invent.kde.org/arraybolt/karton)
* collect some sort of perf data on app start ups and stuff and evaluate that somewhere and somehow
* collect some sort of perf data on app start ups and stuff and evaluate that somewhere and somehow
* building it
** Better kde-builder dependency definitions
** kde-builder to build release tags

Latest revision as of 18:33, 12 November 2024

This is the Obstsalat (fruit salad 🍇🍈🍉🍊...). They are facets of the 🍌 experience. The OS is just part of the story.

  • plasma wayland experience ( remote desktop story. easy sharing. convertible story)
    • remote desktop by token or by ace
    • nearby sharing: via kdeconnect?
    • should sharing and remote desktop be the same thing from a UX perspective?
    • session restore. rebooting needs to be a breeze because users restart a lot for updates
    • detect when kwin is no longer responsive due to load and offer a way out of it
    • detect when memory is being hogged and offer a way out of it (notification "yo this is using lots of ram, how about we kill it")
    • "integrity" check for desktop environment components: detect when an important process (e.g. portals, kded, powerdevil, ksystemstats) is missing because of a crash, attempt to recover
    • backups: dolphin integration to roll back files
    • dolphin integration shebang for google and office365 and nextcloud --- ensure we have companies in the KDE surrounding that can make sure these things are well maintained (i.e. foster a healthy eco system of KDE adjacent companies)
    • make people see that their software product is of crucial importance and must be well maintained (bug triage, forum support, MR commenting)
    • input methods installed. fcitx, ibus, maliit, qvk
  • atomic os
    • binary diff sysupdates need creating -- zsync?
    • encryption: verity subvolume on btrfs?? figure out a good story that requires a single auth even with encryption
    • developer story using sysext needs figuring out and documenting. Check out https://gitlab.gnome.org/tchx84/sysext-utils Might just be what we need to make things more accessible
    • switching editions via updates kcm and maybe the sources list in discover
  • adoption story
    • windows and osx story needs polishing
    • make sure isoimagewriter is a nice tool to use
    • explore having branded usb sticks to deliver to community members and in conferences
    • talk to hardware vendors
    • ARM/RISC-V images?
  • sandbox:
    • plasmoids: see to how to list them and spawn the process. Integrate it into the UI
    • apps: flatpak and snap
    • KIO: needs thinking. make a daemon let it spawn workers
    • anything else: sysext / toolbox for now, should minimize the rest
    • Explore systemd-homed
  • quality
    • Automatic QA (openqa? Selenium? quicktest?)
    • Human QA tracking (test case management of some sort)
    • Health reporting into Sentry to identify bad releases
    • Support sending non-KDE crashes to Sentry
  • recoverability // never dead
    • a/b guards against some breakage
    • recovery mode for breakage outside a/b
    • recover user data mounts all stuff
  • developer experience
  • centralized management story to keep in mind // monitoring: hook into systemd
  • eco system of companies to provide support -- ticketing system
  • apple: no. banana!
  • virt-manager flatpak -- maybe write a kirigami kvm client (there is https://invent.kde.org/arraybolt/karton)
  • collect some sort of perf data on app start ups and stuff and evaluate that somewhere and somehow
  • building it
    • Better kde-builder dependency definitions
    • kde-builder to build release tags
Retrieved from "https://community.kde.org/index.php?title=KDE_Linux/Obstsalat&oldid=102138"