Changes

;Brief explanation: There are many reasons to port Sugar to Python 3, not the least being its support for internationalization (unicode) is greatly improved over Python 2 (Very important as we have users in >100 languages). There is a good discussion of strategies [http://docs.python.org/3/howto/pyporting.html here]. The first task will be to work with the core developer team to decide on a strategy: writing Python 2/3 compatible source or a pure port. Once that decision is made, the remainder of the work will be to do the port itself. Developing a robust test suite is a must.

;Brief explanation: There are many reasons to port Sugar to Python 3, not the least being its support for internationalization (unicode) is greatly improved over Python 2 (Very important as we have users in >100 languages). There is a good discussion of strategies [http://docs.python.org/3/howto/pyporting.html here]. The first task will be to work with the core developer team to decide on a strategy: writing Python 2/3 compatible source or a pure port. Once that decision is made, the remainder of the work will be to do the port itself. Developing a robust test suite is a must.

;Expected results: Support for Python 3 in Sugar Core and a Porting Guide for Sugar Activities.

;Expected results: Support for Python 3 in Sugar Core and a Porting Guide for Sugar Activities.

;Knowledge Prerequisite: Strong background in Python

;Knowledge prerequisite: Strong background in Python

|-

|-

!valign=top | [[File:python-logo.gif|90px|thumb|left]] ||valign=top width="15%" |Activity Unit Tests||valign=top width="15%" | Walter Bender and Daniel Narvaez||align=left valign=top|

!valign=top | [[File:python-logo.gif|90px|thumb|left]] ||valign=top width="15%" |Activity Unit Tests||valign=top width="15%" | Walter Bender and Daniel Narvaez||align=left valign=top|

;Brief explanation: While we have been vigilant about developing tests for most of Sugar core, we have only just begun to scratch the surface regarding test suites for Sugar activities. This project is to develop unit and UI test suites for all of the [http://download.sugarlabs.org/sources/sucrose/fructose/ "Fructose"] activities – those activities that are shipped as part of every Sugar distribution.

;Brief explanation: While we have been vigilant about developing tests for most of Sugar core, we have only just begun to scratch the surface regarding test suites for Sugar activities. This project is to develop unit and UI test suites for all of the [http://download.sugarlabs.org/sources/sucrose/fructose/ "Fructose"] activities – those activities that are shipped as part of every Sugar distribution.

;Expected results: A suite of unit and UI tests for the Fructose Activities and a Testing Guide for Sugar Activities.

;Expected results: A suite of unit and UI tests for the Fructose Activities and a Testing Guide for Sugar Activities.

;Knowledge Prerequisite: Strong background in Python, GTK3

;Knowledge prerequisite: Strong background in Python, GTK3

|-

|-

!valign=top | [[File:JS-logo.png|90px|thumb|left]] || valign=top |JavaScript Collaboration for Sugar || valign=top | Manuel Quiñones ||align=left valign=top|

!valign=top | [[File:JS-logo.png|90px|thumb|left]] || valign=top |JavaScript Collaboration for Sugar || valign=top | Manuel Quiñones ||align=left valign=top|

;Brief explanation: Sugar has promoted JavaScript/HTML5 to be a first-class development language, on par with Python. Lots of work to do to make this ready for prime time. Specific to this project is the development of a collaboration model that includes both the mechanisms for identifying potential collaborators and the mechanisms for sharing between activities. The first step is to agree upon a collaboration strategy with the developer team; then implement that strategy.

;Brief explanation: Sugar has promoted JavaScript/HTML5 to be a first-class development language, on par with Python. Lots of work to do to make this ready for prime time. Specific to this project is the development of a collaboration model that includes both the mechanisms for identifying potential collaborators and the mechanisms for sharing between activities. The first step is to agree upon a collaboration strategy with the developer team; then implement that strategy.

;Expected results: Rich, intuitive collaboration between JavaScript Activities and an update Guide for Developing Sugar Activities in JavaScript.

;Expected results: Rich, intuitive collaboration between JavaScript Activities and an update Guide for Developing Sugar Activities in JavaScript.

;Knowledge Prerequisite: Strong background in JavaScript

;Knowledge prerequisite: Strong background in JavaScript

|-

|-

!valign=top | [[File:Cordova_sugar.png|90px|left|thumb]] || valign=top | Cordova/PhoneGap container for Sugar || valign=top | Lionel Laské ||align=left valign=top |

!valign=top | [[File:Cordova_sugar.png|90px|left|thumb]] || valign=top | Cordova/PhoneGap container for Sugar || valign=top | Lionel Laské ||align=left valign=top |

;Brief explanation: The idea is to allow Sugar Web Activities to use device dependent features. In this objective, the project will be to transform Sugar into a Cordova/PhoneGap container and to implement major PhoneGap features. Shortly, the project is to add Sugar as new supported platform for Cordova/PhoneGap. Lists of Sugar features that could be exposed to Sugar Web Activities using Cordova/PhoneGap will be: Camera, Audio/Video capture, Accelerometer, Connection, Events, File, Globalization, Media. During the project, the student will also have to demonstrate its work by writing some sample activities using device features. Examples of activities include a Record-like activity or a Level-Tool-like activity.

;Brief explanation: The idea is to allow Sugar Web Activities to use device dependent features. In this objective, the project will be to transform Sugar into a Cordova/PhoneGap container and to implement major PhoneGap features. Shortly, the project is to add Sugar as new supported platform for Cordova/PhoneGap. Lists of Sugar features that could be exposed to Sugar Web Activities using Cordova/PhoneGap will be: Camera, Audio/Video capture, Accelerometer, Connection, Events, File, Globalization, Media. During the project, the student will also have to demonstrate its work by writing some sample activities using device features. Examples of activities include a Record-like activity or a Level-Tool-like activity.

;Expected results: Rich media and sensor support for JavaScript Activities and an update to the Guide for Developing Sugar Activities in JavaScript to reflect the new APIs.

;Expected results: Rich media and sensor support for JavaScript Activities and an update to the Guide for Developing Sugar Activities in JavaScript to reflect the new APIs.

;Knowledge Prerequisite: Strong background in JavaScript

;Knowledge prerequisite: Strong background in JavaScript

|-

|-

!valign=top | [[File:Microphone.svg|90px|left|thumb]] || valign=top | Voice Interface || valign=top | Martin Abente Lahaye ||align=left valign=top|

!valign=top | [[File:Microphone.svg|90px|left|thumb]] || valign=top | Voice Interface || valign=top | Martin Abente Lahaye ||align=left valign=top|

* define a general architecture that will allow us to provide high-level speech-recognition functionality to the Sugar core and activities (i.e., exposing this engine as a DBus service);

* define a general architecture that will allow us to provide high-level speech-recognition functionality to the Sugar core and activities (i.e., exposing this engine as a DBus service);

* finding acceptable solutions that will allow us to add new content and being able to handle different languages.

* finding acceptable solutions that will allow us to add new content and being able to handle different languages.

;Knowledge Prerequisite: Strong background in Python; some experience with either PocketSphinx or Voxforge

;Knowledge prerequisite: Strong background in Python; some experience with either PocketSphinx or Voxforge

|-

|-

!valign=top | [[File:Headwand.jpg|90px|left|thumb]] || valign=top | Assistive Interface || valign=top | Andres Aguirre ||align=left valign=top |

!valign=top | [[File:Headwand.jpg|90px|left|thumb]] || valign=top | Assistive Interface || valign=top | Andres Aguirre ||align=left valign=top |

;Brief explanation: Alternative input devices allow individuals to control their computers through means other than a standard keyboard or pointing device. Examples include smaller or larger keyboards, eye-gaze pointing devices, and sip-and-puff systems controlled by breathing. Using a base sensor package, the goal of this project is to provide an alternative physical-sensor interface to the Sugar desktop for people with limited motor control. The project will require an intervention into both the Sugar toolkit and Sugar core to ensure that the necessary hooks for ATSPI. The first task will be to survey the Sugar suite to find holes in the UI; the second task is to develop a work plan in conjunction with the Sugar developer community; the third task is to implement that plan; finally, arrange with the mentor to deploy the results with our target audience for feedback.

;Brief explanation: Alternative input devices allow individuals to control their computers through means other than a standard keyboard or pointing device. Examples include smaller or larger keyboards, eye-gaze pointing devices, and sip-and-puff systems controlled by breathing. Using a base sensor package, the goal of this project is to provide an alternative physical-sensor interface to the Sugar desktop for people with limited motor control. The project will require an intervention into both the Sugar toolkit and Sugar core to ensure that the necessary hooks for ATSPI. The first task will be to survey the Sugar suite to find holes in the UI; the second task is to develop a work plan in conjunction with the Sugar developer community; the third task is to implement that plan; finally, arrange with the mentor to deploy the results with our target audience for feedback.

;Expected results: Expanded coverage of ATSPI throughout Sugar Core; a working prototype that can be tested in the field; an Assistive Technology Guide for Sugar Activity Developers

;Expected results: Expanded coverage of ATSPI throughout Sugar Core; a working prototype that can be tested in the field; an Assistive Technology Guide for Sugar Activity Developers

;Knowledge Prerequisite: Strong background in Python, GTK3, and Atspi; some electronics background would also be useful.

;Knowledge prerequisite: Strong background in Python, GTK3, and Atspi; some electronics background would also be useful.

|}

|}