BrandingForDerivatives
1074
Comment:
|
2640
lsb-release
|
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 17: | Line 30: |
* Help texts * Dialogs * Express Intaller(UbuntuExpress) * Artwork (Logos, images..) * Help texts * Dialogs |
|
Line 26: | Line 45: |
* Grub menu entry * Grub theme |
|
Line 30: | Line 51: |
* Default browser homepage * Default browser boomarks * Gnome/Kde theme * Menu * Apps on "Add/Remove programs" * Icons on panel and desktop * "About Ubuntu..." (System Menu) |
|
Line 31: | Line 59: |
= 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 76: |
= Pre-Work = | == UDU Pre-Work == |
Line 44: | Line 78: |
* Review DistributionDefaultsAndBranding against the above | * Review [http://www.ubuntu.com/wiki/DistributionDefaultsAndBranding DistributionDefaultsAndBranding] against the above * |
Branding
Status
People: ColinWatsonLead, MartinPittSecond
- Contributors:
Interested: MarkShuttleworth, MattZimmerman, JuanjeOjeda, AndrewFitzsimon
Status: BrainDump, DistroSpecification, UduBof, HighPriority
- Branch: n/a
Pending: MarkShuttleworthQueue -- braindump needed.
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:
- Installer
- Boot loader splash image
- Boot loader text
- 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)
- Installer
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
- 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
Review [http://www.ubuntu.com/wiki/DistributionDefaultsAndBranding DistributionDefaultsAndBranding] against the above
UbuntuDownUnder/BOFs/BrandingForDerivatives (last edited 2008-08-06 16:23:24 by localhost)