Changes

## 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?''