Changes

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