5,705
edits
Changes
Jump to navigation
Jump to search
Line 19:
Line 19: + + + + + + + + + + + + + + + + + + + + + + + + + + +
Activity Team/Obsolete/Zero Sugar Use Cases (view source)
Revision as of 01:12, 30 June 2010
, 01:12, 30 June 2010→Per user Sugar on a stick
Assuming that most of activities use Zero Sugar and activity developers want to support packagers (use Zero Sugar OBS integration), it is possible to create live DVD/USB images on [http://wiki.opensuse.org/openSUSE:Build_Service_KIWI demand].
Assuming that most of activities use Zero Sugar and activity developers want to support packagers (use Zero Sugar OBS integration), it is possible to create live DVD/USB images on [http://wiki.opensuse.org/openSUSE:Build_Service_KIWI demand].
== Easy activity development workflow ==
For now, developers:
* create .xo bundles
* choose server/service to host activity e.g. ASLO or just upload .xo somewhere on wiki
* for not python based activity, build code (for how many platforms/environments?)
* for activities that contain non Sugar Platform dependencies, need to mention it somewhere
* within sugar, only one stability activity versions exist
With Zero Sugar, developers:
* call {{Code|0sugar commit}} command to make newly created activity version accessible for users
* developer could release not only stable releases e.g. development, testing, users will know release stability status (without reading it somewhere) and by setting policy, could prefer only stable versions (or help to test development versions)
== Easy activity deployment workflow ==
For now, users:
* find out .xo bundle somewhere e.g. on ASLO or wiki
* after downloading, have to be sured that activity will run in their environment e.g. for binary based activities, blobs were built for their platform or all non Sugar Platform dependencies are installed
* if activity was installed not from ASLO or distributor channel, have to manage activity versions on their own
* if they want to help with testing, have to fetch activity from source repositories or from not regular places like people.sugarlabs.org
With Zero Sugar, users:
* know, that every activity is identified by url like http://go.sugarlsbs.org/My_Activity
* can launch it from any (supported) environment just by {{Code|sugar-launch http://go.sugarlsbs.org/My_Activity}} command or from UI
* activity url could be picked up from everywhere, it could be emailed, passed via jabber message, posted on wiki
* user can help with testing activity just by setting policy (globally or for particular activity) and following regular procedures to launch it