🍌/Obstsalat

From KDE Community Wiki
< 🍌
Revision as of 11:52, 20 September 2024 by Sitter (talk | contribs) (Created page with "* 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 ** 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 "...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
  • 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
    • 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")
    • backups: dolphin integration to roll back files
    • dolphin integration shebang for google and office365 and nextcloud --- goes back to companies to keep these working
    • make people see that their 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
    • developer story using sysext needs figuring out and documenting
    • 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
  • 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 minimise the rest
  • 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
  • collect some sort of perf data on app start ups and stuff and evaluate that somewhere and somehow
Retrieved from "https://community.kde.org/index.php?title=🍌/Obstsalat&oldid=101644"