BrandingForDerivatives
1693
Comment: add "interested" line
|
1781
add priority
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
## page was renamed from UbuntuDownUnder/BOFs/UbuntuDevelopment/Branding | |
Line 8: | Line 9: |
* Status: BrainDump, DistroSpecification, UduBof | * Status: BrainDump, DistroSpecification, UduBof, HighPriority |
Branding
Status
People: ColinWatsonLead, NeedsSecondBR
Contributors: MarkShuttleworth
- Interested: put your wikiname here
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.
Requirements
- Provide for branding or neutralization, as appropriate, of the following components:
- Installer
- Boot loader splash image
- Boot loader text
- Debconf templates
- Package selection
- Live CD
- "Starting Ubuntu..."
- Base
- Archive keyring?
- Debconf templates?
- lsb-release? (hard)
- Boot
- USplash image
- "Starting Ubuntu..."
- Desktop
- GDM theme
- Splash graphic
- Default wallpaper
- Installer
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)
Pre-Work
Review [http://www.ubuntu.com/wiki/DistributionDefaultsAndBranding DistributionDefaultsAndBranding] against the above
Thoughts/Suggestions
UbuntuDownUnder/BOFs/BrandingForDerivatives (last edited 2008-08-06 16:23:24 by localhost)