Derivative Distributions
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
As a Linaro partner
I want to create a new distribution/archive in the hosting software in 3 or 4 clicks
so that this does not require deploying a new instance for each distribution.
As a Linaro partner
I want this new distribution visible only to a certain set of people, and only a subset of that group can upload
so that it's easy to see who is in each of those groups on a single page, at most 1 click from the overview page of the distribution. It is also simple to modify each of the groups, with at most 3 clicks required to add or remove someone from one of the groups.
As Meg who works for a partner enabling pre-release hardware
We are doing this so it's easier for Linaro partners and Canonical's OEM team to build custom distributions. This brings Launchpad's famous usability and feature set to more people who want to use it but currently have to use 3rd party products to do this.
What MUST the new behaviour provide? Nice to have:
(see use cases above)
How will we know when we are done? From https://wiki.ubuntu.com/Specs/M/ARMArchiveBranching: There will be a number of milestone testcases that we have: How will we measure how well we have done?
Creating a new derived distroseries: New portlet for the distroseries page: Showing packages differences:
I want upload modified packages to an archive for a hardware project
so that others who are working on the project can then build on top of this work.
As Lou, the lead developer on the project
I want to go to a web page and see the current state of the archive
so that I am able to remove some obsolete packages. This can be done from a single page, and is at most three clicks to remove a package. Bulk operation should be possible.
Rationale
Stakeholders
Constraints
Workflows
Success
Mockups
Thoughts?