⇤ ← Revision 1 as of 2010-04-27 11:49:56
Size: 1799
Comment:
|
Size: 1792
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 17: | Line 17: |
* Kiko Reis, NewCo | * Kiko Reis |
Derivative Distributions
XXX - more text here
As an OEM provider
I want to make a customized version of Ubuntu
so that I can ship the OS best suited to my hardware
Rationale
Why are we doing this now?
What value does this give our users? Which users?
Stakeholders
- Kiko Reis
- OEM Services
- cody
- smagoun
- ???
Constraints
What MUST the new behaviour provide?
What MUST it not do?
Subfeatures
Brainstorming:
- File a bug upstream, where upstream is the parent distribution
- Official package branch maintenance for derivatives
- Full archive services for these distributions
- See the difference between a derivative and its parent
- Which packages are newer / older
- Copy packages over without rebuilding them
- jml isn't sure if this is a thing
- Support different release cycles from the parent distro
- OEM case is frequently a small, finite number of releases
- Translations?!?
Workflows
What are the workflows for this feature?
- Create a derivative distribution
- ???
Success
How will we know when we are done?
One possible measure: when we can build Debian on Launchpad the way we build Ubuntu.
How will we measure how well we have done?
Thoughts?
- Check over the Ubuntu owner / bug supervisor etc model and see if it's relevant to non-standard projects
- Look up past literature on this subject
- Image building suddenly becomes way more interesting with this
- A distribution that's just customization practically demands to be
- played with
- A distribution that's just customization practically demands to be
- What Ubuntu-specific scripts are we running against Launchpad
- Is this a for-pay service?