Changes

=== obs.sugarlabs.org ===

=== obs.sugarlabs.org ===

The cornerstone component that's intended to be a place to consolidate all the efforts of Sugar doers regarding sharing the code:

The cornerstone component that's intended to be a place to consolidate all the efforts of Sugar doers regarding the sharing of code:

* hosting released sources (so, there is no need in requesting a shell account to upload files to http://download.sugarlabs.org),

* hosting released sources (so, there is no need in requesting a shell account to upload files to http://download.sugarlabs.org),

In the doers' environment, the Activity Library will be a catalog of sweets. In other words, activities.sugarlabs.org might be treated as a front-end for Sugar development process (where obs.sugarlabs.org is a back-end) and an analog of the current Developer Hub on Activity Library.

In the doers' environment, the Activity Library will be a catalog of sweets. In other words, activities.sugarlabs.org might be treated as a front-end for Sugar development process (where obs.sugarlabs.org is a back-end) and an analog of the current Developer Hub on Activity Library.

From usage point of view, only Zero Install interface URL is needed to obtain a new Activity Library entity; the rest will be done by Sweets under the hood.

From a usage point of view, only the Zero Install interface URL is needed to obtain a new Activity Library entity; the rest will be done by Sweets under the hood.

=== packages.sugarlabs.org ===

=== packages.sugarlabs.org ===

It is an [https://build.opensuse.org/ original] Web interface to Open Build Service. It seems to be an overkill for regular Sugar doers' workflow (since OBS is primarily designed to support native packages workflow) when Activity Library's Developers Hub can be used as a more appropriate OBS client. But packages.sugarlabs.org will be useful when people need full OBS control for creating native packages (original ones or basing on existed sweets).

It is an [https://build.opensuse.org/ original] Web interface to Open Build Service. It seems to be an overkill for regular Sugar doers' workflow (since OBS is primarily designed to support native packages workflow) when Activity Library's Developers Hub can be used as a more appropriate OBS client. But packages.sugarlabs.org will be useful when people need full OBS control for creating native packages (original ones or those based on existing sweets).

All packages on packages.sugarlabs.org split into several types:

All packages on packages.sugarlabs.org split into several types:

* aliases that map native packages names of several GNU/Linux distributions into one OBS level name,

* aliases that map native packages names of several GNU/Linux distributions into one OBS level name,

* sweets built only for Zero Install usage,

* sweets built only for Zero Install usage,

* native packages built basing on sweets.

* native packages built based on sweets.

=== sweets.sugarlabs.org ===

=== sweets.sugarlabs.org ===

=== download.sugarlabs.org ===

=== download.sugarlabs.org ===

All files, sources and binaries, that are hosted or produced on obs.sugarlabs.org, will be finally copied to download.sugarlabs.org. The reason is to reuse existed mirroring infrastructure.

All files, sources and binaries, that are hosted or produced on obs.sugarlabs.org, will be finally copied to download.sugarlabs.org. The reason is to reuse the existing mirroring infrastructure.