Platform Team/Package Management System/1.0/Notes - Revision history

Alsroot: moved Platform Team/Sweets/1.0/Notes to Platform Team/Package Management System/1.0/Notes: "Sweets" has evolved to hidden SN parts and public "Sweets Distributoin"

2012-04-27T10:11:17Z

moved Platform Team/Sweets/1.0/Notes to Platform Team/Package Management System/1.0/Notes: "Sweets" has evolved to hidden SN parts and public "Sweets Distributoin"

← Older revision	Revision as of 06:11, 27 April 2012
(No difference)

Alsroot: /* Retrospection */

2011-10-02T18:39:24Z

Retrospection

← Older revision		Revision as of 14:39, 2 October 2011
Line 3:		Line 3:
	Two years ago, Michael Stone [http://thread.gmane.org/gmane.comp.file-systems.zero-install.devel/2728 rolled] the first try to get the folks at Sugar Labs excited about Zero Install software. Several people from both communities showed their interest, e.g., Bernie Innocenti, Thomas Leonard, Rene Lopez, and Anders F Björklund. As a result, a meeting occurred on the #sugar-meeting IRC channel. That meeting was organized by Michael Stone to exchange knowledge and to learn whether Zero Install might be a good fit for use in Sugar activity installation. Thomas Leonard wrote a [http://thread.gmane.org/gmane.comp.file-systems.zero-install.devel/2776 summary] and Michael Stone [http://thread.gmane.org/gmane.comp.file-systems.zero-install.devel/2776/focus=18807 forwarded] it to the sugar-devel mailing list.		Two years ago, Michael Stone [http://thread.gmane.org/gmane.comp.file-systems.zero-install.devel/2728 rolled] the first try to get the folks at Sugar Labs excited about Zero Install software. Several people from both communities showed their interest, e.g., Bernie Innocenti, Thomas Leonard, Rene Lopez, and Anders F Björklund. As a result, a meeting occurred on the #sugar-meeting IRC channel. That meeting was organized by Michael Stone to exchange knowledge and to learn whether Zero Install might be a good fit for use in Sugar activity installation. Thomas Leonard wrote a [http://thread.gmane.org/gmane.comp.file-systems.zero-install.devel/2776 summary] and Michael Stone [http://thread.gmane.org/gmane.comp.file-systems.zero-install.devel/2776/focus=18807 forwarded] it to the sugar-devel mailing list.

	The idea of using Zero Install in the Sugar ecosystem passed several mutations and, eventually, it seems that the core ideas have settled down and are ready to be presented widely in the community. [http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg23055.html ~~Announcement~~, 02 October 2011]		The idea of using Zero Install in the Sugar ecosystem passed several mutations and, eventually, it seems that the core ideas have settled down and are ready to be presented widely in the community.

			Announcement:
			* [http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg23055.html sugar-devel, 02 October 2011].
			* [http://thread.gmane.org/gmane.comp.file-systems.zero-install.devel/4627 zero-install-devel, 02 October 2011].

	== The pillars ==		== The pillars ==

FGrose at 17:43, 2 October 2011

2011-10-02T17:43:49Z

← Older revision		Revision as of 13:43, 2 October 2011
Line 3:		Line 3:
	Two years ago, Michael Stone [http://thread.gmane.org/gmane.comp.file-systems.zero-install.devel/2728 rolled] the first try to get the folks at Sugar Labs excited about Zero Install software. Several people from both communities showed their interest, e.g., Bernie Innocenti, Thomas Leonard, Rene Lopez, and Anders F Björklund. As a result, a meeting occurred on the #sugar-meeting IRC channel. That meeting was organized by Michael Stone to exchange knowledge and to learn whether Zero Install might be a good fit for use in Sugar activity installation. Thomas Leonard wrote a [http://thread.gmane.org/gmane.comp.file-systems.zero-install.devel/2776 summary] and Michael Stone [http://thread.gmane.org/gmane.comp.file-systems.zero-install.devel/2776/focus=18807 forwarded] it to the sugar-devel mailing list.		Two years ago, Michael Stone [http://thread.gmane.org/gmane.comp.file-systems.zero-install.devel/2728 rolled] the first try to get the folks at Sugar Labs excited about Zero Install software. Several people from both communities showed their interest, e.g., Bernie Innocenti, Thomas Leonard, Rene Lopez, and Anders F Björklund. As a result, a meeting occurred on the #sugar-meeting IRC channel. That meeting was organized by Michael Stone to exchange knowledge and to learn whether Zero Install might be a good fit for use in Sugar activity installation. Thomas Leonard wrote a [http://thread.gmane.org/gmane.comp.file-systems.zero-install.devel/2776 summary] and Michael Stone [http://thread.gmane.org/gmane.comp.file-systems.zero-install.devel/2776/focus=18807 forwarded] it to the sugar-devel mailing list.

	The idea of using Zero Install in the Sugar ecosystem passed several mutations and, eventually, it seems that the core ideas have settled down and are ready to be presented widely in the community.		The idea of using Zero Install in the Sugar ecosystem passed several mutations and, eventually, it seems that the core ideas have settled down and are ready to be presented widely in the community. [http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg23055.html Announcement, 02 October 2011]

	== The pillars ==		== The pillars ==

Alsroot: /* What is Sweets */

2011-10-02T16:34:33Z

What is Sweets

← Older revision		Revision as of 12:34, 2 October 2011
Line 41:		Line 41:
	At the same time, existing distribution methods are reused in Sweets:		At the same time, existing distribution methods are reused in Sweets:

	# [[Development_Team/Almanac/Activity_Bundles\|''.xo bundles'']] is a subset of the Sweets workflow from usage point of view		# [[Development_Team/Almanac/Activity_Bundles\|''.xo bundles'']] is a subset of the Sweets workflow, from usage point of view
	#* It is possible to bundle an entire directory as a sweet project to use it as a regular .xo file.		#* It is possible to bundle an entire directory as a sweet project to use it as a regular .xo file.
	# ''native packages''		# ''native packages''

Alsroot: /* What is Sweets */

2011-10-02T16:31:37Z

What is Sweets

← Older revision		Revision as of 12:31, 2 October 2011
Line 31:		Line 31:
	The purpose is to create a new distribution method instead of reusing:		The purpose is to create a new distribution method instead of reusing:

	# [[Development_Team/Almanac/Activity_Bundles\|.xo bundles]]		# [[Development_Team/Almanac/Activity_Bundles\|''.xo bundles'']]
	#* Work smoothly only for pure python activities, and only if all (and the same) dependencies are installed on all systems. They stop working smoothly if activities use non-standard dependencies or contain binaries.		#* Work smoothly only for pure python activities, and only if all (and the same) dependencies are installed on all systems. They stop working smoothly if activities use non-standard dependencies or contain binaries.
	#* But, are not effective in supporting the use of multiple versions of software, e.g., the results of experiments (the work) of different doers, simultaneously. Users must manually handle the variety of activity versions, e.g., sort out all the local bundles or directories in {{Code\|~/Activities}}.		#* But, are not effective in supporting the use of multiple versions of software, e.g., the results of experiments (the work) of different doers, simultaneously. Users must manually handle the variety of activity versions, e.g., sort out all the local bundles or directories in {{Code\|~/Activities}}.
Line 41:		Line 41:
	At the same time, existing distribution methods are reused in Sweets:		At the same time, existing distribution methods are reused in Sweets:

	# [[Development_Team/Almanac/Activity_Bundles\|.xo bundles]] is a subset of the Sweets workflow from usage point of view		# [[Development_Team/Almanac/Activity_Bundles\|''.xo bundles'']] is a subset of the Sweets workflow from usage point of view
	#* It is possible to bundle an entire directory as a sweet project to use it as a regular .xo file.		#* It is possible to bundle an entire directory as a sweet project to use it as a regular .xo file.
	# ''native packages''		# ''native packages''

Alsroot: /* What is Sweets */

2011-10-02T16:30:47Z

What is Sweets

← Older revision		Revision as of 12:30, 2 October 2011
Line 21:		Line 21:
	== What is Sweets ==		== What is Sweets ==

	So, Sweets is a [[wikipedia:Package_management_system \|Package Management System]] based on [http://0install.net/ Zero Install], a decentralized, cross-distribution, software installation system. It is intended to distribute various software projects created in the Sugar ecosystem, such as libraries, sugar itself, and sugar activities.		So, Sweets is a [[wikipedia:Package_management_system \|Package Management System]] entirely based on [http://0install.net/ Zero Install], a decentralized, cross-distribution, software installation system. It might be treated as a tools and infrastructure wrapper around Zero Install. Sweets is intended to distribute various software projects created in the Sugar ecosystem, such as libraries, sugar itself, and sugar activities.

	This new distribution method is initiated assuming that:		This new distribution method is initiated assuming that:
Line 31:		Line 31:
	The purpose is to create a new distribution method instead of reusing:		The purpose is to create a new distribution method instead of reusing:

	# ''.xo bundles''		# [[Development_Team/Almanac/Activity_Bundles\|.xo bundles]]
	#* Work smoothly only for pure python activities, and only if all (and the same) dependencies are installed on all systems. They stop working smoothly if activities use non-standard dependencies or contain binaries.		#* Work smoothly only for pure python activities, and only if all (and the same) dependencies are installed on all systems. They stop working smoothly if activities use non-standard dependencies or contain binaries.
	#* But, are not effective in supporting the use of multiple versions of software, e.g., the results of experiments (the work) of different doers, simultaneously. Users must manually handle the variety of activity versions, e.g., sort out all the local bundles or directories in {{Code\|~/Activities}}.		#* But, are not effective in supporting the use of multiple versions of software, e.g., the results of experiments (the work) of different doers, simultaneously. Users must manually handle the variety of activity versions, e.g., sort out all the local bundles or directories in {{Code\|~/Activities}}.
Line 41:		Line 41:
	At the same time, existing distribution methods are reused in Sweets:		At the same time, existing distribution methods are reused in Sweets:

	# ''.xo bundles'' is a subset of the Sweets workflow		# [[Development_Team/Almanac/Activity_Bundles\|.xo bundles]] is a subset of the Sweets workflow from usage point of view
	#* It is possible to bundle an entire directory as a sweet project to use it as a regular .xo file.		#* It is possible to bundle an entire directory as a sweet project to use it as a regular .xo file.
	# ''native packages''		# ''native packages''

Alsroot: /* Learning by doing */

2011-10-02T16:17:11Z

Learning by doing

← Older revision		Revision as of 12:17, 2 October 2011
Line 9:		Line 9:
	=== Learning by doing ===		=== Learning by doing ===

	The preeminent core idea behind Sugar is learning by doing. Thus, it is critical to Sugar to have the tools that support the doing metaphor well, doing not only within regular activities and project teams, but also by individuals who tweak the software in the process of learning. And not the least of options is sharing the results of doer/learner experiments. Sweets is intended to make these aspects less annoying ~~using~~ the [http://0install.net/why.html Zero Install] system.		The preeminent core idea behind Sugar is learning by doing. Thus, it is critical to Sugar to have the tools that support the doing metaphor well, doing not only within regular activities and project teams, but also by individuals who tweak the software in the process of learning. And not the least of options is sharing the results of doer/learner experiments. Sweets is intended to make these aspects less annoying being based on the [http://0install.net/why.html Zero Install] system.

	=== To not reinvent the wheels ===		=== To not reinvent the wheels ===

Alsroot: /* Learning by doing */

2011-10-02T15:30:47Z

Learning by doing

← Older revision		Revision as of 11:30, 2 October 2011
Line 9:		Line 9:
	=== Learning by doing ===		=== Learning by doing ===

	The preeminent core idea behind Sugar is learning by doing. Thus, it is critical to Sugar to have the tools that support the doing metaphor well, doing not only within regular activities and project teams, but also by individuals who tweak the software in the process of learning. And not the least of options is sharing the results of doer/learner experiments. Sweets is intended to make these aspects less annoying using the [http://0install.net/ Zero Install] system.		The preeminent core idea behind Sugar is learning by doing. Thus, it is critical to Sugar to have the tools that support the doing metaphor well, doing not only within regular activities and project teams, but also by individuals who tweak the software in the process of learning. And not the least of options is sharing the results of doer/learner experiments. Sweets is intended to make these aspects less annoying using the [http://0install.net/why.html Zero Install] system.

	=== To not reinvent the wheels ===		=== To not reinvent the wheels ===

FGrose at 15:18, 2 October 2011

2011-10-02T15:18:17Z

← Older revision		Revision as of 11:18, 2 October 2011
Line 69:		Line 69:
	== Try the release ==		== Try the release ==

	There are Sugar Shell sweets as an example how to use Sweets in practice. See [[Platform_Team/Guide/Sweets_Usage#Sugar_via_Sweets\|Sweets Usage]] guide for instructions.		There are Sugar Shell sweets as an example of how to use Sweets in practice. See [[Platform_Team/Guide/Sweets_Usage#Sugar_via_Sweets\|Sweets Usage]] guide for instructions.

	== Further reading ==		== Further reading ==

Alsroot: /* Feedback */

2011-10-02T07:57:14Z

Feedback

← Older revision		Revision as of 03:57, 2 October 2011
Line 88:		Line 88:
	== Feedback ==		== Feedback ==

	{{:Platform_Team/~~Guide/Sweets_Usage~~/Feedback}}		{{:Platform_Team/Sweets/Feedback}}

	== Credits ==		== Credits ==