102
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: + + + + + + + + + + + + + + + + + + Line 8:
Line 26: + Line 15:
Line 34: − + + + + + + Line 26:
Line 50: − + − + − + Line 38:
Line 62: − + Line 47:
Line 71: + + + + + + + + + + + + + Line 74:
Line 111: − + − + + + + + + + + + + Line 129:
Line 175: + + + + + + + Line 140:
Line 193: − + Line 153:
Line 206: − + Line 173:
Line 226: − + Line 180:
Line 233: − + Line 186:
Line 239: − + Line 206:
Line 259: − + Line 221:
Line 274: − + + Line 230:
Line 284: − More info: [https://github.com/llaske/sugarizer/blob/master/README.md Sugarizer README]+ − + + Line 242:
Line 297: − More info: [https://github.com/llaske/sugarizer/blob/master/README.md#server Sugarizer Server documentation], [http://sugarizer.org/apidoc/ Sugarizer Server API]+ − + − + Line 254:
Line 309: − More info: [https://github.com/llaske/sugarizer/blob/master/README.md#create-your-own-activity Create a Sugarizer activity], [http://activities.sugarlabs.org/us/sugar/addon/4034 Moon], [http://activities.sugarlabs.org/us/sugar/addon/4038 Speak], [http://activities.sugarlabs.org/us/sugar/addon/4253 Fototoon]+
no edit summary
'''Students''': See our guide on [[Summer_of_Code#How_to_participate|how to participate in Google Summer of Code]] for more information.
'''Students''': See our guide on [[Summer_of_Code#How_to_participate|how to participate in Google Summer of Code]] for more information.
The Sugar Labs Google Summer of Code 2016 projects/students/mentors:
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Project !! Student !! Mentors !! Proposal !! Blog !! IRC nick
|-
|Font Editor Activity||Yash Agarwal||Dave Crossland, Eli Heuer || [https://sugarlabs.github.io/edit-fonts-activity/refined-proposal] || [http://sugarlabs.github.io/font-editor-activity/] || yagarwal
|-
|Git Backend||Vikram Ahuja||Walter Bender, Tymon Radzik || Pending || [http://vikramahujagsoc.blogspot.com/] || vikram
|-
|Journal Rethink||Abhijit Patel||Walter Bender, Sam Parkinson||[https://www.docdroid.net/hbalTLC/1458885012-journal-rethink-proposal.pdf.html] || [http://abrahmab.github.io/] || AbrahmAB
|-
|Music Widgets||Hemant Kasat||Walter Bender, Devin Ulibarri || Pending || [http://musicblocks.net/2016/06/13/multiple-rhythm-rulers/] || hemant_kasat
|-
|Sugarizer OS||Jeremie Amsellem||Lionel Laské, Michaël Ohayon || Pending || [http://lp1-eu.blogspot.fr/] || lp1
|-
|Sugar on the Ground||Utkarsh Tiwari||Tony Anderson, Sebastian Silva || [http://docdro.id/zx9U1Vd] || [https://iamutkarshtiwari.wordpress.com/about/google-summer-of-code16-with-sugar-labs-2/] || iamutkarshtiwari
|}
== Project candidates ==
== Project candidates ==
;Note 1: Potential mentors, please feel free to add ideas to this list. Also, feel free to add your name to a project you'd be willing to co-mentor.
;Note 1: Potential mentors, please feel free to add ideas to this list. Also, feel free to add your name to a project you'd be willing to co-mentor.
;Note 2: Potential students, more project ideas can be found on our [[Features]] page.
;Note 2: Potential students, more project ideas can be found on our [[Features]] page.
;Note 3: Accepted projects are in <font color="#00bb00">Green</font>
== Sugar Core ==
== Sugar Core ==
! !! Title !! Mentor !! Project
! !! Title !! Mentor !! Project
|-
|-
!valign=top | [[File:Journal-12.jpeg|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" |Journal Rethink ||valign=top width="15%" | Sam Parkinson ||align=left valign=top|
!valign=top | ||valign=top width="15%" style="background:#e3e4e5;" |Internationalization and Localization ||valign=top width="15%" | Chris Leonard ||align=left valign=top|
;Brief explanation: A goal of Sugar Labs is to enable our users to experience Sugar in their own native language. See [[Translation_Proposal#ToDo:|Translation Proposal To Do List]] for details.
;Expected results: Work flow improvements for i18n
;Knowledge prerequisites: Some knowledge of Pootle; some scripting experience; Python
|-
!valign=top | [[File:Journal-12.jpeg|90px|thumb|center]] ||valign=top width="15%" style="background:#00bb00;" |Journal Rethink ||valign=top width="15%" | Sam Parkinson ||align=left valign=top|
;Brief explanation: The Sugar Journal could be rethought to add more emphasis on collaboration, or adding more organisational support for creating "projects" among other things.
;Brief explanation: The Sugar Journal could be rethought to add more emphasis on collaboration, or adding more organisational support for creating "projects" among other things.
;Expected results: Working code for the journal and vague ideas (more concrete than this) defined ahead of time.
;Expected results: Working code for the journal and vague ideas (more concrete than this) defined ahead of time.
|-
|-
!valign=top | [[File:reflect.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" |Reflection Activity||valign=top width="15%" | Sam Parkinson and Walter Bender ||align=left valign=top|
!valign=top | [[File:reflect.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" |Reflect Activity||valign=top width="15%" | Sam Parkinson and Walter Bender ||align=left valign=top|
;Brief explanation: The Sugar Journal is designed to be a place of reflection. We have the basic stub of a reflection activity that attempts to encourage more reflection and as a vehicle for sharing criticism. This idea needs more thought and coding.
;Brief explanation: The Sugar Journal is designed to be a place of reflection. We have the basic stub of a reflection activity that attempts to encourage more reflection and as a vehicle for sharing criticism. This idea needs more thought and coding.
;Expected results: A solid formulation of how the activity will work in the classroom and working code for the Reflection Activity.
;Expected results: A solid formulation of how the activity will work in the classroom and working code for the Reflect Activity.
;Knowledge prerequisite: Strong background in Python and knowledge of Gtk+.
;Knowledge prerequisite: Strong background in Python and knowledge of Gtk+.
|-
|-
!valign=top | [[File:git_logo.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" |Git backend||valign=top width="15%" | Martin Abente Lahaye and Walter Bender ||align=left valign=top|
!valign=top | [[File:git_logo.png|90px|thumb|center]] ||valign=top width="15%" style="background:#00bb00;" |Git backend||valign=top width="15%" | Martin Abente Lahaye and Walter Bender ||align=left valign=top|
;Brief explanation: The Sugar Journal doesn't do a great job of supporting versioning or forking. This project is to build a backend for the Journal that is based on git, which does support versioning and forking. By building on top of a git hosting site we get the added benefit of network access as well.
;Brief explanation: The Sugar Journal doesn't do a great job of supporting versioning or forking. This project is to build a backend for the Journal that is based on git, which does support versioning and forking. By building on top of a git hosting site we get the added benefit of network access as well.
;Expected results: Working code and an integration with Turtle Blocks
;Expected results: Working code and an integration with Turtle Blocks
|-
|-
!valign=top | || valign=top style="background:#e3e4e5;" | Performance tuning on machines with limited memory || valign=top | Samuel Greenfeld and James Cameron||align=left valign=top |
!valign=top | || valign=top style="background:#e3e4e5;" | Performance tuning on machines with limited memory || valign=top | Samuel Greenfeld||align=left valign=top |
;Brief explanation: The newer Sugar builds have performance issues on some old hardware with limited memory. This is keeping some Sugar deployments from upgrading. This project is to look into the performance issues and tune Sugar for low-memory devices.
;Brief explanation: The newer Sugar builds have performance issues on some old hardware with limited memory. This is keeping some Sugar deployments from upgrading. This project is to look into the performance issues and tune Sugar for low-memory devices.
;Expected results: build suitable for running on OLPC XO-1 hardware
;Expected results: build suitable for running on OLPC XO-1 hardware
;Brief explanation: Now that JavaScript has become a first class citizen in the Sugar ecosystem, we must re-design our collaboration model to allow collaboration between web activities regardless of the platform.
;Brief explanation: Now that JavaScript has become a first class citizen in the Sugar ecosystem, we must re-design our collaboration model to allow collaboration between web activities regardless of the platform.
;Knowledge prerequisite: JavaScript, web sockets, web services.
;Knowledge prerequisite: JavaScript, web sockets, web services.
|-
!valign=top | [[File:freedesktop_logo.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" |Make Sugar compliant with Freedesktop standards||valign=top width="15%" | [[User:Sebastian|Sebastian]] ([[User talk:Sebastian|talk]]) 13:50, 10 March 2016 (EST) ||align=left valign=top|
;Brief explanation: Support Freedesktop.Org Desktop Entry specification for launching non-sugar applications, icon standards, etc. Find other ways to make Sugar useful as Linux desktop. Make it easy to run Sugar Activities in regular Linux desktop.
;Expected results: Improved user experience for users of regular Linux apps, merged to Sugar mainline.
;Knowledge prerequisite: Strong background in GTK, Python and GNU/Linux.
|-
!valign=top | [[File:html5_logo.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" |Port Sugar to the Broadwayd HTML5 GTK Backend||valign=top width="15%" | [[User:Sebastian|Sebastian]] ([[User talk:Sebastian|talk]]) 14:09, 10 March 2016 (EST) ||align=left valign=top|
;Brief explanation: Sugar uses GTK3. Recently GTK3 released support for a HTML5 native backend called Broadwayd.
;Expected results: Make it feasible to run Sugar and pure gtk3 activities thru a browser (not Sugarizer). Docker container for Sugar on Broadwayd.
;Knowledge prerequisite: Strong background in GTK, Python and GNU/Linux. Docker.
|}
|}
|-
|-
!valign=top | [[File:Music-Blocks.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" | Music Widgets||valign=top width="15%" | Devin Ulibarri ||align=left valign=top|
!valign=top | [[File:Music-Blocks.png|90px|thumb|center]] ||valign=top width="15%" style="background:#00bb00" | Music Widgets||valign=top width="15%" | Devin Ulibarri ||align=left valign=top|
;Brief explanation: Development four new widgets to improve the possibilities for music
;Brief explanation: Development four new widgets to improve the possibilities for music
learning as well as overall user-experience for Music Blocks. The widgets are 1. Pitch-Staircase 2. Tempo 3. Rhythm Rulers, and 4. Free-Pitch Slider. Widgets will integrate with the current coding environment without disrupting the underlying language in any way (like the current pitch-time matrix).
learning as well as overall user-experience for Music Blocks. The widgets are 1. Pitch-Staircase 2. Tempo 3. Rhythm Rulers, and 4. Free-Pitch Slider. Widgets will integrate with the current coding environment without disrupting the underlying language in any way (like the current pitch-time matrix).
;Expected results: Users will use these to explore musical concepts and generate desired
;Expected results: Users will use these to explore musical concepts and generate desired
blocks from their experiments.
blocks from their experiments.
;Knowledge prerequisite: Strong background in Javascript, Basic knowledge of Music Theory
;Knowledge prerequisite: Strong background in JavaScript, Basic knowledge of Music Theory
and/or physics
and/or physics
|-
!valign=top | || valign=top width = "15%" style="background:#00bb00;" | [[Font Editor|Font Editor Activity]]||valign=top width="15%" | with Dave Crossland || align=left valign=top|
;Brief explanation: Typeface design is a cornerstone of literate cultures, with subliminal power: Typefaces carry the emotions of texts, from formal designs that speak with authority to fun designs that are silly or military or ornate. They are both artistic and functional works, and our ability to share and modify them is important for the same reasons as for software programs. A Sugar font editor activity will empower users to create and modify fonts for their own tastes and needs. Fonts are fun to make, but we need an editor to do it.
;Expected results: Lots of free software Python and JavaScript libraries already exist so this project offers the possibility to make real progress for users this summer.
;Knowledge prerequisite: Strong background in JavaScript or Python
:
:
|}
|}
;Expected Results: a new test suite and scads of documentation.
;Expected Results: a new test suite and scads of documentation.
;Knowledge Prerequisite: A strong background in Python.
;Knowledge Prerequisite: A strong background in Python.
|-
!valign=top | ||valign=top width="15%" style="background:#e3e4e5;" | Redesign and recreate Sugar Labs webappearance ||valign=top width="15%" | Tymon Radzik ||align=left valign=top|
Create new modern and innovative design template for our websites and apply it to all our systems. Consider, how to improve our webappearance. Currently, almost every our website looks different than other and is created in different technology.
;Brief Description: The goal is to create new template to be used to unify view of our websites (main page, Wiki, Planet, Traslation system, ...) and apply it to our systems. It must include storing all code in one place (like in repositories on Github), reducing number of technologies used, improving SEO, considering other solutions to be used instead of obsolete pages and general design.
;Expected Results: new, better webappearance of Sugar Labs, basing on innovative template. All code should be placed in one place on Github.
;Knowledge Prerequisite: Strong skills in HTML5, CSS3, Javascript and other core webtechnologies; experience in creating modern website design.
|}
|}
|-
|-
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" | Sugar Journal save option ||valign=top width="15%" | Tony Anderson ||align=left valign=top|
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width="15%" style="background:#00bb00;" | Sugar Journal save option ||valign=top width="15%" | Tony Anderson ||align=left valign=top|
The Sugar Journal should provide a 'save/save as' interface which should enable a user to choose whether to save the current document when an activity is closed. The interface should require a name change from 'current.activity' to a user supplied name. If the document is derived from one currently saved in the Journal, the user should be allowed to save (overwrite) or save as (create new document) by giving a new name to the document. This could be accomplished by showing a modal dialog at close time requesting the user to supply a name or not save the document. If the document has a user supplied name, the dialog could request the user to save or to provide a new name to create a new document.
The Sugar Journal should provide a 'save/save as' interface which should enable a user to choose whether to save the current document when an activity is closed. The interface should require a name change from 'current.activity' to a user supplied name. If the document is derived from one currently saved in the Journal, the user should be allowed to save (overwrite) or save as (create new document) by giving a new name to the document. This could be accomplished by showing a modal dialog at close time requesting the user to supply a name or not save the document. If the document has a user supplied name, the dialog could request the user to save or to provide a new name to create a new document.
|-
|-
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" | Sugar Journal backup and restore ||valign=top width="15%" | Tony Anderson<br>Ignacio Rodriguez||align=left valign=top|
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width="15%" style="background:#00bb00;" | Sugar Journal backup and restore ||valign=top width="15%" | Tony Anderson ||align=left valign=top|
Sugar provides a method to backup and restore the Journal (one method to a USB key and one method to the school server). The Journal also provides a select box to enable an action to be taken for all selected objects. This mechanism should be sufficient for the USB key case. However, the school server backup currently is based on taking a snapshot of the current Journal state. This means the size of the objects in a user's Journal cannot exceed the available local store on an XO (300MB for an XO-1, 1.9GB for other models). A mechanism is needed to save on the school server all documents created by the user and to restore a selected object to the Journal from the school server. Since many documents may represent library objects (e-books, audio, image or video media), the mechanism should recognize these and not save them as user documents. However, the metadata saved should enable the system to download the library items again as needed (and, as available).
Sugar provides a method to backup and restore the Journal (one method to a USB key and one method to the school server). The Journal also provides a select box to enable an action to be taken for all selected objects. This mechanism should be sufficient for the USB key case. However, the school server backup currently is based on taking a snapshot of the current Journal state. This means the size of the objects in a user's Journal cannot exceed the available local store on an XO (300MB for an XO-1, 1.9GB for other models). A mechanism is needed to save on the school server all documents created by the user and to restore a selected object to the Journal from the school server. Since many documents may represent library objects (e-books, audio, image or video media), the mechanism should recognize these and not save them as user documents. However, the metadata saved should enable the system to download the library items again as needed (and, as available).
;For example: the mechanism may be to upload Journal documents to an OwnCloud repository. The user could then select an item in the OwnCloud repository to be downloaded to the Journal. The user could also share any item in OwnCloud with other user groups or individuals
;For example: the mechanism may be to upload Journal documents to an OwnCloud repository. The user could then select an item in the OwnCloud repository to be downloaded to the Journal. The user could also share any item in OwnCloud with other user groups or individuals
|-
|-
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" | Sugar Journal activity resume feature ||valign=top width="15%" | Tony Anderson ||align=left valign=top|
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width="15%" style="background:#00bb00;" | Sugar Journal activity resume feature ||valign=top width="15%" | Tony Anderson ||align=left valign=top|
In Sugar's Home View, a click on an activity icon by default resumes the most recent instance of the activity. This capability is designed into the Journal and is redundant in the Home View. A Sugar activity is a tool to enable the user to accomplish some task. If that task is not completed, the user can resume it via the Journal. If the tool is to be used on a new task, the user can launch it from the Home View. The current Home View assumes that the intent of the user is to continue the most recent task with that tool.
In Sugar's Home View, a click on an activity icon by default resumes the most recent instance of the activity. This capability is designed into the Journal and is redundant in the Home View. A Sugar activity is a tool to enable the user to accomplish some task. If that task is not completed, the user can resume it via the Journal. If the tool is to be used on a new task, the user can launch it from the Home View. The current Home View assumes that the intent of the user is to continue the most recent task with that tool.
|-
|-
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" | Sugar Activity resume feature ||valign=top width="15%" | Tony Anderson<br>Ignacio Rodriguez ||align=left valign=top|
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" | Sugar Activity resume feature ||valign=top width="15%" | Tony Anderson ||align=left valign=top|
Sugar provides a 'web services' capability. However, these services are only available to an XO which has connection to the internet. This is not useful to a large number of users who do not have internet access. The school server (e.g. XSCE) provides an alternative to the internet for many deployments. This task is to provide a capability on the school server to support some or all of the Sugar web services (e.g. by OwnCloud or ELGG).
Sugar provides a 'web services' capability. However, these services are only available to an XO which has connection to the internet. This is not useful to a large number of users who do not have internet access. The school server (e.g. XSCE) provides an alternative to the internet for many deployments. This task is to provide a capability on the school server to support some or all of the Sugar web services (e.g. by OwnCloud or ELGG).
|-
|-
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" | Sugar offline ||valign=top width="15%" | Tony Anderson ||align=left valign=top|
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width="15%" style="background:#00bb00;" | Sugar offline ||valign=top width="15%" | Tony Anderson ||align=left valign=top|
There are a number of Sugar activities which currently require access to the internet (InfoSlicer, GetBooks). These activities should have an option to function with the school server. For example, GetBooks could access books on the school server and InfoSlicer could create slices from Wikipedia on the school server as Journal objects.
There are a number of Sugar activities which currently require access to the internet (InfoSlicer, GetBooks). These activities should have an option to function with the school server. For example, GetBooks could access books on the school server and InfoSlicer could create slices from Wikipedia on the school server as Journal objects.
|-
|-
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" | One to Many Sugar||valign=top width="15%" | Tony Anderson ||align=left valign=top|
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" | One to Many Sugar||valign=top width="15%" | Tony Anderson ||align=left valign=top|
The OLPC model is that each user has full possession and is the only user of an XO laptop. Therefore, Sugar assumes a 1-1 correspondence between users and XO serial numbers. However, Sugar is being used on other platforms (e.g. SOAS), where there is no obvious equivalent to a serial number. SOAS and James Cameron have created versions of Sugar which do not assume the user is 'olpc', but implement a standard username/password login system. The users storage is allocated to his/her home directory.
The OLPC model is that each user has full possession and is the only user of an XO laptop. Therefore, Sugar assumes a 1-1 correspondence between users and XO serial numbers. However, Sugar is being used on other platforms (e.g. SOAS), where there is no obvious equivalent to a serial number. SOAS and James Cameron [citation?] have created versions of Sugar which do not assume the user is 'olpc', but implement a standard username/password login system. The users storage is allocated to his/her home directory.
This task is to create a Sugar image for the XO which allows for user's to login by username and password. The basic task is to move the Activities folder to a common space so that only one copy is needed per system. This will support deployments where one set of laptops are shared across multiple classes (and users) or where there one laptop is shared between two students - one in a morning shift and the other in an afternoon shift.
This task is to create a Sugar image for the XO which allows for user's to login by username and password. The basic task is to move the Activities folder to a common space so that only one copy is needed per system. This will support deployments where one set of laptops are shared across multiple classes (and users) or where there one laptop is shared between two students - one in a morning shift and the other in an afternoon shift.
|-
|-
!valign=top | [[File:Sugarizer os android.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" | Sugarizer OS ||valign=top width="15%" | Lionel Laské ||align=left valign=top|
!valign=top | [[File:Sugarizer os android.png|90px|thumb|center]] ||valign=top width="15%" style="background:#00bb00;" | Sugarizer OS ||valign=top width="15%" | Lionel Laské and Michaël Ohayon||align=left valign=top|
The goal of this project is to create "Sugarizer OS".
Sugarizer OS is a way to boot directly a device on Sugarizer and allow the user to use both Sugarizer activities and system native applications. Sugarizer OS is not an OS but a way to propose a full Sugar experience on a non-Sugar device.
Sugarizer OS is a way to boot directly a device on Sugarizer and allow the user to use both Sugarizer activities and system native applications. Sugarizer OS is not an OS but a way to propose a full Sugar experience on a non-Sugar device.
Prerequisite: Android, Java, HTML5/JavaScript.
Prerequisite: Android, Java, HTML5/JavaScript.
How to start: Clone the [https://github.com/llaske/sugarizer Sugarizer repository], then create your own APK following instructions [https://github.com/llaske/sugarizer/blob/master/README.md#build-client-for-android-or-ios here]. Think about how to adapt this APK to transform it into an Android launcher.
|-
|-
!valign=top | [[File:Dashboard server.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" | Sugarizer Server Dashboard ||valign=top width="15%" | Lionel Laské ||align=left valign=top|
!valign=top | [[File:Dashboard server.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" | Sugarizer Server Dashboard ||valign=top width="15%" | Lionel Laské and Michaël Ohayon ||align=left valign=top|
The goal of this project is to create the "Sugarizer Server Dashboard".
Sugarizer Server Dashboard is a web admin console for Sugarizer Server. The Dashboard will allow to manage and analyze all activity on a Sugarizer Server. Dashboard features will include:
Sugarizer Server Dashboard is a web admin console for Sugarizer Server. The Dashboard will allow to manage and analyze all activity on a Sugarizer Server. Dashboard features will include:
* Users: how many users has been registered on the server, how many users currently connected, top users on the server, last users connection, create/edit/remove an user.
* Users: how many users has been registered on the server, how many users currently connected, top users on the server, last users connection, create/edit/remove an user.
Technology to use: HTML5/JavaScript, bootstrap, node.js, MongoDB
Technology to use: HTML5/JavaScript, bootstrap, node.js, MongoDB
How to start: Clone the [https://github.com/llaske/sugarizer Sugarizer repository], then install Sugarizer server using instructions [https://github.com/llaske/sugarizer/blob/master/README.md#server here], finally explore the [http://sugarizer.org/apidoc/ Sugarizer Server API] and think about way to implement dashboard features.
|-
|-
!valign=top | [[File:Fototoon-moon-speak.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" | Sugarizer Activity Set ||valign=top width="15%" | Lionel Laské ||align=left valign=top|
!valign=top | [[File:Fototoon-moon-speak.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" | Sugarizer Activity Set ||valign=top width="15%" | Lionel Laské and Michaël Ohayon ||align=left valign=top|
The objective of this project is to port some famous Sugar activities into HTML5/JavaScript Sugar Web activities that will be include into the Sugarizer Package. Three activities will be ported:
The goal of this project is to port some famous Sugar activities into HTML5/JavaScript Sugar Web activities that will be include into the Sugarizer Package. Three activities will be ported:
* Moon: Moon is a Moon phase viewer, includes Lunar phase information and eclipse data.
* Moon: Moon is a Moon phase viewer, includes Lunar phase information and eclipse data.
* Speak: Speak is a talking face. Anything you type will be spoken aloud using the speech synthesizer, espeak.
* Speak: Speak is a talking face. Anything you type will be spoken aloud using the speech synthesizer, espeak.
Technology to use: HTML5/JavaScript
Technology to use: HTML5/JavaScript
How to start: Download and install Sugar like explain [https://wiki.sugarlabs.org/go/Downloads here] and install the existing version of activities to port: [http://activities.sugarlabs.org/us/sugar/addon/4034 Moon], [http://activities.sugarlabs.org/us/sugar/addon/4038 Speak], [http://activities.sugarlabs.org/us/sugar/addon/4253 Fototoon]. Clone the [https://github.com/llaske/sugarizer Sugarizer repository], then create an empty Sugarizer activity following instructions [https://github.com/llaske/sugarizer/blob/master/README.md#create-your-own-activity here]. Think about how to reproduce features of existing activities.
|}
|}