BrandingForDerivatives
1210
Comment: pri
|
1656
update for new format
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
= Priority = | |
Line 3: | Line 2: |
NeedPriorityAssigned | = Branding = |
Line 5: | Line 4: |
= People = | == Status == |
Line 7: | Line 6: |
* ColinWatson | * People: ColinWatsonLead, NeedsSecond[[BR]] * Contributors: MarkShuttleworth * Status: BrainDump, DistroSpecification, UduBof * Branch: n/a * Pending: MarkShuttleworthQueue -- braindump needed. |
Line 9: | Line 12: |
= Goal = | == Introduction == |
Line 11: | Line 14: |
Implement a mechanism to allow simple, centralized branding for Ubuntu derivatives | 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. |
Line 13: | Line 16: |
= Requirements = | == Requirements == |
Line 35: | Line 38: |
= Agenda = | == Agenda == |
Line 46: | Line 49: |
= Pre-Work = | == Pre-Work == |
Line 50: | Line 53: |
= Thoughts/Suggestions = | == Thoughts/Suggestions == |
Branding
Status
People: ColinWatsonLead, NeedsSecondBR
Contributors: MarkShuttleworth
Status: BrainDump, DistroSpecification, UduBof
- 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)