Changes

===Me and the community===

===Me and the community===

* If your project is successfully completed, what will its impact be on the Sugar Labs

* If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.

community? Give 3 answers, each 1-3 paragraphs in length. The first one should be

* Success of this project will help make Sugar more fun and accessible. It’s often noticed that Software Centers help make a platform. Some notable examples include Android and Ubuntu. Making more third party activities available via ASLO would ensure that Sugar reaches both new users and developers. It will also ensure that many developers (not necessarily Sugar members) can reach children and help create tools for them, which would help them learn new and interesting things

yours. The other two should be answers from members of the Sugar Labs community, at

;Walter Bender (Quoting email conversation): Most notably, the notification system is really broken. No indication by email that there are new activities or updates to review. Otherwise, this looks great.

least one of whom should be a Sugar Labs GSoC mentor. Provide email contact

;Tony Anderson (Quoting email conversation): The ASLO site is in desparate need of work. At the moment I am trying to find out which of the activities actually work in the current release of Sugar. The library currently has about 600 activities. A Sugar activity is intended to be self-contained (any dependencies not satisfied by Sugar are to be incorporated in the bundle). Naturally, an activity should work on any Sugar. However, this situation is becoming very complicated. First, two of the XO models (1 and 1.5) have Intel 32 bit architecture processors. The others (1.75 and 4) have Arm processors. Some of the activities incorporate binary modules which limit their use. The Sugar community wishes to support Sugar on a range of platforms. For mobile devices, Lionel Laske is developing Sugarizer. While traditional activities were implemented in Python (with some binary exceptions using Java or C), Sugarizer activities are written in Javascript (HTML5 and CSS). Naturally a trend in modern computers is to 64 bit architecture (AMD 64).

information for non-GSoC mentors.

* Success of this project will help make Sugar more fun and accessible. It’s often noticed

that Software Centers help make a platform. Some notable examples include Android

and Ubuntu. Making more third party activities available via ASLO would ensure that

Sugar reaches both new users and developers. It will also ensure that many developers

(not necessarily Sugar members) can reach children and help create tools for them,

which would help them learn new and interesting things

;Walter Bender (Quoting email conversation): Most notably, the notification system is really broken. No indication by email that

there are new activities or updates to review. Otherwise, this looks great.

;Tony Anderson (Quoting email conversation): The ASLO site is in desparate need of work. At the moment I am trying to find out

which of the activities actually work in the current release of Sugar. The library currently has

about 600 activities. A Sugar activity is intended to be self-contained (any dependencies not

satisfied by Sugar are to be incorporated in the bundle). Naturally, an activity should work on

any Sugar. However, this situation is becoming very complicated. First, two of the XO models

(1 and 1.5) have Intel 32 bit architecture processors. The others (1.75 and 4) have Arm

processors. Some of the activities incorporate binary modules which limit their use. The Sugar

community wishes to support Sugar on a range of platforms. For mobile devices, Lionel Laske

is developing Sugarizer. While traditional activities were implemented in Python (with some

binary exceptions using Java or C), Sugarizer activities are written in Javascript (HTML5 and

CSS). Naturally a trend in modern computers is to 64 bit architecture (AMD 64).

What will you do if you get stuck on your project and your mentor isn't around?

What will you do if you get stuck on your project and your mentor isn't around?

* There are lots of information available. People on IRC and the dev mailing list seems

* There are lots of information available. People on IRC and the dev mailing list seems friendly and helpful, also my experience with stackoverflow has been nice.

friendly and helpful, also my experience with stackoverflow has been nice.

How do you propose you will be keeping the community informed of your progress and

How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?

any problems or questions you might have over the course of the project?

* Via blogs, mailing lists and IRC. This also helps others suggest and review my work :)

* Via blogs, mailing lists and IRC. This also helps others suggest and review my work :)