Activity Team/Obsolete/Zero Sugar Use Cases - Revision history

Alsroot at 18:49, 25 November 2010

2010-11-25T18:49:15Z

← Older revision		Revision as of 14:49, 25 November 2010
Line 3:		Line 3:
	<noinclude>		<noinclude>
	{{TOCright}}		{{TOCright}}
	~~[[Category:Zero Sugar]]~~
	</noinclude>		</noinclude>

	~~How [[Activity Team/Zero Sugar\|Zero Sugar]] could be useful with examples.~~

	== Natively packaged or direct from developer activities? ==		== Natively packaged or direct from developer activities? ==

Alsroot at 18:03, 25 November 2010

2010-11-25T18:03:12Z

← Older revision		Revision as of 14:03, 25 November 2010
Line 1:		Line 1:
			{{Obsolete \| It was only draft content}}

	<noinclude>		<noinclude>
	{{TOCright}}		{{TOCright}}

Alsroot: moved Activity Team/Zero Sugar/Use Cases to Activity Team/Obsolete/Zero Sugar Use Cases

2010-11-25T18:02:06Z

moved Activity Team/Zero Sugar/Use Cases to Activity Team/Obsolete/Zero Sugar Use Cases

← Older revision	Revision as of 14:02, 25 November 2010
(No difference)

FGrose at 20:52, 6 July 2010

2010-07-06T20:52:26Z

← Older revision		Revision as of 16:52, 6 July 2010
Line 16:		Line 16:
	* A user can always pick up a recent version from a developer.		* A user can always pick up a recent version from a developer.

			{{Anchor\|Per_user_Sugar_on_a_stick}}
	== For Sugar on a Stick deployments ==		== For Sugar on a Stick deployments ==

FGrose at 20:45, 6 July 2010

2010-07-06T20:45:22Z

← Older revision		Revision as of 16:45, 6 July 2010
Line 4:		Line 4:
	</noinclude>		</noinclude>

	How [[Activity Team/Zero Sugar\|Zero Sugar]] could be useful on examples.		How [[Activity Team/Zero Sugar\|Zero Sugar]] could be useful with examples.

	== Natively packaged or ~~directly~~ from developer activities? ==		== Natively packaged or direct from developer activities? ==

	Zero Sugar could help with optimizing developer-to-distributor-to-user model. For example:		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		* Developer lets 0sugar create packages for major GNU/Linux distributions 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		* Distributors, either using native OBS features (like links and branches), create their own compilations of activities on OBS, or just attach/copy OBS packages, and so compose repositories with activities for end users.
	* on end users ~~side~~, ~~sugar~~ will understand that there are packaged and direct activity instances		* For end users, Sugar will understand that there are packaged and direct activity instances
	* user(or distributor), by setting policy, ~~can~~ prefer only packaged versions		* The user (or distributor), by setting a policy, may prefer only packaged versions.
	* user ~~all time~~ can pick up recent version from developer		* A user can always pick up a recent version from a developer.

	== ~~Per user~~ Sugar on a ~~stick~~ ==		== For Sugar on a Stick deployments ==

	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 activities use Zero Sugar and activity developers want to support packagers (that is, 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 ==		== Easy activity development workflow ==

	For now, developers:		For now, developers:
	* create .xo bundles		* create .xo bundles,
	* choose server/service to host activity e.g. ASLO or just upload .xo somewhere on wiki		* 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 a non-Python-based activity, build code (for how many platforms/environments?).
	* ~~for~~ activities that contain ~~non~~ Sugar Platform ~~dependencies~~, ~~need~~ to mention it somewhere		* For activities that contain dependencies beyond those in the Sugar Platform, the developer needs to mention it somewhere.
	* ~~within sugar~~, only one ~~stability~~ activity ~~versions exist~~		* Within Sugar, only one 'stable' activity version exists.

	With Zero Sugar, developers:		With Zero Sugar, developers:
	* call {{Code\|0sugar commit}} command to make newly created activity version accessible for users		* call {{Code\|0sugar commit}} command to make a 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)		* The developer could release, not only stable releases, e.g., development, or testing releases, (users will know the release stability status, without reading it somewhere). And by setting a policy, one could prefer only stable versions (or help to test development versions).

	== Easy activity deployment workflow ==		== Easy activity deployment workflow ==

	For now, users:		For now, users:
	* find ~~out~~ .xo bundle somewhere e.g. on ASLO or wiki		* find .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		* after downloading, have to be sure that that the activity will run in their environment, e.g., for binary-based activities, blobs were built for their platform, or all extra-Sugar-Platform dependencies are installed.
	* if activity was installed ~~not~~ from ASLO or distributor channel, have to manage activity versions on their own		* If activity was not installed from ASLO or a distributor channel, the users 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		* If they want to help with testing, they have to fetch the activity from source repositories or from irregular places, like people.sugarlabs.org.

	With Zero Sugar, users:		With Zero Sugar, users:
	* know, that every activity is identified by ~~url~~ like http://go.sugarlsbs.org/My_Activity		* know, that every activity is identified by a 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		* 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		* The activity URL could be picked up from anywhere, it could be emailed, passed via jabber message, posted on a wiki, etc.
	* user can help with testing activity just by setting policy (globally or for particular activity) and following regular procedures to launch it		* The user can help with testing an activity just by setting a policy (globally or for a particular activity) and following regular procedures to launch it.

Alsroot: /* Per user Sugar on a stick */

2010-06-30T06:12:04Z

Per user Sugar on a stick

← Older revision		Revision as of 02:12, 30 June 2010
Line 19:		Line 19:

	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

Alsroot: /* Per user Sugar on a stick */

2010-06-30T05:35:59Z

Per user Sugar on a stick

← Older revision		Revision as of 01:35, 30 June 2010
Line 18:		Line 18:
	== Per user Sugar on a stick ==		== 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~~] just by using OBS [https://build.opensuse.org/ web client~~].		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].

Alsroot: /* Per user Sugar on a stick */

2010-06-30T05:34:33Z

Per user Sugar on a stick

← Older revision		Revision as of 01:34, 30 June 2010
Line 18:		Line 18:
	== Per user Sugar on a stick ==		== Per user Sugar on a stick ==

	Assuming that most of activities use Zero Sugar 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].		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] just by using OBS [https://build.opensuse.org/ web client].

Alsroot: /* Per user Sugar on a stick */

2010-06-30T05:33:44Z

Per user Sugar on a stick

← Older revision		Revision as of 01:33, 30 June 2010
Line 18:		Line 18:
	== Per user Sugar on a stick ==		== 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].		Assuming that most of activities use Zero Sugar 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].

Alsroot: /* Per user Sugar on a stick */

2010-06-30T05:33:06Z

Per user Sugar on a stick

← Older revision		Revision as of 01:33, 30 June 2010
Line 18:		Line 18:
	== Per user Sugar on a stick ==		== 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].		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].