Difference between revisions of "Deployment Platform/Software"

From Sugar Labs
Jump to navigation Jump to search
m
 
(20 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
{{Template:Harmonic Distribution Cycle Linkbar}}
+
{{Template:Deployment Platform Cycle Linkbar}}
  
−
== Base software ==
+
== Software Map ==
  
−
This software components will be provided from native package repositories.
+
{| border="0"
 +
|-
 +
|- valign="top" align="left"
 +
| [[File:Harmonic Distribution Software.png]]
 +
| The whole software within the Harmonic Distribution is structured as:
  
−
Sucrose and Server Kit packages will conform LTS release plan of [[Platform Team/Harmonic Distribution|Harmonic Distribution]] itself.
+
* '''Base software'''<br>Provided from [[#Sweets_Distribution|Sweets Distribution]] in form of native packages. Base software is separated by targeted audience:
  
−
=== Sucrose ===
+
:* '''Using oriented'''<br>For regular usage. This kind of software exists in two dimensions:
  
−
Stable Sucrose [[:Category:Platform Cycle|releases]].
+
:: By purpose:
  
−
=== Doers' Kit ===
+
::* '''Client side'''<br>[[#Desktop|Desktop]] - Desktop Environment for Sugar Learning Platform.
 +
::* '''Server side'''<br>[[#Server_Kit|Server Kit]] - to form school servers.
 +
 
 +
:: By the supporting time:
 +
 
 +
::* '''Short-term support''' (STS)<br>Targeting to individual usage and based on Sucrose six months release cycle.
 +
::* '''Long-term support''' (LTS)<br>Targeting to Sugar deployments that can't switch between Sucrose releases every six months.
 +
 
 +
:* '''Development oriented'''<br>[[#Doers' Kit|Doers' Kit]] - targeting to developers who code within the Sugar Learning Platform.
 +
 
 +
* '''Community software'''<br>The rest of software created on top of the Base one. In contrast to the Base, this kind of software is being provided via [[#Sugar Network|Sugar Network]].
 +
|-
 +
|}
 +
 
 +
== Sweets Distribution ==
 +
 
 +
This is a 3rd party repository with Base Software packages built against all [[Sweets_Distribution/Supported_platforms|supported platforms]]. These packages are being built on Sugar Labs instance of [[Platform_Team/Open_Build_Service|Open Build Service]] and formed in several projects:
 +
 
 +
* [https://packages.sugarlabs.org/project/show?project=SweetsDistribution SweetsDistribution]<br>Contains all [[Sweets_Distribution/Supported_platforms|supported platforms]] as OBS repositories and system packages for upstream projects (not Base software) that are not well packages in supported platforms.
 +
 
 +
* [https://packages.sugarlabs.org/project/show?project=SweetsDistribution%3AFactory SweetsDistribution:Factory]<br>OBS project with development packages that are intended for testing only.
 +
 
 +
* [https://packages.sugarlabs.org/project/subprojects?project=SweetsDistribution SweetsDistribution:<SUCROSE-RELEASE>]<br>Stable STS/LTS releases of Harmonic Distribution.
 +
 
 +
After building, OBS uploads resulting packages to [http://download.sugarlabs.org/packages/ download.sugarlabs.org] site. Follow [[Sweets Distribution]] instructions to setup them for individual usage.
 +
 
 +
=== Desktop ===
 +
 
 +
Components:
 +
 
 +
* Stable Sucrose [[:Category:Platform Cycle|releases]] [http://git.sugarlabs.org/shell patched] to include Harmonic Distribution specific features.
 +
* [[Platform_Team/sugar-stats|sugar-stats]] library to gather Sugar [[Platform_Team/Usage_Statistics|usage statistics]].
  
−
Sugar Doers Kit (SDK) is a set of tools and libraries to help people code in Sugar.
+
Sources:
  
−
* [[Platform_Team/Sweets|Sweets]], Zero Install based Package Management System for Sugar.
+
* [http://git.sugarlabs.org/desktop Desktop] project.
−
* [[Platform_Team/Sugar_Lint|sugar-lint]], utility to lint various source files.
 
−
* [[Platform_Team/gatch|gatch]], support long or ever standing, all time being on top, downstream patchset for the base branch in a Git repository.
 
−
* [[Platform_Team/Guide/Sweets_Usage#Sugar_via_Sweets|Sugar via Sweets]], several Sucrose versions via Sweets.
 
  
 
=== Server Kit ===
 
=== Server Kit ===
 +
 +
Components:
  
 
* [[Platform_Team/Server_Kit/sugar-server|sugar-server]]
 
* [[Platform_Team/Server_Kit/sugar-server|sugar-server]]
Line 28: Line 62:
 
* [[Platform_Team/Server_Kit/Prosody|prosody-sugar]]
 
* [[Platform_Team/Server_Kit/Prosody|prosody-sugar]]
 
* [[Platform_Team/Server_Kit/sugar-unit|sugar-unit]]
 
* [[Platform_Team/Server_Kit/sugar-unit|sugar-unit]]
 +
 +
Sources:
 +
 +
* [http://git.sugarlabs.org/server Server] project.
  
 
For detailed information, see [[Platform_Team/Server_Kit|Server Kit]]'s home page.
 
For detailed information, see [[Platform_Team/Server_Kit|Server Kit]]'s home page.
  
−
== Community software ==
+
=== Doers' Kit ===
 +
 
 +
Sugar Doers Kit (SDK) is a set of tools and libraries to help people code in Sugar.
 +
 
 +
Components:
 +
 
 +
* [[Platform_Team/Sweets|Sweets]], Zero Install based Package Management System for Sugar.
 +
* [[Platform_Team/Sugar_Lint|sugar-lint]], utility to lint various source files.
 +
* [[Platform_Team/gatch|gatch]], support long or ever standing, all time being on top, downstream patchset for the base branch in a Git repository.
 +
* [[Platform_Team/Guide/Sweets_Usage#Sugar_via_Sweets|Sugar via Sweets]], several Sucrose versions via Sweets.
 +
 
 +
Sources:
 +
 
 +
* [http://git.sugarlabs.org/sdk SDK] project.
 +
 
 +
==== Glucose development ====
 +
 
 +
== Sugar Network ==
 +
 
 +
Components:
 +
 
 +
* [[Platform_Team/Sugar_Network/Implementation|sugar-network]].
 +
* [[Platform_Team/Sugar_Network/Web_UI|Web UI]].
 +
* [[Sugar_Network/Contributor_Hub|Contributor Hub]].
 +
 
 +
Sources:
 +
 
 +
* [http://git.sugarlabs.org/network Network] project.
  
−
Out of base software, the rest software will be provided via [[Sugar Network]] and will be treated, in local environment, by [[Platform_Team/Sweets|Sweets]] library.
+
=== Distribution via Sugar Network ===
  
 
The high-level overview is looks like:
 
The high-level overview is looks like:

Latest revision as of 22:16, 26 November 2012

Deployment Platform version cycle: | 1.0 | 1.1 | 2.0 |

Software Map

Harmonic Distribution Software.png The whole software within the Harmonic Distribution is structured as:
  • Base software
    Provided from Sweets Distribution in form of native packages. Base software is separated by targeted audience:
  • Using oriented
    For regular usage. This kind of software exists in two dimensions:
By purpose:
  • Client side
    Desktop - Desktop Environment for Sugar Learning Platform.
  • Server side
    Server Kit - to form school servers.
By the supporting time:
  • Short-term support (STS)
    Targeting to individual usage and based on Sucrose six months release cycle.
  • Long-term support (LTS)
    Targeting to Sugar deployments that can't switch between Sucrose releases every six months.
  • Development oriented
    Doers' Kit - targeting to developers who code within the Sugar Learning Platform.
  • Community software
    The rest of software created on top of the Base one. In contrast to the Base, this kind of software is being provided via Sugar Network.

Sweets Distribution

This is a 3rd party repository with Base Software packages built against all supported platforms. These packages are being built on Sugar Labs instance of Open Build Service and formed in several projects:

After building, OBS uploads resulting packages to download.sugarlabs.org site. Follow Sweets Distribution instructions to setup them for individual usage.

Desktop

Components:

Sources:

Server Kit

Components:

Sources:

For detailed information, see Server Kit's home page.

Doers' Kit

Sugar Doers Kit (SDK) is a set of tools and libraries to help people code in Sugar.

Components:

  • Sweets, Zero Install based Package Management System for Sugar.
  • sugar-lint, utility to lint various source files.
  • gatch, support long or ever standing, all time being on top, downstream patchset for the base branch in a Git repository.
  • Sugar via Sweets, several Sucrose versions via Sweets.

Sources:

Glucose development

Sugar Network

Components:

Sources:

Distribution via Sugar Network

The high-level overview is looks like:

  • software creators
    upload source bundles to the Sugar Network; only sources, even if it is binary based activities;
  • Sugar Network
    if uploaded software needs building, it will send it to OBS;
  • on users side
    Sweets library will:
    • read Sugar Network to find out information about implementations of software that user requested to launch;
    • according to the local environment, it will download proper implementation;
    • if there is no proper binary implementation, it will download sources and will build them in local environment.
Retrieved from "https://wiki.sugarlabs.org/index.php?title=Deployment_Platform/Software&oldid=84350"