Changes

== Retrospection ==

== Retrospection ==

It is mostly 2 years passed after the time when a meeting, between several Zero Install and Sugar people, happened on #sugar-meeting IRC channel. The meeting was organized by Michael Stone (if I'm wrong, he will correct me) 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 sugar-devel mailing list.

Nearly 2 years have passed since the time of a meeting, between several Zero Install and Sugar people, occurred on the #sugar-meeting IRC channel. The meeting was organized by Michael Stone (if I'm wrong, he will correct me) 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 sugar-devel mailing list.

The idea of using Zero Install in Sugar ecosystem passed several mutations and, eventually, it seems to be that core ideas were settled down and 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 to be that the core ideas have settled down and are ready to be presented widely in the community.

== The pillars ==

== The pillars ==

=== For learning by doing ===

=== Learning by doing ===

The one of the core ideas behind Sugar is learning by doing. It is critical to have the tool that will well support doing metaphor, doing not only within regular project teams but also by individuals who tweak the software in the process of learning. But not the least option is sharing results of experiments. Sweets is intended to make both aspects less annoying using the [http://0install.net/ Zero Install] system.

The preeminent core idea behind Sugar is learning by doing. It is critical to Sugar to have the tools that support the doing metaphor well, doing not only within regular 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.

=== To not reinvent the wheels ===

=== To not reinvent the wheels ===

It will be useful to let people in Sugar community to be concentrated only on software they are developing and reuse existing efforts of GNU/Linux distributions as underliing dependencies for developing software. The [http://www.packagekit.org/ PackageKit] project gives such possibility.

It will be useful to let people in the Sugar community to concentrate only on software they are developing, and to reuse existing efforts of GNU/Linux distributions as underlying dependencies for developing software. The [http://www.packagekit.org/ PackageKit] project provides this possibility.

=== Infrastructure does matter ===

=== Infrastructure does matter ===

The core difference of the final approach with previous evolutions is the idea that successful model should cover the full lifetime cycle of software, from developing by creators to using by the community. Another project, the [http://openbuildservice.org/ Open Build System], was chosen for that.

The core difference of the final Sweets approach with previous evolutions is the idea that a successful model should cover the full life cycle of software, from developing by creators to using by the community. Another project, the [http://openbuildservice.org/ Open Build System], was chosen for that.

== What is Sweets ==

== What is Sweets ==

So, Sweets is a [http://en.wikipedia.org/wiki/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]] 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.

This new distribution method is initiated assuming that:

This new distribution method is initiated assuming that:

* The method to share software projects should to be as convenient as possible.

* The method to share software projects should be as convenient as possible.

* It is important to stimulate users into becoming doers, to modify existing activities, and to share the results of their experiments with other people, i.e., a distribution method should handle different variants of the same project.

* It is important to stimulate users into becoming doers, to modify existing activities, and to share the results of their experiments with other people, i.e., a distribution method should handle different variants of the same project.

* This distribution method is not intended to be the only one, but is targeted more towards direct distribution—from software creators to software users.

* This distribution method is not intended to be the only one, but is targeted more towards direct distribution—from software creators to software users.

== In this release ==

== In this release ==

This is the initial release and have some critical, for Sugar, points missed, e.g., GUI to launch activities using Sweets. The major point for this release is exposing the fact that basic ideas and core implementation is mature enough to make Sweets useful in some [[#Try_the_release|workflows]] and to involve more people to Sweets and Sweets related projects developing, e.g., a la Ubuntu AppCenter for Sugar.

This is the initial release and has missed some critical points for Sugar, e.g., a GUI to launch activities using Sweets. The major purpose for this release is exposing the fact that basic ideas and core implementations are mature enough to make Sweets useful in some [[#Try_the_release|workflows]] and to involve more people in Sweets and Sweets related project development, e.g., a la Ubuntu AppCenter for Sugar.

== Getting the release ==

== Getting the release ==

The details instructions can be found in [[Platform_Team/Guide/Sweets_Usage#Installation|Sweets Usage]] guide.

The details instructions can be found in [[Platform_Team/Guide/Sweets_Usage#Installation|Sweets Usage]] guide.

First, install PackageKit package with a packages for integration with Desktop Environment you are using, e.g., {{Code|gnome-packagekit}} for Gnome. It is important to install exactly integration package to have an authentication agent that depends on particular Desktop Environment. After installation, it might require to relogin from the Desktop Environment session.

First, install the PackageKit package with the packages for integration with the Desktop Environment you are using, e.g., {{Code|gnome-packagekit}} for Gnome. It is important to install exactly integration package to have an authentication agent that depends on the particular Desktop Environment. After installation, it might be required to relogin from the Desktop Environment session.

Download and run Sweets installer:

Download and run Sweets installer:

  sh installer.sh

  sh installer.sh

Relogin from the Desktop Environment session to take into account the new PATH environment variable value that installer will set.

Relogin from the Desktop Environment session to take into account the new PATH environment variable value that the installer will set.

== Try the release ==

== Try the release ==

To try Sweets on practice, run several Sugar versions. On the Sweets level, there are no any restrictions to use Sweets on any GNU/Linux distribution. The successful usage depends only on the PackageKit presence and the quality of sweet packages (sweets). For now, sugar sweets are well aware about Fedora, Debian/Ubuntu and Gentoo package names and not so well about openSUSE and Mandriva. Sugar sweets launch were tested on some recent Fedora and Ubuntu releases. The quality of other GNU/Linux distributions support depends only on how often Sweets will be used on these distributions.

To try Sweets in practice, run several Sugar versions. On the Sweets level, there are not any restrictions to using Sweets on any GNU/Linux distribution. Successful usage depends only on the presence of PackageKit and the quality of sweet packages (sweets). For now, sugar sweets are well aware of Fedora, Debian/Ubuntu and Gentoo package names and not so well aware of openSUSE and Mandriva. Sugar sweets launchs were tested on some recent Fedora and Ubuntu releases. The quality of other GNU/Linux distribution support depends only on how often Sweets is used on these distributions and the reporting of problems by the community.

Note, Sugar Shell does not start authentication agent and preparing sugar start can be processed only in Desktop Environment, e.g., Gnome. To launch recent stable Sugar version in emulator mode, type in a terminal:

Note, Sugar Shell does not start the authentication agent, and preparing sugar start can be processed only in a Desktop Environment, e.g., Gnome. To launch a recent stable Sugar version in emulator mode, type in a terminal:

  sweets sdk/sugar:emulator

  sweets sdk/sugar:emulator

To run particular version:

To run a particular version:

  sweets sdk/sugar:emulator = 0.88

  sweets sdk/sugar:emulator = 0.88

* provide [[Activity Library]] activities via Zero Install,

* provide [[Activity Library]] activities via Zero Install,

* support search among remote sweets on a client side,

* support search among remote sweets on the client side,

* Initial GUI for browsing local and remote sweets.

* provide an initial GUI for browsing local and remote sweets.

== Credits ==

== Credits ==

* The [[Infrastructure Team]] for their help with setting up services required for Sweets infra.

* The [[Infrastructure Team]] for their help with setting up services required for Sweets infra.

* The [[Wiki Team]] for continuous polishing [[Platform_Team/Sweets|Sweets]] wiki pages.

* The [[Wiki Team]] for continuous polishing [[Platform_Team/Sweets|Sweets]] wiki pages.

* [http://activitycentral.com/ Activity Central] for supporting during the work on 1.0 release final phase.

* [http://activitycentral.com/ Activity Central] for supporting the work on the 1.0 release final phase.