Sugar Network/Concept - Revision history

FGrose at 15:22, 9 June 2012

2012-06-09T15:22:43Z

Alsroot: /* Targeted audience */

2012-06-09T08:30:13Z

Targeted audience

← Older revision		Revision as of 04:30, 9 June 2012
Line 21:		Line 21:
	* Deployment supporters who need to provide technical and educational support;		* Deployment supporters who need to provide technical and educational support;
	* Software developers who will have a chance to get feedback directly from users.		* Software developers who will have a chance to get feedback directly from users.

			Particular persons might belong to several categories at the same time, e.g., be a content creator, a user of content created by different creators, review content uploaded by another people.
	\|}		\|}

Alsroot at 08:07, 9 June 2012

2012-06-09T08:07:37Z

← Older revision		Revision as of 04:07, 9 June 2012
Line 3:		Line 3:
	== Overview ==		== Overview ==

	The ~~whole initiative~~ is ~~tailored~~ by ~~the following decisions~~:		The major goal of the Sugar Network is providing an infrastructure to let people sharing different kinds of content, e.g., Sugar Activities, artifacts created by Sugar Activities, books, etc. for friends, a class, parents, teachers, or Sugar Learners anywhere.

			Functionality of Sugar Network is split into two parts:

	* ~~The Sugar Network should be useful in off-line environments;~~		* Core functionality that covers low level needs to work with content ([[#Summary\|described below]]);
	* The scope of provided [[#Resources\|resources]] should cover the full complement of low level ~~collaborative behaviors between Network participants; where ''low level'' means that~~ [[#~~Resources~~\|~~resources]] are shared for all types of collaborative [[#Contexts\|contexts~~]];		* Any amount of representation models that are based on core functionality and add high level scenarios to interact with the same content, e.g., gamification elements. Representation models are pluggable and optional.
	* ~~The scope~~ of ~~provided [[#Resources\|resources]] should be designed so~~ that ~~the Sugar Network is equally useful operating~~ on~~-line as off-line;~~
	* The software architecture and ~~interfaces~~ are ~~structured to stimulate a "doing"~~ and ~~"sharing" workflow~~.

	~~The whole Sugar Network is pictured by the following graphics:~~		== Targeted audience ==

	{\| border="0"		{\| border="0"
	\|- valign="top" align="let"		\|- valign="top" align="let"
	\| [[File:Sugar-network.png]]		\| [[File:Sugar-network-audience.png\|350px]]
	\| ~~Where,~~		\| The audience of Sugar Network might be different:
	* ~~'''Server'''<br>is shared data and services~~, ~~in general. It~~ might be ~~a server accessible from the Internet (~~on~~-line case) or various distributed servers located, e.g., in schools (off-line case). See [[Platform_Team/Sugar_Network\|technical pages]] for more details.~~
	* ~~'''Conceptual level logic'''<br>The design logic~~ and ~~software code structures that reify~~ the ~~Sugar~~ Network ~~concepts. From a conceptual level, these designs and code standards represent a separate entity that operates inbetween the Clients and Servers. From the~~ technical ~~perspective, this level is represented by the Server [[Platform_Team/Sugar_Network/API\|application programming interface (API)]]~~ and ~~[[Platform_Team/Sugar_Network/Objects_model\|objects model]] in particular.~~		* Students, might be different ages, depending on particular representation model;
	* ~~'''Client'''<br>is the software that allows Network participants~~ to ~~interact with the Sugar Network. These software components let people~~ get ~~access to the Sugar Network, and define how the Sugar Network should appear to~~ users according to their needs. The user experience provided by the client software will vary from need to need, starting from a couple of elements in the existing software [[Wikipedia:Graphical_user_interface\|GUI]] (when people even don't suspect they are interacting with the Sugar Network), and extending to clients that represent advanced conceptual elements of the Sugar Network as closely as possible.		* Educators who need to populate content for students and review what students uploaded to the Network;
			* Deployment supporters who need to provide technical and educational support;
			* Software developers who will have a chance to get feedback directly from users.
	\|}		\|}

Line 309:		Line 311:
	:* Click Home button for the found entity;		:* Click Home button for the found entity;
	:* ''TODO''		:* ''TODO''

			== Infrastructure overview ==

			The whole initiative is tailored by the following decisions:

			* The Sugar Network should be useful in off-line environments;
			* The scope of provided [[#Resources\|resources]] should cover the full complement of low level collaborative behaviors between Network participants; where ''low level'' means that [[#Resources\|resources]] are shared for all types of collaborative [[#Contexts\|contexts]];
			* The scope of provided [[#Resources\|resources]] should be designed so that the Sugar Network is equally useful operating on-line as off-line;
			* The software architecture and interfaces are structured to stimulate a "doing" and "sharing" workflow.

			The whole Sugar Network is pictured by the following graphics:

			{\| border="0"
			\|- valign="top" align="let"
			\| [[File:Sugar-network.png]]
			\| Where,
			* '''Server'''<br>is shared data and services, in general. It might be a server accessible from the Internet (on-line case) or various distributed servers located, e.g., in schools (off-line case). See [[Platform_Team/Sugar_Network\|technical pages]] for more details.
			* '''Conceptual level logic'''<br>The design logic and software code structures that reify the Sugar Network concepts. From a conceptual level, these designs and code standards represent a separate entity that operates inbetween the Clients and Servers. From the technical perspective, this level is represented by the Server [[Platform_Team/Sugar_Network/API\|application programming interface (API)]] and [[Platform_Team/Sugar_Network/Objects_model\|objects model]] in particular.
			* '''Client'''<br>is the software that allows Network participants to interact with the Sugar Network. These software components let people get access to the Sugar Network, and define how the Sugar Network should appear to users according to their needs. The user experience provided by the client software will vary from need to need, starting from a couple of elements in the existing software [[Wikipedia:Graphical_user_interface\|GUI]] (when people even don't suspect they are interacting with the Sugar Network), and extending to clients that represent advanced conceptual elements of the Sugar Network as closely as possible.
			\|}

	== Todo ==		== Todo ==

FGrose at 14:31, 30 May 2012

2012-05-30T14:31:37Z

← Older revision		Revision as of 10:31, 30 May 2012
Line 326:		Line 326:
	* [http://www.ideatorrent.org/ IdeaTorrent].		* [http://www.ideatorrent.org/ IdeaTorrent].
	* [http://www.curriki.org/ Curriki], Open Curricula Community.		* [http://www.curriki.org/ Curriki], Open Curricula Community.
	* [[~~Wiki~~:Gamification\|Gamification]].		* [[wikipedia:Gamification\|Gamification]].

Alsroot: /* See also */

2012-05-30T09:49:00Z

FGrose at 02:51, 10 April 2012

2012-04-10T02:51:52Z

Show changes

Alsroot: More object model changes

2012-04-09T21:53:06Z

More object model changes

← Older revision		Revision as of 17:53, 9 April 2012
Line 25:		Line 25:
	The Sugar Network is about all these:		The Sugar Network is about all these:

	* [[#~~Players~~\|~~Players~~]],		* [[#Users\|Users]],
	* in different [[#Contexts\|Contexts]],		* in different [[#Contexts\|Contexts]],
	* interacting with [[#Resources\|Resources]],		* interacting with [[#Resources\|Resources]],
	* to accomplish their [[#Needs\|Needs]].		* to accomplish their [[#Needs\|Needs]].
	* When changed, Resources broadcast [[#Events\|Events]].		* When changed, Resources broadcast [[#Events\|Events]].
	* Having [[#Workflows\|Workflows]] defined that describe the regular behaviour of ~~Players~~.		* Having [[#Workflows\|Workflows]] defined that describe the regular behaviour of Users.

	== Needs ==		== Needs ==
Line 38:		Line 38:
	'''Identity'''		'''Identity'''

	: Each ~~player or participant~~ should be able to create and manage a unique identity in the network. Every interaction of the ~~player~~ with the network should be accounted in the ~~player~~'s metrics, as eventually, this may be part of the ~~player~~ dashboard. Each ~~player~~ may have an individual reputation, based on other ~~players~~' ratings made on his contributions.		: Each User should be able to create and manage a unique identity in the network. Every interaction of the User with the network should be accounted in the User's metrics, as eventually, this may be part of the User's dashboard. Each User may have an individual reputation, based on other Users' ratings made on his contributions.

	'''Understanding'''		'''Understanding'''

	: A ~~player~~ should be able to view all objects and optionally apply filters to control their view based on the resource type, the Network Zoom level, tags, or the associated ~~player/team~~. In this preview, we may be able to offer basic statistics of the object in order to give an analytical perspective to the selection. The ~~player~~ should be able to select the object in order to participate on a deeper level, where he should be able to explore the associated resources. As a ~~player~~, I might receive events from the objects I'm subscribed to, as well as personal events, like invitations made by other ~~players~~.		: A User should be able to view all objects and optionally apply filters to control their view based on the resource type, the Network Zoom level, tags, or the associated Users. In this preview, we may be able to offer basic statistics of the object in order to give an analytical perspective to the selection. The User should be able to select the object in order to participate on a deeper level, where he should be able to explore the associated resources. As a User, I might receive events from the objects I'm subscribed to, as well as personal events, like invitations made by other Users.

	'''Participation'''		'''Participation'''

	: Any ~~player~~ may comment on any object, rate any contribution, edit any wiki, create any issue, attach any object to any gallery, become a follower of any object.		: Any User may comment on any object, rate any contribution, edit any wiki, create any issue, attach any object to any gallery, become a follower of any object.

	'''Creation'''		'''Creation'''

	: Any ~~player~~ may create a new Context by defining a name, the type of Context, and the Context objective(s). A Context's creator may invite other ~~players~~ to follow/contribute to his Context.		: Any User may create a new Context by defining a name, the type of Context, and the Context objective(s). A Context's creator may invite other Users to follow/contribute to his Context.

	== ~~Players~~ ==		== Users ==

	These are real people that take part in the Sugar Network.		These are real people that take part in the Sugar Network.
Line 62:		Line 62:
	=== Reputation ===		=== Reputation ===

	Any particular Resource, i.e., contributions of some ~~Players~~, might be rated by another ~~Players~~. The Reputation of a particular ~~Player~~ depends on how other ~~Players~~ appreciate him or his contributions.		Any particular Resource, i.e., contributions of some Users, might be rated by another Users. The Reputation of a particular User depends on how other Users appreciate him or his contributions.

	=== Statistics ===		=== Statistics ===

	Based on tracking of [[#Events\|Events]], it is possible to [[#Understanding\|measure]] a particular ~~Player~~'s behaviour. This might be useful, e.g., for researchers.		Based on tracking of [[#Events\|Events]], it is possible to [[#Understanding\|measure]] a particular User's behaviour. This might be useful, e.g., for researchers.

	== Contexts ==		== Contexts ==

	In the Sugar Network, Contexts are the classes of content or software that include with them assumptions on how they may be shared or used. A Context describes how ~~Players~~ behave with Resources. A Context represents the Behavior or set of Behaviors that are supported for associated Resources.		In the Sugar Network, Contexts are the classes of content or software that include with them assumptions on how they may be shared or used. A Context describes how Users behave with Resources. A Context represents the Behavior or set of Behaviors that are supported for associated Resources.

	There is a predefined general Context, the Global Context, which contains all other Contexts (according to the current [[#Network_Zoom\|zoom level]]). Thus, ~~Players~~ can interact with all Resources accessible on this [[#Network_Zoom\|zoom level]].		There is a predefined general Context, the Global Context, which contains all other Contexts (according to the current [[#Network_Zoom\|zoom level]]). Thus, Users can interact with all Resources accessible on this [[#Network_Zoom\|zoom level]].

	Context types may differ. For now, these are the only Context types:		Context types may differ. For now, these are the only Context types:
Line 211:		Line 211:
	== Events ==		== Events ==

	If some Resource has been changed, e.g., as a result of ~~Player~~ interacting, Resource sends global notifications. These notification might be seen while investigating this particular object or by Following this Resource. In the last case, events will go to followers' queue of global events.		If some Resource has been changed, e.g., as a result of User interacting, Resource sends global notifications. These notification might be seen while investigating this particular object or by Following this Resource. In the last case, events will go to followers' queue of global events.

	Events might be personal, e.g., personal invitations or personal messages.		Events might be personal, e.g., personal invitations or personal messages.
Line 217:		Line 217:
	== Workflows ==		== Workflows ==

	These are kinds of workflows that [[#Roles\|Roles]] can take part in. The particular activity might involve several ~~Players~~ and several Roles.		These are kinds of workflows that [[#Roles\|Roles]] can take part in. The particular activity might involve several Users and several Roles.

	=== Support ===		=== Support ===
Line 264:		Line 264:
	Sharing arbitrary education related media content.		Sharing arbitrary education related media content.

	:* Teacher (or any other ~~Player~~) creates new (or reuse existing) Wiki Context;		:* Teacher (or any other User) creates new (or reuse existing) Wiki Context;
	:* Set appropriate, to the purpose, Tags and Context description;		:* Set appropriate, to the purpose, Tags and Context description;
	:* Create initial Wiki page, populate it and attach media content;		:* Create initial Wiki page, populate it and attach media content;

Alsroot: /* Resources */ Reflect on recent object model changes

2012-04-09T21:50:16Z

Resources: Reflect on recent object model changes

← Older revision		Revision as of 17:50, 9 April 2012
Line 81:		Line 81:
	== Resources ==		== Resources ==

	The whole experience within the Sugar Network is about a ~~Player~~'s interaction with resources. Resources are tied to the current Context and might be of different types:		The whole experience within the Sugar Network is about a User's interaction with resources. Resources are tied to the current Context and might be of different types:

	* Feedback related:		* Feedback related:
Line 88:		Line 88:
	** [[#Problems\|Problems]],		** [[#Problems\|Problems]],
	* [[#Wiki\|Wiki]],		* [[#Wiki\|Wiki]],
	* [[#~~Gallery~~\|~~Gallery~~]],		* [[#Artifact\|Artifact]],
	* Development related:		* Development related:
	** [[#Sources\|Releases]],		** [[#Sources\|Releases]],
Line 127:		Line 127:
	=== Problems ===		=== Problems ===

	Report a problem with the Context. A user-friendly interface to complain about an error that the ~~Player~~ encountered when working with the Context. The workflow is much simpler, compared to typical bugs trackers, just complain and wait for a fix.		Report a problem with the Context. A user-friendly interface to complain about an error that the User encountered when working with the Context. The workflow is much simpler, compared to typical bugs trackers, just complain and wait for a fix.

	The rest of non-developers needs are covered by [[#Questions\|Questions]] and [[#Ideas\|Ideas]]. The developers needs are covered by the [[#Objectives\|Objectives]] and its advanced view in particular.		The rest of non-developers needs are covered by [[#Questions\|Questions]] and [[#Ideas\|Ideas]]. The developers needs are covered by the [[#Objectives\|Objectives]] and its advanced view in particular.
Line 158:		Line 158:
	:* View the history of modifying.		:* View the history of modifying.

	=== ~~Gallery~~ ===		=== Artifact ===

	A collection of ~~activity~~ objects of types depending on Context type~~. This is exactly~~ the ~~gallery to share your creatures~~. ~~Using the [[#Browser\|Browser]] it will~~ be ~~possible to explore Gallery entities directly on the top level~~.		A collection of binary objects, of types depending on Context type, associated the the Context. Such artifacts might be, for example, Journal objects created by Sugar activities.

	Actions:		Actions:
Line 172:		Line 172:
	:* Simplify creating new Exhibit having a UI way to fast share just created activity object, e.g., from in Naming alert or from Journal.		:* Simplify creating new Exhibit having a UI way to fast share just created activity object, e.g., from in Naming alert or from Journal.

	=== ~~Version~~ ===		=== Implementation ===

	For software Contexts, this Resource is about released versions of this Context software. This is exactly what ~~Player~~ can execute. There might be several ~~versions~~ with different stability levels. By default, ~~Players~~ execute only recent stable version, but it is possible to choose any version.		For software Contexts, this Resource is about released versions of this Context software. This is exactly what User can execute. There might be several implementations with different stability levels. By default, Users execute only recent stable version, but it is possible to choose any version.

	Actions:		Actions:

	:* Context owners can create new ~~Version~~;		:* Context owners can create new Implementation;
	:* Launch.		:* Launch.
	:* Discuss the Release;		:* Discuss the Release;
Line 192:		Line 192:
	These are the exactly objectives that Context is trying to achieve. This type of Resources has two faces:		These are the exactly objectives that Context is trying to achieve. This type of Resources has two faces:

	* The view for ~~Players~~ that are not the part of Context implementers, they see this Resource as a list of, e.g., features that Context is trying to provide;		* The view for Users that are not the part of Context implementers, they see this Resource as a list of, e.g., features that Context is trying to provide;
	* The full functional project management interface for people who are owners of the Context and take care of implementation.		* The full functional project management interface for people who are owners of the Context and take care of implementation.

FGrose at 21:06, 9 April 2012

2012-04-09T21:06:17Z

Show changes

Alsroot: /* Resources */ History won't be implemented, at least in nearest future

2012-01-02T21:57:06Z

Resources: History won't be implemented, at least in nearest future

← Older revision		Revision as of 17:57, 2 January 2012
Line 92:		Line 92:
	** [[#Sources\|Releases]],		** [[#Sources\|Releases]],
	** [[#Objectives\|Objectives]].		** [[#Objectives\|Objectives]].

	~~When it is possible, Resources support the history. Resources can't be physically removed, only stated as removed and hidden from the default observing.~~

	=== Questions ===		=== Questions ===

← Older revision		Revision as of 05:49, 30 May 2012
Line 326:		Line 326:
	* [http://www.ideatorrent.org/ IdeaTorrent].		* [http://www.ideatorrent.org/ IdeaTorrent].
	* [http://www.curriki.org/ Curriki], Open Curricula Community.		* [http://www.curriki.org/ Curriki], Open Curricula Community.
			* [[Wiki:Gamification\|Gamification]].