Difference between revisions of "Activity Team/Obsolete/Zero Sugar Use Cases"
< Activity Team | Obsolete
Jump to navigation
Jump to search
| Line 15: | Line 15: | ||
* user(or distributor), by setting policy, can prefer only packaged versions | * user(or distributor), by setting policy, can prefer only packaged versions | ||
* user all time can pick up recent version from developer | * user all time can pick up recent version from developer | ||
| + | |||
| + | == Per user Sugar on a stick == | ||
| + | |||
| + | Assuming that most of activities are follow Zero Sugar workflow and activity developers want to support packagers, it is possible to create live DVD/USB images on [http://wiki.opensuse.org/openSUSE:Build_Service_KIWI|demand]] just by using OBS [https://build.opensuse.org/ web client]. | ||
Revision as of 01:32, 30 June 2010
How Zero Sugar could be useful on examples.
Natively packaged or directly from developer activities?
Zero Sugar could help with optimizing developer-to-distributor-to-user model. For example:
- developer lets 0sugar create packages for major GNU/Linux distribution on OBS
- distributors, either using native OBS features (like links and branches) create their own compilations of activities on OBS or just attach/copy OBS packages, compose repositories with activities for end users
- on end users side, sugar will understand that there are packaged and direct activity instances
- user(or distributor), by setting policy, can prefer only packaged versions
- user all time can pick up recent version from developer
Per user Sugar on a stick
Assuming that most of activities are follow Zero Sugar workflow and activity developers want to support packagers, it is possible to create live DVD/USB images on [1]] just by using OBS web client.