Unity's relations and dependancies on GNOME
Unity still uses many GNOME bits. This session aims to discuss if Unity as a desktop environment should it distinguish itself by rewriting certain utilities for itself?
What are some issues when sticking with GNOME?
-Sound effects module has been broken for some time and needs a rewrite. We need to make customization of effects/
-Menu editor and other gnome-specific preferences that do not apply to Unity are accessible from Unity's dash causing confusion and a diminished user experience.
- Preferences set for Unity are used in GNOME (Ubuntu Classic) although some users want independent preferences based on the desktop environment used.
- Certain programs still require a systray icon. Certain application do not integrate into the Unity side-bar properly. There are issues with running some software in Unity.
[Still in Draft - Please add other issues to be discussed]
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- komputes
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Drafting
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Whiteboard
FWIW, I do not agree that the sound effects needs a rewrite. Yes; there have been problems - and logout sound is still broken, but that's more of a resource/priority issue. I believe the time spent on rewriting libcanberra is better spent fixing the existing system up. // David Henningsson
