Difference between revisions of "Deployment Platform/Software"

From Sugar Labs
Jump to navigation Jump to search
Line 15: Line 15:
 
:: By purpose:
 
:: By purpose:
  
−
::* '''Client side'''<br>[[#Shell|Shell]] - Desktop Environment for Sugar Learning Platform.
+
::* '''Client side'''<br>[[#Desktop|Desktop]] - Desktop Environment for Sugar Learning Platform.
 
::* '''Server side'''<br>[[#Server_Kit|Server Kit]] - to form school servers.
 
::* '''Server side'''<br>[[#Server_Kit|Server Kit]] - to form school servers.
  
Line 29: Line 29:
 
|}
 
|}
  
−
== Shell ==
+
== Desktop ==
  
 
Components:
 
Components:
Line 38: Line 38:
 
Sources:
 
Sources:
  
−
* Gitorious [http://git.sugarlabs.org/shell Shell] project.
+
* [http://git.sugarlabs.org/dekstop Desktop] project.
  
 
== Doers' Kit ==
 
== Doers' Kit ==
  
 
Sugar Doers Kit (SDK) is a set of tools and libraries to help people code in Sugar.
 
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/Sweets|Sweets]], Zero Install based Package Management System for Sugar.
Line 48: Line 50:
 
* [[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/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.
 
* [[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 ===
 
=== Glucose development ===
  
 
== Server Kit ==
 
== Server Kit ==
 +
 +
Components:
  
 
* [[Platform_Team/Server_Kit/sugar-server|sugar-server]]
 
* [[Platform_Team/Server_Kit/sugar-server|sugar-server]]
Line 59: Line 67:
 
* [[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.
  
 
== Sugar Network ==
 
== Sugar Network ==
 +
 +
Components:
  
 
* [[Platform_Team/Active_Document|active-document]] library.
 
* [[Platform_Team/Active_Document|active-document]] library.
 
* [[Platform_Team/RESTful_Document|restful-document]] library.
 
* [[Platform_Team/RESTful_Document|restful-document]] library.
 
* [[Platform_Team/Sugar_Network/Client|sugar-network]] client library.
 
* [[Platform_Team/Sugar_Network/Client|sugar-network]] client library.
 +
* [[Platform_Team/Sugar_Network/Client|sugar-network]] client library.
 +
* [[Platform_Team/Sugar_Network/Browser|mejorar-sistema]] client application.
 
* [[Platform_Team/Sugar_Network/Server|sugar-network-server]] server.
 
* [[Platform_Team/Sugar_Network/Server|sugar-network-server]] server.
  
 +
Sources:
 +
 +
* [http://git.sugarlabs.org/network Network] project.
  
 
=== Distribution via Sugar Network ===
 
=== Distribution via Sugar Network ===

Revision as of 01:27, 25 March 2012

Harmonic Distribution version cycle: | 1.0 | Factory |

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 Base, this kind of software is being provided via Sugar Network.

Desktop

Components:

Sources:

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

Server Kit

Components:

Sources:

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

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=76791"