Platform Team/Glossary - Revision history

Alsroot: Pop HD page up to make links shorter

2012-07-27T06:38:25Z

Pop HD page up to make links shorter

← Older revision		Revision as of 02:38, 27 July 2012
Line 3:		Line 3:
	</noinclude>		</noinclude>

	===== [[~~Platform_Team/Harmonic_Distribution\|~~Harmonic Distribution]] =====		===== [[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]].		: 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]].

FGrose at 15:56, 3 May 2012

2012-05-03T15:56:03Z

← Older revision		Revision as of 11:56, 3 May 2012
Line 5:		Line 5:
	===== [[Platform_Team/Harmonic_Distribution\|Harmonic Distribution]] =====		===== [[Platform_Team/Harmonic_Distribution\|Harmonic Distribution]] =====

	: ~~The~~ systematic approach to ~~support~~ full cycle of Sugar Learning Platform ecosystem. Harmonic Distribution ~~consist~~ of software, services and practices that make interacting within the Sugar community more useful. Harmonic Distribution consists of two major parts, [[#Sweets_Distribution\|Sweets Distribution]] and [[#Sugar_Network\|Sugar Network]].		: 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]] =====		===== [[Sweets Distribution]] =====

	: ~~Provides~~ base software in heterogeneous ~~environment, i.e.,~~ most popular~~, within the Sugar community,~~ GNU/Linux distributions and hardware platforms. Sweets Distribution provides the ~~easy~~ way to launch ~~initial software~~ and start exploring the rest of the Sugar related content using the [[#Sugar_Network\|Sugar Network]].		: 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]] =====		===== [[Sugar Network]] =====

	: ~~The~~ system that is ~~intended~~ to share different kinds of content ~~within the Sugar community~~, e.g., Sugar Activities, artifacts created by Sugar Activities, books, etc. ~~Using~~ [[Wikipedia:Social_network\|social network]] mechanisms, setup ~~the relations~~ between community members to improve Sugar Network content. Sugar Network consists of one global server and arbitrary number of distributed servers (to support people who don't have direct access, e.g., due to lack on Internet connectivity~~, to the global one)~~.		: 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.		<!-- The former "Sweets" evolved. Some of commented terms will be back after settling down new implementation.

Alsroot: /* Harmonic Distribution */

2012-04-28T20:28:01Z

Harmonic Distribution

← Older revision		Revision as of 16:28, 28 April 2012
Line 5:		Line 5:
	===== [[Platform_Team/Harmonic_Distribution\|Harmonic Distribution]] =====		===== [[Platform_Team/Harmonic_Distribution\|Harmonic Distribution]] =====

	: The systematic approach to support full cycle of Sugar Learning Platform ecosystem. Harmonic Distribution consist of software, services and practices that make interacting within the Sugar community more useful. Harmonic Distribution consists of two major parts, [[#~~Harmonic_Distribution~~\|~~Harmonic~~ Distribution]] and [[#Sugar_Network\|Sugar Network]].		: The systematic approach to support full cycle of Sugar Learning Platform ecosystem. Harmonic Distribution consist of software, services and practices that make interacting within the Sugar community more useful. Harmonic Distribution consists of two major parts, [[#Sweets_Distribution\|Sweets Distribution]] and [[#Sugar_Network\|Sugar Network]].

	===== [[Sweets Distribution]] =====		===== [[Sweets Distribution]] =====

Alsroot at 20:27, 28 April 2012

2012-04-28T20:27:03Z

← Older revision		Revision as of 16:27, 28 April 2012
Line 5:		Line 5:
	===== [[Platform_Team/Harmonic_Distribution\|Harmonic Distribution]] =====		===== [[Platform_Team/Harmonic_Distribution\|Harmonic Distribution]] =====

	The systematic approach to support full cycle of Sugar Learning Platform ecosystem. Harmonic Distribution consist of software, services and practices that make interacting within the Sugar community more useful. Harmonic Distribution consists of two major parts, [[#Harmonic_Distribution\|Harmonic Distribution]] and [[#Sugar_Network\|Sugar Network]].		: The systematic approach to support full cycle of Sugar Learning Platform ecosystem. Harmonic Distribution consist of software, services and practices that make interacting within the Sugar community more useful. Harmonic Distribution consists of two major parts, [[#Harmonic_Distribution\|Harmonic Distribution]] and [[#Sugar_Network\|Sugar Network]].

	===== [[Sweets Distribution]] =====		===== [[Sweets Distribution]] =====

	Provides base software in heterogeneous environment, i.e., most popular, within the Sugar community, GNU/Linux distributions and hardware platforms. Sweets Distribution provides the easy way to launch initial software and start exploring the rest of the Sugar related content using the [[#Sugar_Network\|Sugar Network]].		: Provides base software in heterogeneous environment, i.e., most popular, within the Sugar community, GNU/Linux distributions and hardware platforms. Sweets Distribution provides the easy way to launch initial software and start exploring the rest of the Sugar related content using the [[#Sugar_Network\|Sugar Network]].

	===== [[Sugar Network]] =====		===== [[Sugar Network]] =====

	The system that is intended to share different kinds of content within the Sugar community, e.g., Sugar Activities, artifacts created by Sugar Activities, books, etc. Using [[Wikipedia:Social_network\|social network]] mechanisms, setup the relations between community members to improve Sugar Network content. Sugar Network consists of one global server and arbitrary number of distributed servers (to support people who don't have direct access, e.g., due to lack on Internet connectivity, to the global one).		: The system that is intended to share different kinds of content within the Sugar community, e.g., Sugar Activities, artifacts created by Sugar Activities, books, etc. Using [[Wikipedia:Social_network\|social network]] mechanisms, setup the relations between community members to improve Sugar Network content. Sugar Network consists of one global server and arbitrary number of distributed servers (to support people who don't have direct access, e.g., due to lack on Internet connectivity, to the global one).

	<!-- The former "Sweets" evolved. Some of commented terms will be back after settling down new implementation.		<!-- The former "Sweets" evolved. Some of commented terms will be back after settling down new implementation.

Alsroot at 20:22, 28 April 2012

2012-04-28T20:22:43Z

@@ Line 2: / Line 2: @@
 == Glossary ==
 </noinclude>
 A list of terms to understand the basic concepts of ''Sweets''.
@@ Line 40: / Line 55: @@
 =====sweet package=====
 :Using the http://packages.sugarlabs.org Web UI, it is possible to create a repository with native packages from released ''sweets''.
+-->

Alsroot: moved Platform Team/Package Management System/Glossary to Platform Team/Glossary

2012-04-28T20:01:33Z

moved Platform Team/Package Management System/Glossary to Platform Team/Glossary

← Older revision	Revision as of 16:01, 28 April 2012
(No difference)

Alsroot: moved Platform Team/Sweets/Glossary to Platform Team/Package Management System/Glossary: "Sweets" has evolved to hidden SN parts and public "Sweets Distributoin"

2012-04-27T10:11:19Z

moved Platform Team/Sweets/Glossary to Platform Team/Package Management System/Glossary: "Sweets" has evolved to hidden SN parts and public "Sweets Distributoin"

← Older revision	Revision as of 06:11, 27 April 2012
(No difference)

Alsroot: /* Sweets Distribution */

2011-11-07T12:56:28Z

Sweets Distribution

← Older revision		Revision as of 08:56, 7 November 2011
Line 42:		Line 42:

	=====Sweets Distribution=====		=====Sweets Distribution=====
	:It is a [http://download.sugarlabs.org/packages/SweetsDistribution:/ repository] with Glucose and Fructose ''sweet packages'' based on {{Code\|~~sdk~~/}} ''sweets''.		:It is a [http://download.sugarlabs.org/packages/SweetsDistribution:/ repository] with Glucose and Fructose ''sweet packages'' based on {{Code\|dextrose/sugar}} ''sweets''.

FGrose: /* local sweet */

2011-09-05T16:45:25Z

local sweet

← Older revision		Revision as of 12:45, 5 September 2011
Line 36:		Line 36:

	=====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, ~~that implements~~ {{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 {{Code\|sdk/sugar-toolkit}} dependency of {{Code\|sdk/sugar}}.		: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=====

Alsroot: /* local sweet */

2011-09-05T08:04:17Z

local sweet

← Older revision		Revision as of 04:04, 5 September 2011
Line 36:		Line 36:

	=====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, that implements {{Code\|sdk/sugar-toolkit}} ''interface'', were cloned to the {{Code\|~/src/sugar-toolkit}} directory, then while running a {{Code\|~~sdl~~/sugar}} ''sweet'', it would become possible to reuse local sugar-toolkit sources as a regular ''implementation'' of {{Code\|sdk/sugar-toolkit}} dependency of {{Code\|sdk/sugar}}.		: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, that implements {{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 {{Code\|sdk/sugar-toolkit}} dependency of {{Code\|sdk/sugar}}.

	=====sweet package=====		=====sweet package=====