Plasma/Workspace Sprint/Games/ProductTreeRaw

Tree Structure

Product tree

Important base characteristics:
 * Web apps and services integration
 * Applications integration
 * Adaptability to the user workflow

Trunk:
 * Notifications management
 * Windows Switching
 * Gestures (Leverage Advanced Features of Existing Input Methods)
 * Screen Management
 * Adaptability to different form factors

Core Features:
 * Widgets Dashboard
 * Pulse Audio support
 * Present Windows
 * Seamless sync between services
 * Prioritize resources based on the activity or workspace

Lesser Important Features (to hide from user Pov):
 * Widgets on the desktop
 * Modify network settings
 * Support for new input methods
 * Windows Snapping
 * Per Activity Power Profile

Marginal features (droppable longer term):
 * Virtual Desktop switching
 * Add/Remove Virtual Desktops
 * Per Virtual Desktop Wallpaper

To drop:
 * Separated Dashboard and Activities

Observer 1 Notes

Discussion about criteria for placing in the tree: importance vs timeline (picked importance)
Digression about usefulness of gestures
"Feature was not there in the 10 year old tree"
Vertical axis implies dependencies
Help the user to switch to a better workflow but provide a fallback (e.g. icons on the desktop still available even if "deprecated")
Deciding left part of tree is dedicated to activities
 -> Activities are more and more important
Discussion on web app data access:
 * How far should we go in our synchronization
 * Strong resistance against web apps

Facilitator addendum: Last point doesn't map with my own experience, nor the other observer notes

Observer 2 Notes

Present Windows: less important than windows switching
Focus follows eyes: feasibility? Future
New input methods is important: focus on gestures with touchscreen or touchpad
Per activity power profile (e.g. presentation example)
Files in context of an activity: important
Follow user workflow: Something for the future, rather important
Widgets on the desktop vs Dashboard widgets: Make sense together?
Windows Snapping: useful or not? nice to have, not really important
Activity switching: important
Window switching: supports the whole experience of the workspace
Desktop switching: disagreement power user only vs useful for all
 -> Activities vs virtual desktops
Modifying network settings: new solution coming, not so important (seldomly used)
Per activity power profile: not so important
Notification system management: very important
Wallpaper for virtual desktops: not important
Windows Snapping Settings: not needed?
Integrating web into KDE: how far you reach into the web resources?