Difference between revisions of "Platform Team/Glossary"
Jump to navigation
Jump to search
m (Pop HD page up to make links shorter) |
|||
| (10 intermediate revisions by 2 users not shown) | |||
| Line 2: | Line 2: | ||
== Glossary == | == Glossary == | ||
</noinclude> | </noinclude> | ||
| + | |||
| + | ===== [[Harmonic Distribution]] ===== | ||
| + | |||
| + | : A systematic approach to supporting the full cycle of discovery, learning, collaboration, and development within the Sugar Learning Platform ecosystem. Harmonic Distribution consists of software, services, and practices that make interacting within the Sugar community more useful and complete. Harmonic Distribution consists of two major parts, the [[#Sweets_Distribution|Sweets Distribution]] and the [[#Sugar_Network|Sugar Network]]. | ||
| + | |||
| + | ===== [[Sweets Distribution]] ===== | ||
| + | |||
| + | : A set of repositories that provide base Sugar software within heterogeneous environments including the most popular GNU/Linux distributions and hardware platforms within the Sugar community. Sweets Distribution provides the easiest way to launch Sugar and start exploring the rest of the Sugar related content using the [[#Sugar_Network|Sugar Network]]. | ||
| + | |||
| + | ===== [[Sugar Network]] ===== | ||
| + | |||
| + | : A system that is designed to share within the Sugar community different kinds of content, e.g., Sugar Activities, artifacts created by Sugar Activities, books, lessons, reviews, comments, questions, etc. It uses [[Wikipedia:Social_network|social network]] mechanisms, to setup relationships between community members intending to improve Sugar Network content. The Sugar Network consists of one global server and an arbitrary number of distributed servers to support people who don't have direct access to the global one, e.g., due to lack of Internet connectivity. | ||
| + | |||
| + | <!-- The former "Sweets" evolved. Some of commented terms will be back after settling down new implementation. | ||
| + | |||
A list of terms to understand the basic concepts of ''Sweets''. | A list of terms to understand the basic concepts of ''Sweets''. | ||
| Line 36: | Line 51: | ||
=====local sweet===== | =====local sweet===== | ||
| − | :It is an important high-level concept in ''Sweets'', which is intended to make the development process of ''sweet'' projects more comfortable. Technically, it is the source software of the ''sweet'' project (i.e., with a ''recipe'' file) placed somewhere in the file system and registered in the local ''Sweets'' instance as a single ''implementation'' for ''interfaces'' it ''implements''. It is always possible to run this ''local sweet'' directly by using the full filesystem path as an ''interface'', but its most useful feature is reuse of the ''local implementation'' in routine ''Sweets'' workflows. For example, if sugar-toolkit sources were cloned to the {{Code|~/src/sugar-toolkit}} directory, then while running a {{Code|sugar}} ''sweet'', it would become possible to reuse local sugar-toolkit sources as a regular ''implementation''. | + | :It is an important high-level concept in ''Sweets'', which is intended to make the development process of ''sweet'' projects more comfortable. Technically, it is the source software of the ''sweet'' project (i.e., with a ''recipe'' file) placed somewhere in the file system and registered in the local ''Sweets'' instance as a single ''implementation'' for ''interfaces'' it ''implements''. It is always possible to run this ''local sweet'' directly by using the full filesystem path as an ''interface'', but its most useful feature is reuse of the ''local implementation'' in routine ''Sweets'' workflows. For example, if the sugar-toolkit sources, which implement the {{Code|sdk/sugar-toolkit}} ''interface'', were cloned to the {{Code|~/src/sugar-toolkit}} directory, then, while running a {{Code|sdk/sugar}} ''sweet'', it would become possible to reuse local sugar-toolkit sources as a regular ''implementation'' of the {{Code|sdk/sugar-toolkit}} dependency of {{Code|sdk/sugar}}. |
=====sweet package===== | =====sweet package===== | ||
:Using the http://packages.sugarlabs.org Web UI, it is possible to create a repository with native packages from released ''sweets''. | :Using the http://packages.sugarlabs.org Web UI, it is possible to create a repository with native packages from released ''sweets''. | ||
| − | + | --> | |
| − | |||
| − | |||
Latest revision as of 01:38, 27 July 2012
Glossary
Harmonic Distribution
- A systematic approach to supporting the full cycle of discovery, learning, collaboration, and development within the Sugar Learning Platform ecosystem. Harmonic Distribution consists of software, services, and practices that make interacting within the Sugar community more useful and complete. Harmonic Distribution consists of two major parts, the Sweets Distribution and the Sugar Network.
Sweets Distribution
- A set of repositories that provide base Sugar software within heterogeneous environments including the most popular GNU/Linux distributions and hardware platforms within the Sugar community. Sweets Distribution provides the easiest way to launch Sugar and start exploring the rest of the Sugar related content using the Sugar Network.
Sugar Network
- A system that is designed to share within the Sugar community different kinds of content, e.g., Sugar Activities, artifacts created by Sugar Activities, books, lessons, reviews, comments, questions, etc. It uses social network mechanisms, to setup relationships between community members intending to improve Sugar Network content. The Sugar Network consists of one global server and an arbitrary number of distributed servers to support people who don't have direct access to the global one, e.g., due to lack of Internet connectivity.