Sugar Network/Declaration of purpose - Revision history

Alsroot at 00:00, 28 January 2012

2012-01-28T00:00:50Z

← Older revision		Revision as of 20:00, 27 January 2012
Line 8:		Line 8:
	## Using social functionality (1.3) and integrated automatic fail reporting functionality, it will be possible to provide technical support, e.g., from Sugar Activity authors or from Sugar deployment personal.		## Using social functionality (1.3) and integrated automatic fail reporting functionality, it will be possible to provide technical support, e.g., from Sugar Activity authors or from Sugar deployment personal.
	# ''How is it done today, and what are the limits of current practice?''		# ''How is it done today, and what are the limits of current practice?''
	## In comparing to (1.1). There are several resources for Sugar, and, educational in general, content. Such as [[Activity Library]], several methods to get to get Sugar Activities that are integrated to the Sugar Shell, various Wikis, services placed on school servers (starting from Moodle and ending with ure HTML pages that serves Sugar Activity bundles. The users experience is too different from ~~content~~ source to source. Besides, these sources might be not students ~~friendly~~, e.g., it will require creating an account (with specifying email address), be too technical like sugar mailing lists. In most cases they are poorly integrated to the Sugar desktop environment.		## In comparing to (1.1). There are several resources for Sugar, and, educational in general, content. Such as [[Activity Library]], several methods to get to get Sugar Activities that are integrated to the Sugar Shell, various Wikis, services placed on school servers (starting from Moodle and ending with ure HTML pages that serves Sugar Activity bundles. The users experience is too different from source to source. Besides, these sources might be not friendly to students, e.g., it will require creating an account (with specifying email address), be too technical like sugar mailing lists. In most cases they are poorly integrated to the Sugar desktop environment.
	## In comparing to (1.2). The richest resources are all located in the Internet, but Internet access is not chip and wide for all Sugar deployments, and might be simply absent. If some resources are accessible on school servers, it might be not integrated to the global Sugar community. To support [[Wikipedia:Offline\|offline]] workflow, students need to ~~routines~~ work, e.g., copying Sugar Activity bundles from the Internet or school's server to the Journal. And as (2.1) points, on all levels the users experience is ~~too~~ different.		## In comparing to (1.2). The richest resources are all located in the Internet, but Internet access is not chip and wide for all Sugar deployments, and might be simply absent. If some resources are accessible on school servers, it might be not integrated to the global Sugar community. To support [[Wikipedia:Offline\|offline]] workflow, students need to do routine work, e.g., copying Sugar Activity bundles from the Internet or school's server to the Journal. And as (2.1) points, on all levels the users experience is different.
	## In comparing to (1.3). The existing ways to discuss the content within the Sugar community is either limitted or too basic. There is the [[Activity Library]], but people can post only reviews (not questions, ideas or problems). To report a bug they need to login to [http://bugs.sugarlabs.org bugs.sugarlabs.org]. To ask question or share ideas, they need to subscribe to mailing lists. All these resources are located in the Internet (2.2). And mostly not friendly for students at all (2.1). Besides, some resources located on school servers might not allow any collaboration and content uploading at all, i.e., pure HTML page to download Sugar Activity bundles. And as (2.1) says, the users experience is too different from resource to resource.		## In comparing to (1.3). The existing ways to discuss the content within the Sugar community is either limitted or too basic. There is the [[Activity Library]], but people can post only reviews (not questions, ideas or problems). To report a bug they need to login to [http://bugs.sugarlabs.org bugs.sugarlabs.org]. To ask question or share ideas, they need to subscribe to mailing lists. All these resources are located in the Internet (2.2). And mostly not friendly for students at all (2.1). Besides, some resources located on school servers might not allow any collaboration and content uploading at all, i.e., pure HTML page to download Sugar Activity bundles. And as (2.1) says, the users experience is too different from resource to resource.
	## In comparing to (1.4). Sugar Shell's functionality is pretty basic in case of providing support for educational related needs. There should plenty of ways to make Sugar Learning environment more integrated to the educational process.		## In comparing to (1.4). Sugar Shell's functionality is pretty basic in case of providing support for educational related needs. There should plenty of ways to make Sugar Learning environment more integrated to the educational process.

Alsroot at 23:36, 27 January 2012

2012-01-27T23:36:38Z

← Older revision		Revision as of 19:36, 27 January 2012
Line 11:		Line 11:
	## In comparing to (1.2). The richest resources are all located in the Internet, but Internet access is not chip and wide for all Sugar deployments, and might be simply absent. If some resources are accessible on school servers, it might be not integrated to the global Sugar community. To support [[Wikipedia:Offline\|offline]] workflow, students need to routines work, e.g., copying Sugar Activity bundles from the Internet or school's server to the Journal. And as (2.1) points, on all levels the users experience is too different.		## In comparing to (1.2). The richest resources are all located in the Internet, but Internet access is not chip and wide for all Sugar deployments, and might be simply absent. If some resources are accessible on school servers, it might be not integrated to the global Sugar community. To support [[Wikipedia:Offline\|offline]] workflow, students need to routines work, e.g., copying Sugar Activity bundles from the Internet or school's server to the Journal. And as (2.1) points, on all levels the users experience is too different.
	## In comparing to (1.3). The existing ways to discuss the content within the Sugar community is either limitted or too basic. There is the [[Activity Library]], but people can post only reviews (not questions, ideas or problems). To report a bug they need to login to [http://bugs.sugarlabs.org bugs.sugarlabs.org]. To ask question or share ideas, they need to subscribe to mailing lists. All these resources are located in the Internet (2.2). And mostly not friendly for students at all (2.1). Besides, some resources located on school servers might not allow any collaboration and content uploading at all, i.e., pure HTML page to download Sugar Activity bundles. And as (2.1) says, the users experience is too different from resource to resource.		## In comparing to (1.3). The existing ways to discuss the content within the Sugar community is either limitted or too basic. There is the [[Activity Library]], but people can post only reviews (not questions, ideas or problems). To report a bug they need to login to [http://bugs.sugarlabs.org bugs.sugarlabs.org]. To ask question or share ideas, they need to subscribe to mailing lists. All these resources are located in the Internet (2.2). And mostly not friendly for students at all (2.1). Besides, some resources located on school servers might not allow any collaboration and content uploading at all, i.e., pure HTML page to download Sugar Activity bundles. And as (2.1) says, the users experience is too different from resource to resource.
	## In comparing to (1.4). Sugar Shell's functionality is pretty ~~simple~~ in case of providing support for educational related ~~workflows that might happen, e.g., during the class time~~. There should plenty of ways to make Sugar Learning environment more ~~useful for education needs~~.		## In comparing to (1.4). Sugar Shell's functionality is pretty basic in case of providing support for educational related needs. There should plenty of ways to make Sugar Learning environment more integrated to the educational process.
	## In comparing to (1.5). It is mostly impossible to get feedback from students, that use Sugar Activities in the field, on [http://bugs.sugarlabs.org bugs.sugarlabs.org] on mailing lists, partially because of lack of Internet connection (2.1) and partially because these resources are too technical (2.2). Besides, there is no convenient and direct (between users and Activity developers) ways to share technical information when Sugar Activity fails.		## In comparing to (1.5). It is mostly impossible to get feedback from students, that use Sugar Activities in the field, on [http://bugs.sugarlabs.org bugs.sugarlabs.org] on mailing lists, partially because of lack of Internet connection (2.1) and partially because these resources are too technical (2.2). Besides, there is no convenient and direct (between users and Activity developers) ways to share technical information when Sugar Activity fails.
	# ''What's new in your approach and why do you think it will be successful?''		# ''What's new in your approach and why do you think it will be successful?''

Alsroot at 23:00, 27 January 2012

2012-01-27T23:00:05Z

← Older revision		Revision as of 19:00, 27 January 2012
Line 17:		Line 17:
	## To solve (2.2) and accomplish (1.2). On all network accessibility levels (online, school, offline), people use the same Sugar Network Browser (3.1). The only differences are: being online, people see the full picture; being connected to school network, people see the picture that is a snapshot of the full picture (that is being updated from time to time); being offline, e.g., switching from online of from school network, people see only resources they marked as persistent manually.		## To solve (2.2) and accomplish (1.2). On all network accessibility levels (online, school, offline), people use the same Sugar Network Browser (3.1). The only differences are: being online, people see the full picture; being connected to school network, people see the picture that is a snapshot of the full picture (that is being updated from time to time); being offline, e.g., switching from online of from school network, people see only resources they marked as persistent manually.
	## To solve (2.3) and accomplish (1.3). Still, it is the same Sugar Network Browser (3.1). On all network accessibility (3.2) levels, people can share content created by themselves, ask questions, share ideas, complain about problem, etc. for all accessible resources in their Browser. After increasing network accessibility level, e.g., connecting to the school server after being offline, all new changes will be merged to the upper level.		## To solve (2.3) and accomplish (1.3). Still, it is the same Sugar Network Browser (3.1). On all network accessibility (3.2) levels, people can share content created by themselves, ask questions, share ideas, complain about problem, etc. for all accessible resources in their Browser. After increasing network accessibility level, e.g., connecting to the school server after being offline, all new changes will be merged to the upper level.
			## To solve (2.4) and accomplish (1.4). Still, it is the same Sugar Network Browser (3.1). Teachers will get a channel to share methodological materials, track how their students behave within the Sugar Network, get access to users behaviour statistics, to accomplish various educational related needs.
	## To solve (2.4) and accomplish (1.4). Still, it is the same Sugar Network Browser (3.1). After clicking the Sugar Activity and getting its fail, the error dialog might show the button "Share the report", then, nothing else from user's point of view. Activity developer will get this repost immediately (depending on network accessibility level). Besides, people can ask questions, share ideas, complain about problems, all this information is accessible for developers.		## To solve (2.5) and accomplish (1.5). Still, it is the same Sugar Network Browser (3.1). After clicking the Sugar Activity and getting its fail, the error dialog might show the button "Share the report", then, nothing else from user's point of view. Activity developer will get this repost immediately (depending on network accessibility level). Besides, people can ask questions, share ideas, complain about problems, all this information is accessible for developers.

	## To solve (2.5) and accomplish (1.5). Still, it is the same Sugar Network Browser (3.1). This part is the most non-trivial and not technical. But, it should be possible to support different educational related workflows in the Browser, e.g., during the class time, students migth see only resources that are related to the current subject (when teacher has more powerful view in his Browser).


	# ''Who cares?''		# ''Who cares?''
	## Students		## Students
	## Teachers		## Teachers
	## Local deployment supporters		## Local deployment supporters
	## ~~Software~~ developers		## The Sugar community that can help all previous categories of Sugar Network participants, e.g. software developers or educators.
	# ''If you're successful, what difference will it make?''		# ''If you're successful, what difference will it make?''
	## For students (4.1). The central place to get convenient access to various content (Sugar Activities, Journal objects, Wiki articles). The content might be mostly the same that might be found in the Internet but on different resources. The additional (for online case) and convenient tool to support social activities (regarding Sugar Network objects) to share ideas and complains regarding particular resources to collaborate with other people.		## For students (4.1). The central place to get convenient access to various content (Sugar Activities, Journal objects, Wiki articles). The content might be mostly the same that might be found in the Internet but on different resources. The additional (for online case) and convenient tool to support social activities (regarding Sugar Network objects) to share ideas and complains regarding particular resources to collaborate with other people.
	## For teachers (4.2). Sugar Network is the right place to share various methodical materials and have educators only level discussions. Potentially, Sugar Network might be well tuned regarding educational process.		## For teachers (4.2). Sugar Network is the right place to share various methodical materials and have educators only level discussions. Potentially, Sugar Network might be well tuned regarding educational process.
	## For local deployment supporters (4.3). More convenient way to provide remote support for people at schools, especially for offline schools.		## For local deployment supporters (4.3). More convenient way to provide remote support for people at schools, especially for offline schools.
	## For ~~software developers~~ (4.4). ~~Developers~~ will get a chance to have direct feedback from the field, including auto generated reports about software fails.		## For Sugar community (4.4). People will get a chance to have direct feedback from the field, including auto generated reports about software fails.
	# ''What are the risks and the payoffs?''		# ''What are the risks and the payoffs?''
	#: The idea might be evolved during the process of implementation. But for sure, there are a problem (2) and it should be solved. Any doing in this direction should be useful, even if original intention will be shifted.		#: The idea might be evolved during the process of implementation. But for sure, there are a problem (2) and it should be solved. Any doing in this direction should be useful, even if original intention will be shifted.

Alsroot at 22:52, 27 January 2012

2012-01-27T22:52:46Z

← Older revision		Revision as of 18:52, 27 January 2012
Line 2:		Line 2:

	# ''What are you trying to do? Articulate your objectives using absolutely no jargon.''		# ''What are you trying to do? Articulate your objectives using absolutely no jargon.''
	## The convenient and well integrated, to the Sugar, environment to share various types of content. Such as Sugar Activities, content created by Sugar Activities, documentation and educational materials, etc.		## The convenient and well integrated, to the Sugar, environment to share various types of content created or introduced by Sugar Network participants. Such as Sugar Activities, content created by Sugar Activities, documentation and educational materials, etc.
	## Provide ~~this access~~ (1.1), but with different latencies, on several [[Wikipedia:Computer_network\|Network]] levels, i.e., [[Wikipedia:Online\|online]] access to the Internet, access to the school network with possible (but not mandatory) access to the Internet, [[Wikipedia:Offline\|offline]] case when Sugar Network participant has only his computer.		## Provide (1.1), but with different latencies, on several [[Wikipedia:Computer_network\|Network]] levels, i.e., [[Wikipedia:Online\|online]] access to the Internet, access to the school network with possible (but not mandatory) access to the Internet, [[Wikipedia:Offline\|offline]] case when Sugar Network participant has only his computer.
	## Supplement ~~this access~~ (1.1) on all levels (1.2) with [[Wikipedia:Social_network\|social network]] features when Sugar Network participants can ~~share content created by themselves,~~ ask questions, propose ideas, complain about problems and express opinions ~~within~~ the Sugar Network.		## Supplement (1.1) on all Network levels (1.2) with [[Wikipedia:Social_network\|social network]] features when Sugar Network participants can ask questions, propose ideas, complain about problems and express opinions regarding the content found in the Sugar Network.
	## ~~Using~~ social functionality (1.3) and integrated to ~~the Sugar~~ Network automatic ~~bug report~~ functionality, it will be possible to provide technical support, e.g., from Sugar Activity authors or from Sugar deployment personal.		## Sharing content (1.1), using social functionality (1.3) and integrated reporting features, such as users behaviour statistics, it will be possible to provide educational support on all Network levels (1.2).
	~~## The last, but not the least. The entire Sugar Network should be well integrated to the educational process, e.g., support different scope workflows, such as school, class time, personal home work.~~		## Using social functionality (1.3) and integrated automatic fail reporting functionality, it will be possible to provide technical support, e.g., from Sugar Activity authors or from Sugar deployment personal.

	# ''How is it done today, and what are the limits of current practice?''		# ''How is it done today, and what are the limits of current practice?''
	## In comparing to (1.1). There are several resources for Sugar, and, educational in general, content. Such as [[Activity Library]], several methods to get to get Sugar Activities that are integrated to the Sugar Shell, various Wikis, services placed on school servers (starting from Moodle and ending with ure HTML pages that serves Sugar Activity bundles. The users experience is too different from content source to source. Besides, these sources might be not students friendly, e.g., it will require creating an account (with specifying email address), be too technical like sugar mailing lists. In most cases they are poorly integrated to the Sugar desktop environment.		## In comparing to (1.1). There are several resources for Sugar, and, educational in general, content. Such as [[Activity Library]], several methods to get to get Sugar Activities that are integrated to the Sugar Shell, various Wikis, services placed on school servers (starting from Moodle and ending with ure HTML pages that serves Sugar Activity bundles. The users experience is too different from content source to source. Besides, these sources might be not students friendly, e.g., it will require creating an account (with specifying email address), be too technical like sugar mailing lists. In most cases they are poorly integrated to the Sugar desktop environment.

	## In comparing to (1.2). The richest resources are all located in the Internet, but Internet access is not chip and wide for all Sugar deployments, and might be simply absent. If some resources are accessible on school servers, it might be not integrated to the global Sugar community. To support [[Wikipedia:Offline\|offline]] workflow, students need to routines work, e.g., copying Sugar Activity bundles from the Internet or school's server to the Journal. And as (2.1) points, on all levels the users experience is too different.		## In comparing to (1.2). The richest resources are all located in the Internet, but Internet access is not chip and wide for all Sugar deployments, and might be simply absent. If some resources are accessible on school servers, it might be not integrated to the global Sugar community. To support [[Wikipedia:Offline\|offline]] workflow, students need to routines work, e.g., copying Sugar Activity bundles from the Internet or school's server to the Journal. And as (2.1) points, on all levels the users experience is too different.
	## In comparing to (1.3). The existing ways to ~~share~~ content within the Sugar community is either limitted or too basic. There is the [[Activity Library]], but people can post only reviews (not questions, ideas or problems). To report a bug they need to login to [http://bugs.sugarlabs.org bugs.sugarlabs.org]. To ask question or share ideas, they need to subscribe to mailing lists. All these resources are located in the Internet (2.2). And mostly not friendly for students at all (2.1). Besides, some resources located on school servers might not allow any collaboration and content uploading at all, i.e., pure HTML page to download Sugar Activity bundles. And as (2.1) says, the users experience is too different from resource to resource.		## In comparing to (1.3). The existing ways to discuss the content within the Sugar community is either limitted or too basic. There is the [[Activity Library]], but people can post only reviews (not questions, ideas or problems). To report a bug they need to login to [http://bugs.sugarlabs.org bugs.sugarlabs.org]. To ask question or share ideas, they need to subscribe to mailing lists. All these resources are located in the Internet (2.2). And mostly not friendly for students at all (2.1). Besides, some resources located on school servers might not allow any collaboration and content uploading at all, i.e., pure HTML page to download Sugar Activity bundles. And as (2.1) says, the users experience is too different from resource to resource.
	## In comparing to (1.4). It is mostly impossible to get feedback from students, that use Sugar Activities in the field, on [http://bugs.sugarlabs.org bugs.sugarlabs.org] on mailing lists, partially because of lack of Internet connection (2.1) and partially because these resources are too technical (2.2). Besides, there is no convenient and direct (between users and Activity developers) ways to share technical information when Sugar Activity fails.		## In comparing to (1.4). Sugar Shell's functionality is pretty simple in case of providing support for educational related workflows that might happen, e.g., during the class time. There should plenty of ways to make Sugar Learning environment more useful for education needs.
	## In comparing to (1.5). Sugar Shell's functionality is pretty simple in case of providing support for educational related workflows that might happen, e.g., during the class time. There should plenty of ways to make Sugar Learning environment more useful.		## In comparing to (1.5). It is mostly impossible to get feedback from students, that use Sugar Activities in the field, on [http://bugs.sugarlabs.org bugs.sugarlabs.org] on mailing lists, partially because of lack of Internet connection (2.1) and partially because these resources are too technical (2.2). Besides, there is no convenient and direct (between users and Activity developers) ways to share technical information when Sugar Activity fails.
	# ''What's new in your approach and why do you think it will be successful?''		# ''What's new in your approach and why do you think it will be successful?''
	## To solve (2.1) and accomplish (1.1). Sugar Network is not intended to replace all existing (2.1) resources, but rather get singular and unified access point to the same resources from the Sugar Network Browser application that is well integrated to the Sugar desktop environment. It should be friendly to students, i.e., instead of going to [http://bugs.sugarlabs.org bugs.sugarlabs.org], creating an account there, create new ticket with possibility to set bunch of technical fields (like targeting release, OS, etc), a student needs to open Sugar Network Browser, find the targeting activity and type the problem (just the text). Or, to launch Sugar Activity, a student should not browse [[Activity Library]], school server, or Wikis, just click it in Sugar Network Browser.		## To solve (2.1) and accomplish (1.1). Sugar Network is not intended to replace all existing (2.1) resources, but rather get singular and unified access point to the same resources from the Sugar Network Browser application that is well integrated to the Sugar desktop environment. It should be friendly to students, i.e., instead of going to [http://bugs.sugarlabs.org bugs.sugarlabs.org], creating an account there, create new ticket with possibility to set bunch of technical fields (like targeting release, OS, etc), a student needs to open Sugar Network Browser, find the targeting activity and type the problem (just the text). Or, to launch Sugar Activity, a student should not browse [[Activity Library]], school server, or Wikis, just click it in Sugar Network Browser.
	## To solve (2.2) and accomplish (1.2). On all network accessibility levels (online, school, offline), people use the same Sugar Network Browser (3.1). The only differences are: being online, people see the full picture; being connected to school network, people see the picture that is a snapshot of the full picture (that is being updated from time to time); being offline, e.g., switching from online of from school network, people see only resources they marked as persistent manually.		## To solve (2.2) and accomplish (1.2). On all network accessibility levels (online, school, offline), people use the same Sugar Network Browser (3.1). The only differences are: being online, people see the full picture; being connected to school network, people see the picture that is a snapshot of the full picture (that is being updated from time to time); being offline, e.g., switching from online of from school network, people see only resources they marked as persistent manually.
	## To solve (2.3) and accomplish (1.3). Still, it is the same Sugar Network Browser (3.1). On all network accessibility (3.2) levels, people can share content created by themselves, ask questions, share ideas, complain about problem, etc. for all accessible resources in their Browser. After increasing network accessibility level, e.g., connecting to the school server after being offline, all new changes will be merged to the upper level.		## To solve (2.3) and accomplish (1.3). Still, it is the same Sugar Network Browser (3.1). On all network accessibility (3.2) levels, people can share content created by themselves, ask questions, share ideas, complain about problem, etc. for all accessible resources in their Browser. After increasing network accessibility level, e.g., connecting to the school server after being offline, all new changes will be merged to the upper level.

	## To solve (2.4) and accomplish (1.4). Still, it is the same Sugar Network Browser (3.1). After clicking the Sugar Activity and getting its fail, the error dialog might show the button "Share the report", then, nothing else from user's point of view. Activity developer will get this repost immediately (depending on network accessibility level). Besides, people can ask questions, share ideas, complain about problems, all this information is accessible for developers.		## To solve (2.4) and accomplish (1.4). Still, it is the same Sugar Network Browser (3.1). After clicking the Sugar Activity and getting its fail, the error dialog might show the button "Share the report", then, nothing else from user's point of view. Activity developer will get this repost immediately (depending on network accessibility level). Besides, people can ask questions, share ideas, complain about problems, all this information is accessible for developers.

	## To solve (2.5) and accomplish (1.5). Still, it is the same Sugar Network Browser (3.1). This part is the most non-trivial and not technical. But, it should be possible to support different educational related workflows in the Browser, e.g., during the class time, students migth see only resources that are related to the current subject (when teacher has more powerful view in his Browser).		## To solve (2.5) and accomplish (1.5). Still, it is the same Sugar Network Browser (3.1). This part is the most non-trivial and not technical. But, it should be possible to support different educational related workflows in the Browser, e.g., during the class time, students migth see only resources that are related to the current subject (when teacher has more powerful view in his Browser).


	# ''Who cares?''		# ''Who cares?''
	## Students		## Students

Alsroot at 22:28, 27 January 2012

2012-01-27T22:28:58Z

← Older revision		Revision as of 18:28, 27 January 2012
Line 2:		Line 2:

	# ''What are you trying to do? Articulate your objectives using absolutely no jargon.''		# ''What are you trying to do? Articulate your objectives using absolutely no jargon.''
	## ~~Convenient, unified,~~ and well integrated to the Sugar ~~desktop~~ environment ~~access~~ to various ~~Sugar, and, education in general,~~ content. Such as Sugar Activities, content created by Sugar Activities, documentation and educational materials, etc.		## The convenient and well integrated, to the Sugar, environment to share various types of content. Such as Sugar Activities, content created by Sugar Activities, documentation and educational materials, etc.
	## Provide this access (1.1), but with different latencies, on several [[Wikipedia:Computer_network\|Network]] levels, i.e., [[Wikipedia:Online\|online]] access to the Internet, access to the school network with possible (but not mandatory) access to the Internet, [[Wikipedia:Offline\|offline]] case when Sugar Network participant has only his computer.		## Provide this access (1.1), but with different latencies, on several [[Wikipedia:Computer_network\|Network]] levels, i.e., [[Wikipedia:Online\|online]] access to the Internet, access to the school network with possible (but not mandatory) access to the Internet, [[Wikipedia:Offline\|offline]] case when Sugar Network participant has only his computer.
	## Supplement this access (1.1) on all levels (1.2) with [[Wikipedia:Social_network\|social network]] features when Sugar Network participants can share content created by themselves, ask questions, propose ideas, complain about problems and express opinions within the Sugar Network.		## Supplement this access (1.1) on all levels (1.2) with [[Wikipedia:Social_network\|social network]] features when Sugar Network participants can share content created by themselves, ask questions, propose ideas, complain about problems and express opinions within the Sugar Network.
	## Using social functionality (1.3) and integrated to the Sugar Network automatic bug report functionality, it will be possible to provide technical support, e.g., from Sugar Activity authors or from Sugar deployment personal.		## Using social functionality (1.3) and integrated to the Sugar Network automatic bug report functionality, it will be possible to provide technical support, e.g., from Sugar Activity authors or from Sugar deployment personal.
	## The last, but not the least. The entire Sugar Network should be well integrated to the educational process, e.g., support different scope workflows, such as school, class time, personal home work.		## The last, but not the least. The entire Sugar Network should be well integrated to the educational process, e.g., support different scope workflows, such as school, class time, personal home work.

	# ''How is it done today, and what are the limits of current practice?''		# ''How is it done today, and what are the limits of current practice?''
	## In comparing to (1.1). There are several resources for Sugar, and, educational in general, content. Such as [[Activity Library]], several methods to get to get Sugar Activities that are integrated to the Sugar Shell, various Wikis, services placed on school servers (starting from Moodle and ending with ure HTML pages that serves Sugar Activity bundles. The users experience is too different from content source to source. Besides, these sources might be not students friendly, e.g., it will require creating an account (with specifying email address), be too technical like sugar mailing lists. In most cases they are poorly integrated to the Sugar desktop environment.		## In comparing to (1.1). There are several resources for Sugar, and, educational in general, content. Such as [[Activity Library]], several methods to get to get Sugar Activities that are integrated to the Sugar Shell, various Wikis, services placed on school servers (starting from Moodle and ending with ure HTML pages that serves Sugar Activity bundles. The users experience is too different from content source to source. Besides, these sources might be not students friendly, e.g., it will require creating an account (with specifying email address), be too technical like sugar mailing lists. In most cases they are poorly integrated to the Sugar desktop environment.

	## In comparing to (1.2). The richest resources are all located in the Internet, but Internet access is not chip and wide for all Sugar deployments, and might be simply absent. If some resources are accessible on school servers, it might be not integrated to the global Sugar community. To support [[Wikipedia:Offline\|offline]] workflow, students need to routines work, e.g., copying Sugar Activity bundles from the Internet or school's server to the Journal. And as (2.1) points, on all levels the users experience is too different.		## In comparing to (1.2). The richest resources are all located in the Internet, but Internet access is not chip and wide for all Sugar deployments, and might be simply absent. If some resources are accessible on school servers, it might be not integrated to the global Sugar community. To support [[Wikipedia:Offline\|offline]] workflow, students need to routines work, e.g., copying Sugar Activity bundles from the Internet or school's server to the Journal. And as (2.1) points, on all levels the users experience is too different.
	## In comparing to (1.3). The existing ways to share content within the Sugar community is either limitted or too basic. There is the [[Activity Library]], but people can post only reviews (not questions, ideas or problems). To report a bug they need to login to [http://bugs.sugarlabs.org bugs.sugarlabs.org]. To ask question or share ideas, they need to subscribe to mailing lists. All these resources are located in the Internet (2.2). And mostly not friendly for students at all (2.1). Besides, some resources located on school servers might not allow any collaboration and content uploading at all, i.e., pure HTML page to download Sugar Activity bundles. And as (2.1) says, the users experience is too different from resource to resource.		## In comparing to (1.3). The existing ways to share content within the Sugar community is either limitted or too basic. There is the [[Activity Library]], but people can post only reviews (not questions, ideas or problems). To report a bug they need to login to [http://bugs.sugarlabs.org bugs.sugarlabs.org]. To ask question or share ideas, they need to subscribe to mailing lists. All these resources are located in the Internet (2.2). And mostly not friendly for students at all (2.1). Besides, some resources located on school servers might not allow any collaboration and content uploading at all, i.e., pure HTML page to download Sugar Activity bundles. And as (2.1) says, the users experience is too different from resource to resource.

Alsroot at 15:41, 20 January 2012

2012-01-20T15:41:42Z

← Older revision		Revision as of 11:41, 20 January 2012
Line 4:		Line 4:
	## Convenient, unified, and well integrated to the Sugar desktop environment access to various Sugar, and, education in general, content. Such as Sugar Activities, content created by Sugar Activities, documentation and educational materials, etc.		## Convenient, unified, and well integrated to the Sugar desktop environment access to various Sugar, and, education in general, content. Such as Sugar Activities, content created by Sugar Activities, documentation and educational materials, etc.
	## Provide this access (1.1), but with different latencies, on several [[Wikipedia:Computer_network\|Network]] levels, i.e., [[Wikipedia:Online\|online]] access to the Internet, access to the school network with possible (but not mandatory) access to the Internet, [[Wikipedia:Offline\|offline]] case when Sugar Network participant has only his computer.		## Provide this access (1.1), but with different latencies, on several [[Wikipedia:Computer_network\|Network]] levels, i.e., [[Wikipedia:Online\|online]] access to the Internet, access to the school network with possible (but not mandatory) access to the Internet, [[Wikipedia:Offline\|offline]] case when Sugar Network participant has only his computer.
	## Supplement this access (1.1) on all levels (1.2) with [[Wikipedia:Social_network\|social network]] features when Sugar Network participants can share content created by themselves, questions, ideas, problems and opinions within the Sugar Network.		## Supplement this access (1.1) on all levels (1.2) with [[Wikipedia:Social_network\|social network]] features when Sugar Network participants can share content created by themselves, ask questions, propose ideas, complain about problems and express opinions within the Sugar Network.
	## Using social functionality (1.3) and integrated to the Sugar Network automatic bug report functionality, it will be possible to provide technical support, e.g., from Sugar Activity authors or from Sugar deployment personal.		## Using social functionality (1.3) and integrated to the Sugar Network automatic bug report functionality, it will be possible to provide technical support, e.g., from Sugar Activity authors or from Sugar deployment personal.
	## The last, but not the least. The entire Sugar Network should be well integrated to the educational process, e.g., support different scope workflows, such as school, class time, personal home work.		## The last, but not the least. The entire Sugar Network should be well integrated to the educational process, e.g., support different scope workflows, such as school, class time, personal home work.

Alsroot at 15:39, 20 January 2012

2012-01-20T15:39:54Z

Alsroot at 00:00, 20 January 2012

2012-01-20T00:00:58Z

← Older revision		Revision as of 20:00, 19 January 2012
Line 12:		Line 12:
	## In comparing to (1.3). The existing ways to share content within the Sugar community is either imited or too basic. There is the [[Activity Library]], but people can post only reviews. To report a bug they need to login to [http://bugs.sugarlabs.org bugs.sugarlabs.org]. To ask question or share ideas, they need to subscribe to mailing lists. All these resources are located in the Internet (2.2). And mostly not users friendly for students at all (2.1). Besides, some resources located on school servers might not allow any collaboration at all, i.e., pure HTML page to download Sugar Activity bundles. And as (2.1) says, the users experience is too different from resource to resource.		## In comparing to (1.3). The existing ways to share content within the Sugar community is either imited or too basic. There is the [[Activity Library]], but people can post only reviews. To report a bug they need to login to [http://bugs.sugarlabs.org bugs.sugarlabs.org]. To ask question or share ideas, they need to subscribe to mailing lists. All these resources are located in the Internet (2.2). And mostly not users friendly for students at all (2.1). Besides, some resources located on school servers might not allow any collaboration at all, i.e., pure HTML page to download Sugar Activity bundles. And as (2.1) says, the users experience is too different from resource to resource.
	## In comparing to (1.4). It is mostly impossible to get feedback from students, that use Sugar Activities in the field, on [http://bugs.sugarlabs.org bugs.sugarlabs.org] on mailing lists, partially because of lack of Internet connection (2.1) and partially because these resources are too technical (2.2). Besides, there is no convenient and direct (between users and Activity developers) ways to share technical information when Sugar Activity fails.		## In comparing to (1.4). It is mostly impossible to get feedback from students, that use Sugar Activities in the field, on [http://bugs.sugarlabs.org bugs.sugarlabs.org] on mailing lists, partially because of lack of Internet connection (2.1) and partially because these resources are too technical (2.2). Besides, there is no convenient and direct (between users and Activity developers) ways to share technical information when Sugar Activity fails.
	## In comparing to (1.5). ~~For sure, educational support exists. But due to very simple~~ Sugar ~~desktop environment~~ functionality~~, it~~ is ~~too basic~~, i.e., ~~download {{Code\|~~.~~xol}} bundle or open the Browse~~ to ~~get access to the content in the network~~.		## In comparing to (1.5). Sugar Shell's functionality is pretty simple in case of providing support for educational related workflows that might happen, e.g., during the class time. There should plenty of ways to make Sugar Learning environment more useful.
	# ''What's new in your approach and why do you think it will be successful?''		# ''What's new in your approach and why do you think it will be successful?''
	## To solve (2.1) and accomplish (1.1). Sugar Network is not intended to replace all existing (2.1) resources, but rather get singular and unified access point to the same resources from the Sugar Network Browser application that is well integrated to the Sugar desktop environment. It should be friendly to students, i.e., instead of going to [http://bugs.sugarlabs.org bugs.sugarlabs.org], creating an account there, create new ticket with possibility to set bunch of technical fields (like targeting release, OS, etc), a student needs to open Sugar Network Browser, find the targeting activity and type the problem (just the text). Or, to launch Sugar Activity, a student should not browse [[Activity Library]], school server, or Wikis, just click it in Sugar Network Browser.		## To solve (2.1) and accomplish (1.1). Sugar Network is not intended to replace all existing (2.1) resources, but rather get singular and unified access point to the same resources from the Sugar Network Browser application that is well integrated to the Sugar desktop environment. It should be friendly to students, i.e., instead of going to [http://bugs.sugarlabs.org bugs.sugarlabs.org], creating an account there, create new ticket with possibility to set bunch of technical fields (like targeting release, OS, etc), a student needs to open Sugar Network Browser, find the targeting activity and type the problem (just the text). Or, to launch Sugar Activity, a student should not browse [[Activity Library]], school server, or Wikis, just click it in Sugar Network Browser.

Alsroot at 18:23, 17 January 2012

2012-01-17T18:23:51Z

Alsroot at 17:51, 17 January 2012

2012-01-17T17:51:29Z

← Older revision		Revision as of 13:51, 17 January 2012
Line 24:		Line 24:
	## Local deployment supporters		## Local deployment supporters
	## Software developers		## Software developers
	~~## Sugar community~~
	# ''If you're successful, what difference will it make?''		# ''If you're successful, what difference will it make?''
			## For students (4.1). The central place to get convenient access to various content (Sugar Activities, Journal objects, Wiki articles). The content might be mostly the same that might be found in the Internet but on different resources. The additional (for online case) and convenient tool to support social activities (regarding Sugar Network objects) to share ideas and complains regarding particular resources to collaborate with other people.
			## For teachers (4.2). Sugar Network is the right place to share various methodical materials and have educators only level discussions. Potentially, Sugar Network might be well tuned regarding educational process.
			## For local deployment supporters (4.3). More convenient way to provide remote support for people at schools, especially for offline schools.
			## For software developers (4.4). Developers will get a chance to have direct feedback from the field, including auto generated reports about software fails.
	# ''What are the risks and the payoffs?''		# ''What are the risks and the payoffs?''
	#: The idea might be evolved during the process of implementation. But for sure, there are a problem (2) and it should be solved. Any doing in this direction should be useful, even if original intention will be shifted.		#: The idea might be evolved during the process of implementation. But for sure, there are a problem (2) and it should be solved. Any doing in this direction should be useful, even if original intention will be shifted.

← Older revision		Revision as of 11:39, 20 January 2012
Line 4:		Line 4:
	## Convenient, unified, and well integrated to the Sugar desktop environment access to various Sugar, and, education in general, content. Such as Sugar Activities, content created by Sugar Activities, documentation and educational materials, etc.		## Convenient, unified, and well integrated to the Sugar desktop environment access to various Sugar, and, education in general, content. Such as Sugar Activities, content created by Sugar Activities, documentation and educational materials, etc.
	## Provide this access (1.1), but with different latencies, on several [[Wikipedia:Computer_network\|Network]] levels, i.e., [[Wikipedia:Online\|online]] access to the Internet, access to the school network with possible (but not mandatory) access to the Internet, [[Wikipedia:Offline\|offline]] case when Sugar Network participant has only his computer.		## Provide this access (1.1), but with different latencies, on several [[Wikipedia:Computer_network\|Network]] levels, i.e., [[Wikipedia:Online\|online]] access to the Internet, access to the school network with possible (but not mandatory) access to the Internet, [[Wikipedia:Offline\|offline]] case when Sugar Network participant has only his computer.
	## Supplement this access (1.1) on all levels (1.2) with [[Wikipedia:Social_network\|social network]] features when Sugar Network participants can share ~~their creatures~~, questions, ideas, problems and opinions within the Sugar Network.		## Supplement this access (1.1) on all levels (1.2) with [[Wikipedia:Social_network\|social network]] features when Sugar Network participants can share content created by themselves, questions, ideas, problems and opinions within the Sugar Network.
	## Using social functionality (1.3) and integrated to the Sugar Network automatic bug report functionality, it will be possible to provide technical support, e.g., from Sugar Activity authors or from Sugar deployment personal.		## Using social functionality (1.3) and integrated to the Sugar Network automatic bug report functionality, it will be possible to provide technical support, e.g., from Sugar Activity authors or from Sugar deployment personal.
	## The last, but not the least. The entire Sugar Network should be well integrated to the educational process, e.g., support different scope workflows, such as school, class time, personal home work.		## The last, but not the least. The entire Sugar Network should be well integrated to the educational process, e.g., support different scope workflows, such as school, class time, personal home work.
Line 10:		Line 10:
	## In comparing to (1.1). There are several resources for Sugar, and, educational in general, content. Such as [[Activity Library]], several methods to get to get Sugar Activities that are integrated to the Sugar Shell, various Wikis, services placed on school servers (starting from Moodle and ending with ure HTML pages that serves Sugar Activity bundles. The users experience is too different from content source to source. Besides, these sources might be not students friendly, e.g., it will require creating an account (with specifying email address), be too technical like sugar mailing lists. In most cases they are poorly integrated to the Sugar desktop environment.		## In comparing to (1.1). There are several resources for Sugar, and, educational in general, content. Such as [[Activity Library]], several methods to get to get Sugar Activities that are integrated to the Sugar Shell, various Wikis, services placed on school servers (starting from Moodle and ending with ure HTML pages that serves Sugar Activity bundles. The users experience is too different from content source to source. Besides, these sources might be not students friendly, e.g., it will require creating an account (with specifying email address), be too technical like sugar mailing lists. In most cases they are poorly integrated to the Sugar desktop environment.
	## In comparing to (1.2). The richest resources are all located in the Internet, but Internet access is not chip and wide for all Sugar deployments, and might be simply absent. If some resources are accessible on school servers, it might be not integrated to the global Sugar community. To support [[Wikipedia:Offline\|offline]] workflow, students need to routines work, e.g., copying Sugar Activity bundles from the Internet or school's server to the Journal. And as (2.1) points, on all levels the users experience is too different.		## In comparing to (1.2). The richest resources are all located in the Internet, but Internet access is not chip and wide for all Sugar deployments, and might be simply absent. If some resources are accessible on school servers, it might be not integrated to the global Sugar community. To support [[Wikipedia:Offline\|offline]] workflow, students need to routines work, e.g., copying Sugar Activity bundles from the Internet or school's server to the Journal. And as (2.1) points, on all levels the users experience is too different.
	## In comparing to (1.3). The existing ways to share content within the Sugar community is either ~~imited~~ or too basic. There is the [[Activity Library]], but people can post only reviews. To report a bug they need to login to [http://bugs.sugarlabs.org bugs.sugarlabs.org]. To ask question or share ideas, they need to subscribe to mailing lists. All these resources are located in the Internet (2.2). And mostly not ~~users~~ friendly for students at all (2.1). Besides, some resources located on school servers might not allow any collaboration at all, i.e., pure HTML page to download Sugar Activity bundles. And as (2.1) says, the users experience is too different from resource to resource.		## In comparing to (1.3). The existing ways to share content within the Sugar community is either limitted or too basic. There is the [[Activity Library]], but people can post only reviews (not questions, ideas or problems). To report a bug they need to login to [http://bugs.sugarlabs.org bugs.sugarlabs.org]. To ask question or share ideas, they need to subscribe to mailing lists. All these resources are located in the Internet (2.2). And mostly not friendly for students at all (2.1). Besides, some resources located on school servers might not allow any collaboration and content uploading at all, i.e., pure HTML page to download Sugar Activity bundles. And as (2.1) says, the users experience is too different from resource to resource.
	## In comparing to (1.4). It is mostly impossible to get feedback from students, that use Sugar Activities in the field, on [http://bugs.sugarlabs.org bugs.sugarlabs.org] on mailing lists, partially because of lack of Internet connection (2.1) and partially because these resources are too technical (2.2). Besides, there is no convenient and direct (between users and Activity developers) ways to share technical information when Sugar Activity fails.		## In comparing to (1.4). It is mostly impossible to get feedback from students, that use Sugar Activities in the field, on [http://bugs.sugarlabs.org bugs.sugarlabs.org] on mailing lists, partially because of lack of Internet connection (2.1) and partially because these resources are too technical (2.2). Besides, there is no convenient and direct (between users and Activity developers) ways to share technical information when Sugar Activity fails.
	## In comparing to (1.5). Sugar Shell's functionality is pretty simple in case of providing support for educational related workflows that might happen, e.g., during the class time. There should plenty of ways to make Sugar Learning environment more useful.		## In comparing to (1.5). Sugar Shell's functionality is pretty simple in case of providing support for educational related workflows that might happen, e.g., during the class time. There should plenty of ways to make Sugar Learning environment more useful.
Line 16:		Line 16:
	## To solve (2.1) and accomplish (1.1). Sugar Network is not intended to replace all existing (2.1) resources, but rather get singular and unified access point to the same resources from the Sugar Network Browser application that is well integrated to the Sugar desktop environment. It should be friendly to students, i.e., instead of going to [http://bugs.sugarlabs.org bugs.sugarlabs.org], creating an account there, create new ticket with possibility to set bunch of technical fields (like targeting release, OS, etc), a student needs to open Sugar Network Browser, find the targeting activity and type the problem (just the text). Or, to launch Sugar Activity, a student should not browse [[Activity Library]], school server, or Wikis, just click it in Sugar Network Browser.		## To solve (2.1) and accomplish (1.1). Sugar Network is not intended to replace all existing (2.1) resources, but rather get singular and unified access point to the same resources from the Sugar Network Browser application that is well integrated to the Sugar desktop environment. It should be friendly to students, i.e., instead of going to [http://bugs.sugarlabs.org bugs.sugarlabs.org], creating an account there, create new ticket with possibility to set bunch of technical fields (like targeting release, OS, etc), a student needs to open Sugar Network Browser, find the targeting activity and type the problem (just the text). Or, to launch Sugar Activity, a student should not browse [[Activity Library]], school server, or Wikis, just click it in Sugar Network Browser.
	## To solve (2.2) and accomplish (1.2). On all network accessibility levels (online, school, offline), people use the same Sugar Network Browser (3.1). The only differences are: being online, people see the full picture; being connected to school network, people see the picture that is a snapshot of the full picture (that is being updated from time to time); being offline, e.g., switching from online of from school network, people see only resources they marked as persistent manually.		## To solve (2.2) and accomplish (1.2). On all network accessibility levels (online, school, offline), people use the same Sugar Network Browser (3.1). The only differences are: being online, people see the full picture; being connected to school network, people see the picture that is a snapshot of the full picture (that is being updated from time to time); being offline, e.g., switching from online of from school network, people see only resources they marked as persistent manually.
	## To solve (2.3) and accomplish (1.3). Still, it is the same Sugar Network Browser (3.1). On all network accessibility (3.2) levels, people can ask ~~question~~, share ~~idea~~, ~~concern~~ about problem, etc. for all accessible resources in their Browser. After increasing network accessibility level, e.g., connecting to the school server after being offline, all new changes will be merged to the ~~new~~ level.		## To solve (2.3) and accomplish (1.3). Still, it is the same Sugar Network Browser (3.1). On all network accessibility (3.2) levels, people can share content created by themselves, ask questions, share ideas, complain about problem, etc. for all accessible resources in their Browser. After increasing network accessibility level, e.g., connecting to the school server after being offline, all new changes will be merged to the upper level.
	## To solve (2.4) and accomplish (1.4). Still, it is the same Sugar Network Browser (3.1). After clicking the Sugar Activity and getting its fail, the error dialog might show the button "Share the report", then, nothing else from user's point of view. Activity developer will get this repost immediately (depending on network accessibility level). Besides, people can ask questions, share ideas, complain about problems, all this information is accessible for developers.		## To solve (2.4) and accomplish (1.4). Still, it is the same Sugar Network Browser (3.1). After clicking the Sugar Activity and getting its fail, the error dialog might show the button "Share the report", then, nothing else from user's point of view. Activity developer will get this repost immediately (depending on network accessibility level). Besides, people can ask questions, share ideas, complain about problems, all this information is accessible for developers.
	## To solve (2.5) and accomplish (1.5). Still, it is the same Sugar Network Browser (3.1). This part is the most non-trivial and not technical. But, it should be possible to support different educational related workflows in the Browser, e.g., during the class time, students migth see only resources that are related to the current subject (when teacher has more powerful view in his Browser).		## To solve (2.5) and accomplish (1.5). Still, it is the same Sugar Network Browser (3.1). This part is the most non-trivial and not technical. But, it should be possible to support different educational related workflows in the Browser, e.g., during the class time, students migth see only resources that are related to the current subject (when teacher has more powerful view in his Browser).

← Older revision		Revision as of 14:23, 17 January 2012
Line 4:		Line 4:
	## Convenient, unified, and well integrated to the Sugar desktop environment access to various Sugar, and, education in general, content. Such as Sugar Activities, content created by Sugar Activities, documentation and educational materials, etc.		## Convenient, unified, and well integrated to the Sugar desktop environment access to various Sugar, and, education in general, content. Such as Sugar Activities, content created by Sugar Activities, documentation and educational materials, etc.
	## Provide this access (1.1), but with different latencies, on several [[Wikipedia:Computer_network\|Network]] levels, i.e., [[Wikipedia:Online\|online]] access to the Internet, access to the school network with possible (but not mandatory) access to the Internet, [[Wikipedia:Offline\|offline]] case when Sugar Network participant has only his computer.		## Provide this access (1.1), but with different latencies, on several [[Wikipedia:Computer_network\|Network]] levels, i.e., [[Wikipedia:Online\|online]] access to the Internet, access to the school network with possible (but not mandatory) access to the Internet, [[Wikipedia:Offline\|offline]] case when Sugar Network participant has only his computer.
	## Supplement this access (1.1) on all levels (1.2) with [[Wikipedia:Social_network\|social network]] features when Sugar Network participants can share their creatures, questions, ideas, problems and opinions ~~withing~~ the Sugar Network.		## Supplement this access (1.1) on all levels (1.2) with [[Wikipedia:Social_network\|social network]] features when Sugar Network participants can share their creatures, questions, ideas, problems and opinions within the Sugar Network.
	## Using social functionality (1.3) and integrated to the Sugar Network automatic bug report functionality, it will be possible to provide technical support, e.g., from Sugar Activity authors or from Sugar deployment personal.		## Using social functionality (1.3) and integrated to the Sugar Network automatic bug report functionality, it will be possible to provide technical support, e.g., from Sugar Activity authors or from Sugar deployment personal.
	## The last, but not the least. The entire Sugar Network should be well integrated to the educational process, e.g., support different scope workflows, such as school, class time, personal home work.		## The last, but not the least. The entire Sugar Network should be well integrated to the educational process, e.g., support different scope workflows, such as school, class time, personal home work.
Line 18:		Line 18:
	## To solve (2.3) and accomplish (1.3). Still, it is the same Sugar Network Browser (3.1). On all network accessibility (3.2) levels, people can ask question, share idea, concern about problem, etc. for all accessible resources in their Browser. After increasing network accessibility level, e.g., connecting to the school server after being offline, all new changes will be merged to the new level.		## To solve (2.3) and accomplish (1.3). Still, it is the same Sugar Network Browser (3.1). On all network accessibility (3.2) levels, people can ask question, share idea, concern about problem, etc. for all accessible resources in their Browser. After increasing network accessibility level, e.g., connecting to the school server after being offline, all new changes will be merged to the new level.
	## To solve (2.4) and accomplish (1.4). Still, it is the same Sugar Network Browser (3.1). After clicking the Sugar Activity and getting its fail, the error dialog might show the button "Share the report", then, nothing else from user's point of view. Activity developer will get this repost immediately (depending on network accessibility level). Besides, people can ask questions, share ideas, complain about problems, all this information is accessible for developers.		## To solve (2.4) and accomplish (1.4). Still, it is the same Sugar Network Browser (3.1). After clicking the Sugar Activity and getting its fail, the error dialog might show the button "Share the report", then, nothing else from user's point of view. Activity developer will get this repost immediately (depending on network accessibility level). Besides, people can ask questions, share ideas, complain about problems, all this information is accessible for developers.
	## To solve (2.5) and accomplish (1.5). Still, it is the same Sugar Network Browser (3.1). This part is the most non-trivial and not technical. But, it should be possible to support different educational related workflows ~~withing~~ the Browser, e.g., during the class time, students migth see only resources that are related to the current subject (when teacher has more powerful view in his Browser).		## To solve (2.5) and accomplish (1.5). Still, it is the same Sugar Network Browser (3.1). This part is the most non-trivial and not technical. But, it should be possible to support different educational related workflows in the Browser, e.g., during the class time, students migth see only resources that are related to the current subject (when teacher has more powerful view in his Browser).
	# ''Who cares?''		# ''Who cares?''
	## Students		## Students
Line 47:		Line 47:
	##* Create a Wiki article;		##* Create a Wiki article;
	##* Post to the Sugar Network a question, idea, problem or review regarding the Sugar Activity, Journal object or Wiki page;		##* Post to the Sugar Network a question, idea, problem or review regarding the Sugar Activity, Journal object or Wiki page;
	##* Sugar Activity, Reports, Journal objects, Wiki and reports, are accessible ~~withing~~ the Sugar Network, school level and the global one;		##* Sugar Activity, Reports, Journal objects, Wiki and reports, are accessible within the Sugar Network, school level and the global one;
	##* Some Activities and Wiki pages, student mark as persistent to work in offline;		##* Some Activities and Wiki pages, student mark as persistent to work in offline;
	##* Being offline at home, he can do the same as he did at school;		##* Being offline at home, he can do the same as he did at school;
	##* After visiting the school, all changes made at home will be automatically merged to the Sugar Network and regular work begins.		##* After visiting the school, all changes made at home will be automatically merged to the Sugar Network and regular work begins.