- Branch: n/a
Pending: MarkShuttleworthQueue -- braindump needed.
This specification describes our strategies to allow for the effective branding of Ubuntu and derivatives. Some branding can be attained without affecting packages, other branding initiatives will require derivatives to rebuild or even modify and rebuild packages. We will also refer to aspects of Rosetta that should affect distro branding.
Scope and Use Cases
- Provide for branding or neutralization, as appropriate, of the following components:
- Boot loader splash image
- Boot loader text
- Debconf templates
- Package selection
- Help texts
Express Installer (UbuntuExpress)
- Artwork (Logos, images..)
- Help texts
- Live CD
- "Starting Ubuntu..."
- Archive keyring?
- Debconf templates?
- lsb-release? (hard)
- USplash image
- "Starting Ubuntu..."
- Grub menu entry
- Grub theme
- Application defaults
- GDM theme
- Splash graphic
- Default wallpaper
- Default browser homepage
- Default browser bookmarks
- Gnome/Kde theme
- Apps on "Add/Remove programs"
- Icons on panel and desktop
- "About Ubuntu..." (System Menu)
- Debootstrap script
- We have discussed several approaches to branding, and in which cases they are useful:
- The Rosetta team has done some initial work to mark branded strings
- Neutralizing strings
- The simplest case to handle, and requires no effort to re-brand for each derivative
- We should apply this technique wherever possible
- Runtime substitution
- Appropriate for simple circumstances (e.g., Apache version string, Mozilla version string)
- Can use lsb_release, and have a reasonable chance of having the code passed upstream
Add liblsb to provide the functionality of lsb_release as a library and use it for identification strings.
- Collect brand data into central locations
- Works well for artwork
- Works well for gconf configuration data
- Build-time branding
- There are hard problems to be solved in the packaging system and in Launchpad before we can manage a separate build for every derivative
- This isn't achievable for Breezy, so for the near term we must avoid it entirely
- Branding human-readable strings
- Upstream software hardly uses distro-specific branding, so we can deal with that on a by-case basis.
- Most branding applies to debconf templates, debian-installer is the only package that really needs branding (other packages should be neutralized).
- Most of the installer branding can be neutralized.
- For the remaining cases, we have two (nonexclusive) options:
- Translate the remaining few cases manually to properly catch Linguistic issues (plurals, genders, tenses, etc.). This would require additional complexity and effort in order to avoid duplicating work across distributions which target the same languages.
- Try to catch the most common cases with a global macro (debconf already supports per-package macro substitution).
- Use special-case macros, but since they have to be maintained somehow, this could create more problems than it solves.
- Human-readable strings must be translated, so retranslation is required after branding them
- Try to neutralize where possible instead
- Needs to be different in every derivative
- Used by tools such as reportbug (don't fall back to Debian!)
Possibility to create a tool to derivate distros: [http://software-libre.org/moin/Meta/en/BrandingSystem Branding System] (not checked translation from [http://metadistros.hispalinux.es Metadistros] subproject)
UDU BOF Agenda
- Runtime branding, build-time branding and package-selection branding
- Which approach is most suitable for each requirement?
- Can we avoid build-time branding entirely? It causes big infrastructure problems
- Branded CD builds
- Debconf branding
- Refactoring desktop branding
gconf schemas, etc. (<dist>-branding)
Review [http://www.ubuntu.com/wiki/DistributionDefaultsAndBranding DistributionDefaultsAndBranding] against the above