Changes

## 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.