OEM/Carrier Customization goals for 14.04

Registered by Chris Wayne on 2014-03-10

Going over the current efforts to provide an API for OEM/Carrier customizations, and shaping the future of this system

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
Chris Wayne
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

Prototype documentation:
http://people.canonical.com/~achiang/ubuntu_savvy/

Launchpad branch for code, docs, and tests:
lp:savilerow

Prototype test tool:
lp:~achiang/savilerow/tailor-poc

Bug tracker:
https://bugs.launchpad.net/savilerow

Excellent prior art:
https://developer.mozilla.org/en-US/Firefox_OS/Developing_Firefox_OS/Market_customizations_guide

Customization Ideas:
One thing that I think we don't have support for is custom APs. So as an AT&T customer I autologin to their Wifi network.
customizing the launcher is common on android
system update settings might be worth overriding too
update frequency, automatic updates, update server etc.
need to look into oem/carrier updating only custom bits

Followups:
The proper name for the build artifacts that Savvy will produce is a "remix". See:

http://www.ubuntu.org.cn/trademark-policy

There are some corner cases about pre-installed click packages, but they seem harmless enough for now.

(?)

Work Items

Work items:
[achiang] figure out proper terminology for community remix?: DONE
[cwayne18] we need to add the custom.prop feature to docs: TODO
[cwayne18] add support for deploy to emulator: TODO

This blueprint contains Public information 
Everyone can see this information.