Ubuntu Wiki

Please check the status of this specification in Launchpad before editing it. If it is Approved, contact the Assignee or another knowledgeable person before making changes.

• Launchpad Entry: hardy-theme

• Packages affected:

Summary

Creating a new theme from the top down for the next LTS cycle.

Release Note

Our target audience will be drawn to ubuntu because of the fresh bling and simple beauty of the OS. Through this we can fix bug#1

Rationale

Every LTS cycle should represent a concise design direction which evolves over the course of the cycle in a well planned and managed way.

Use Cases

Klaus loves pretty things, they make him smile.

Design

The color palette, design principles and examples will be explained in the Artwork teams wiki page (tbd)

Implementation

In order to complete this work we need to address the following:

Name

Every good theme needs a good name. The name Human was very descriptive although we made very little out of it. Finding a good name to explain the look and describing it well will make things easier.

Process

Defining a process for approval of the theme elements is very important and will solve problems later. All of this needs to be as open as possible.

Timeline

Accompanying the process for approval is a strict timeline to be followed to ensure there is ample time for testing and tweaking for cohesiveness and completeness. As this is an evolving process we will need to determine which pieces need to be done when and how to keep everything in line not only over the course of one release but over several releases.

UI Changes

As we create the theme this will have an impact on other parts (like compiz effects, etc). All of this should be inline and use the same design principles.

Code Changes

Minor pieces of code will need to changed. We need to find people able to help with this.

Test/Demo Plan

This need not be added or completed until the specification is nearing beta.

Outstanding Issues

We need to define a plan which is not only for Hardy but can also evolve over the course of the entire LTS cycle.

BoF agenda and discussion

Ubuntu

• Radically changed lots of stuff for this long term release
• Define the process:
  • Definition of the color palette in advance
• Start working on changes a lot earlier in the process to make sure any changes do not "break" other parts
• Find coders to handle the parts that artists either do not know or are not willing to learn
• Big Issue: Change the Name of the Theme
  • Either change the name to something like "Human 3.0" or...
• Everything we want to change:
  • Installer Picture
  • Usplash -- Traditionally Installer Picture and Usplash have used the same image
    • These two will be changed in Ubuntu, Kubuntu, and Edubuntu
  • GDM

    • GDM Face Browser Spec, https://blueprints.launchpad.net/ubuntu/+spec/hardy-gdm

  • Wallpaper
  • Application Splash
    • Keep as little as possible

    • GIMP and OpenOffice

    • Use the same in the Example Look section
  • GTK+ -- Work with a coder (Andrea Cimitan, Murrine-author) on this
  • Compiz Effects
  • Metacity
  • Installer
    • Show some form of graphics during the install phase, but do not think this is going to happen in this release cycle
  • Cursor Theme
    • Across Kubuntu,Edubuntu and Ubuntu
• Look at Tango Guidelines
• Color Palette
• Design
• Target Audience
  • Needs true defintion, current Target is "Everybody", working on defining who it will be
  • Will follow with the next "marketing" goal of 8.04 LTS
• WINE
• WUBI

Kubuntu

• Minor Changes, distinct important changes due to KDE4 comming out
• Changing the Desktop Splash
  • Discussing whether or not to use it, but this is a technical discussion and not an artwork/theme issue
• Amarok Theme
  • Will not change between KDE3 and KDE4
  • Need to change theme for Hardy

Ubuntu Studio

• Working with the Studio theme, how can we use all the different pieces and parts

Edubuntu

Xubuntu

CategorySpec