BrandingForDerivatives

Differences between revisions 1 and 23 (spanning 22 versions)
Revision 1 as of 2005-04-04 18:05:11
Size: 1074
Editor: ca-studio-bsr1o-251
Comment:
Revision 23 as of 2005-04-25 03:44:20
Size: 2714
Editor: intern146
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= People = ## page was renamed from DerivativeBranding
## page was renamed from UbuntuBranding
## page was renamed from UbuntuDevel/Branding
## page was renamed from UbuntuDownUnder/BOFs/UbuntuDevelopment/Branding
= Branding =
Line 3: Line 7:
 * ColinWatson == Status ==
Line 5: Line 9:
= Goal =  * People: ColinWatsonLead, MartinPittSecond
 * Contributors:
 * Interested: MarkShuttleworth, MattZimmerman, JuanjeOjeda, AndrewFitzsimon
 * Status: BrainDump, DistroSpecification, UduBof, HighPriority
 * Branch: n/a
 * Pending: MarkShuttleworthQueue -- braindump needed.
Line 7: Line 16:
Implement a mechanism to allow simple, centralized branding for Ubuntu derivatives == Introduction ==
Line 9: Line 18:
= Requirements = 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.

== Rationale ==

== Scope and Use Cases ==
Line 12: Line 25:
  * Installer   * CD
Line 15: Line 28:
  * Installer
Line 17: Line 31:
   * Help texts
   * Dialogs
  * Express Intaller(UbuntuExpress)
   * Artwork (Logos, images..)
   * Help texts
   * Dialogs
Line 26: Line 46:
   * Grub menu entry
   * Grub theme
Line 30: Line 52:
   * Default browser homepage
   * Default browser boomarks
   * Gnome/Kde theme
   * Menu
   * Apps on "Add/Remove programs"
   * Icons on panel and desktop
   * "About Ubuntu..." (System Menu)
  * Others
   * Debootstrap script
   * Defaults applications
Line 31: Line 63:
= Agenda = == Outstanding Issues ==

 * /etc/lsb-release
  * Used by tools to determine, e.g., where to report bugs
 * Posibility 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] subproyect)

== UDU BOF Agenda ==
Line 42: Line 80:
= Pre-Work = == UDU Pre-Work ==
Line 44: Line 82:
 * Review DistributionDefaultsAndBranding against the above  * Review [http://www.ubuntu.com/wiki/DistributionDefaultsAndBranding DistributionDefaultsAndBranding] against the above

 *

Branding

Status

Introduction

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.

Rationale

Scope and Use Cases

  • Provide for branding or neutralization, as appropriate, of the following components:
    • CD
      • Boot loader splash image
      • Boot loader text
    • Installer
      • Debconf templates
      • Package selection
      • Help texts
      • Dialogs
    • Express Intaller(UbuntuExpress)

      • Artwork (Logos, images..)
      • Help texts
      • Dialogs
    • Live CD
      • "Starting Ubuntu..."
    • Base
      • Archive keyring?
      • Debconf templates?
      • lsb-release? (hard)
    • Boot
      • USplash image
      • "Starting Ubuntu..."
      • Grub menu entry
      • Grub theme
    • Desktop
      • GDM theme
      • Splash graphic
      • Default wallpaper
      • Default browser homepage
      • Default browser boomarks
      • Gnome/Kde theme
      • Menu
      • Apps on "Add/Remove programs"
      • Icons on panel and desktop
      • "About Ubuntu..." (System Menu)
    • Others
      • Debootstrap script
      • Defaults applications

Outstanding Issues

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)

    • artwork (<dist>-artwork)

UDU Pre-Work

UbuntuDownUnder/BOFs/BrandingForDerivatives (last edited 2008-08-06 16:23:24 by localhost)