Sugar Labs - User contributions [en]

Summer of Code/2017

2017-01-29T13:35:38Z

TymonR: added myself to mentor list

== Project Ideas ==

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! !! Title !! Mentor !! Project

|-
!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 and JavaScript

|-
!valign=top | ||valign=top width="15%" style="background:#e3e4e5;" |New backend server for Turtle Blocks and Music Blocks ||valign=top width="15%" | Walter Bender Vikram Ahuja Ignacio Rodriguez ||align=left valign=top|
;Brief explanation: Last year we sponsored [http://vikramahujagsoc.blogspot.com/ an exploration] of using a git-like back end for projects so that they could be cloned, forked, etc. This summer we would like to implement and deploy this new approach.
;Expected results: Deployment of "git" back end.
;Knowledge prerequisites: Knowledge of Git, JavaScript, server-side skills

|-
!valign=top | ||valign=top width="15%" style="background:#e3e4e5;" |Going beyond Equal Temperament in Music Blocks ||valign=top width="15%" | Walter Bender Devin Ulibarri||align=left valign=top|
;Brief explanation: Most modern music systems are designed around [https://en.wikipedia.org/wiki/Equal_temperament equal temperament]. But there are many ways to [https://en.wikipedia.org/wiki/Musical_temperament chose and tune notes] in a musical system that offer different expressive characteristics.
;Expected results: Extend Music Blocks such that different approaches to temperament are available to the user.
;Knowledge prerequisites: Knowledge of JavaScript, music theory
|-
!
!Giving Sugar Labs website a new Look
!Ignacio Rodriguez
Samson Goddy

Dave Crossland

Walter Bender

Tymon Radzik
!Brief explanation
Sugar Labs tend to give it [https://github.com/sugarlabs/www-sugarlabs homepage] a new look, with the goal to attract make it more attracting and making it more easier for strangers to explore.

See link to get more information concerning the [https://github.com/sugarlabs/www-sugarlabs/blob/master/STRUCTURE.md proposed homepage]

Expected results

Here's a list of organizations that might be considered peers with Sugar Labs. Comparing their websites with ours may give us ideas for how we can improve.
* <nowiki>https://learningequality.org</nowiki>
* <nowiki>http://haxe.org</nowiki>

Knowledge prerequisites

JavaScript, HTML & CSS, Ruby, JQuery
|}

Google Code In 2015

2016-12-30T00:49:43Z

TymonR: /* Mentors */ - for the history

<noinclude>[[Category:Trac Reference]][[Category:Idea]]
[[Category: GCI2015]]</noinclude>

[[File:Gci-sugarlabs-2015.png]]

This is the project page for the Sugar Labs application to [http://www.google-melange.com/gci/homepage/google/gci2015 Google Code In 2015]. Sugar Labs community members: please feel free to add tasks below. We'll do an edit before final applications are due the first week of November 2015.

== Message to potential participants ==

It is important that you obtain permission of your parents.

Es importante que obtengas el permiso de tus padres para participar.

https://developers.google.com/open-source/gci/resources/contest-rules

Please see the Contest Rules for Eligibility and Registration process.

https://developers.google.com/open-source/gci/resources/contest-rules

'''Details regarding the required forms and paperwork are here: [[Google Code In 2015/Participate#Students]].'''

Also, you will likely need to set up the Sugar development environment. See http://developer.sugarlabs.org/dev-environment.md.html for details. Further information about contributing to the project can be found here: http://developer.sugarlabs.org/

Please don't hesitate to ask questions on our irc channel (#sugar on irc.freenode.net) or on the sugar-devel list: sugar-devel AT lists.sugarlabs DOT org

== Why we are participating ==

Sugar is written and maintained by volunteers, who range from seasoned professionals to children as young as 12-years of age. Children who have grown up with Sugar have transitioned from Sugar users to Sugar App developers to Sugar maintainers. They hang out on IRC with the global Sugar developer community and are full-fledged members of the Sugar development team. It is this latter group of children we hope will participate in and benefit from Google Code-in. Specifically we want to re-enforce the message that Sugar belongs to its users and that they have both ownership and the responsibility that ownership implies. Just as learning is not something done to you, but something you do, learning with Sugar ultimately means participating in the Sugar development process. At Sugar Labs, we are trying to bring the culture of Free Software into the culture of school. So the Code-in is not just an opportunity for us to get some tasks accomplished, it is quintessential to our overall mission.

== Some background from GCI ==

[See https://developers.google.com/open-source/gci/resources/getting-started]

===Open Source Fundamentals ===

You can contribute without being a coder!
You do not have to be a coder to contribute to open source. There are many different skill sets needed to help an open source community thrive:
;Documentation: If you are a good writer and enjoy attention to detail then you might want to contribute by writing or editing documentation. Documentation is a huge part of a successful open source project. Organizations need documentation to help attract new contributors as it helps them see what the codebase looks like and where things are and what the plan is for the project.
;Research: An organization may need help crunching numbers or sorting through pages of documents to better understand what the users want or need. There are many different types of tasks that students could work on that are very important to the health of the project.
;Outreach: If you have an outgoing personality and like being around and talking to people, take a look at the outreach tasks. Outreach tasks often include hosting meetups in your local community or creating a plan on how people around the globe can host a meetup about the project in their local communities.
;Training: You could create a YouTube video discussing a new feature of the project or maybe some basics on what the project does so people who haven’t heard about it can understand the project and get involved.
;User Interface: User interface can include many types of tasks including designing new aspects of a webpage or creating a new logo for the project. It may also include various accessibility opportunities to help make the project easier for people who are blind.
;Other: If you have an idea that may help an organization, reach out to them and let them know! Sometimes the best task is one that the organization hasn’t even considered yet.
=== Collaboration===
Open source is not just about coding but working with other people to find the best solution. Being a part of the community is an essential part of success in Google Code-in. Mentors tell us every year that their best students were the ones who worked hard on their projects but also participated on IRC and helped answer questions other students had. Collaborate with the community and mentors on the #sugar channel in the irc.freenode.net network.

=== Quality over Quantity ===

It’s not about being the student who completes the most tasks, that only gets you to the top 10 to be reviewed, it doesn’t mean you will be a grand prize winner. We have had quite a few students who completed the most tasks for their organization yet were not named as Grand Prize Winners because they did everything solo and didn’t get involved in the community or think about the health of the project as a whole, they just kept completing task after task like a machine. If you actively participate in the community then you not only feel the camaraderie that comes with working as a team but you become committed to making the project better for everyone.

== Some basics about Sugar Labs ==

For some basics about the project, see [http://people.sugarlabs.org/walter/docs/Learning-to-Change-the-World-Chapter-4.pdf Chapter 4 of Learning to Change the World].

=== Getting started with coding ===

Sugar development is in either Python or Javascript.

* You will need knowledge of Python and GTK (See http://python-gtk-3-tutorial.readthedocs.org/en/latest/);
* or Javascript/HTML5;
* and then the basic of Sugar development (See http://www.flossmanuals.net/make-your-own-sugar-activities/);
* and to have a Sugar development environment running (See http://developer.sugarlabs.org).

Please note that you must run [http://legacy.python.org/dev/peps/pep-0008/#introduction pep8] and pyflakes on your code ''before'' submitting your patches.

=== Getting started with GIT ===

Some knowledge of git is important as your work will be submitted to our git repository (https://github.com/sugarlabs). The basic mechanism is a pull request (PR), which is detailed in [http://developer.sugarlabs.org/contributing.md.html].

GitHub provides a tutorial (See https://try.github.io/levels/1/challenges/1), although there are many others as well.

Note that our bug tracker is http:bugs.sugarlabs.org.

=== Getting started with Sugarizer ===

Sugar Web Framework is the JavaScript Framework for Sugar [https://github.com/sugarlabs/sugar-docs/blob/master/web-architecture.md]. Sugarizer [http://sugarizer.org] is a subset of Sugar that allow runing activities developed with Sugar Web Framework on any web browser. Sugarizer is also available as Android, iOS, Firefox OS and Chrome Web App.





== Mentors ==
;NOTES TO MENTORS:
:Please refer to [[Google Code In 2015/Participate#Mentors]] for details regarding enrolling as a mentor.
:Please add yourself to the list below.
:Feel free to add new tasks to the table above.

Depending on the project, we will assign multiple mentors from our various development and support teams.

* Walter Bender - also org admin for GCI
* Sam Parkinson (student volunteer)
* Ignacio Rodriguez (student volunteer)
* German Ruiz
* Amit Kumar Jha
* Martin Abente
* Mariah Noelle Villarreal
* Gary Servin Cardozo
* Rajul Srivastava
* Julio Daniel Reyes
* Arturo Volpe
* Lionel Laské
* Bernie Innocenti
* Devin Ulibarri
* Tummala Dhanvi
* Tymon Radzik

Summer of Code/2016

2016-03-06T11:31:15Z

TymonR: /* Sugar Technology */ - new project

'''Students''': See our guide on [[Summer_of_Code#How_to_participate|how to participate in Google Summer of Code]] for more information.

== Project candidates ==

In the table below is a list of projects potential participants might contribute to in the GSoC program.

;Note 0: These are project ideas from Sugar Labs contributors. '''Students, feel free to propose your ideas as well.'''
;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.

== Sugar Core ==

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! !! Title !! Mentor !! Project
|-
!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:#e3e4e5;" |Journal Rethink ||valign=top width="15%" | Sam Parkinson Ignacio Rodríguez ||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.
;Expected results: Working code for the journal and vague ideas (more concrete than this) defined ahead of time.
;Knowledge prerequisite: Strong background in Python and knowledge of Gtk+.
|-
!valign=top | [[Image:Sugarlabs_mainpage_01.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" | Groups Rethink ||valign=top width="15%" | Sam Parkinson Ignacio Rodríguez ||align=left valign=top|
;Brief explanation: Sugar has a buddies/group zoom view, which is very limited. It could be further integrated with sugar (eg. send to group, share with group, have a shared group journal) and expanded upon (having multiple groups user configured, like: a science prac group, a drama play group, etc.).
;Expected results: Working code for the Sugar and vague ideas (more concrete than this) defined ahead of time.
;Knowledge prerequisite: Strong background in Python and knowledge of Gtk+. Knowledge of telepathy is might be helpful.

|-
!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.
;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+.

|-
!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|
;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
;Knowledge prerequisite: Strong background in Git and scripting languages such as Python, Ruby and JavaScript.

|-
!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.
;Expected results: build suitable for running on OLPC XO-1 hardware
;Knowledge prerequisite:

|-
!valign=top | || valign=top style="background:#e3e4e5;" | Re-design collaboration with web technologies || valign=top | Martin Abente Lahaye and Walter Bender ||align=left valign=top |
;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.
|}

== Sugar Activities ==

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! !! Title !! Mentor !! Project

|-
!valign=top | [[File:confusion.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" |Beyond Flashcards: Programming to ReadJS||valign=top width="15%" | Walter Bender||align=left valign=top|
;Brief explanation: Back in the 1980s, IBM had a literacy program, "Writing to Read". The gist was that writing was a great way to spark a child's interest in reading. What if writing code could achieve a similar result? The project is to explore how programming might be incorporated into a literacy program. Like turtle, only simple sentences instead of stacks. It would be a "whole word" approach rather than a "phonics" approach: they can take "sentences" and make paragraphs that result in animations.
;Expected results: Working prototype
;Knowledge prerequisite: Strong background in Python or JavaScript

|-
!valign=top | ||valign=top width="15%" style="background:#e3e4e5;" | Covert Record, Clock, Speak and Measure to gstreamer 1.0 ||valign=top width="15%" | Ignacio Rodríguez ||align=left valign=top|
;Brief explanation: The vast majority of Activities that use gstreamer for sound have been converted to gstreamer 1.0 because the older 0.10 is now End of Life and is no longer being developed. It also adds quite a large set of extra duplicate dependencies to Sugar distributions. There's a lot of good examples of Activities that have been converted to provide excellent examples. The gstreamer 1.0 bindings are provided by gobject-introspection so it also assists in the conversion of Activities to gtk3.
;Expected results: As many of the above Activities converted to use gst 1.0
;Knowledge prerequisite: Strong background in Python, gobject-introspection and gstreamer

|-
!valign=top | ||valign=top width="15%" style="background:#e3e4e5;" | Covert TamTam to Csound6 ||valign=top width="15%" | <TBD> ||align=left valign=top|
;Brief explanation: TamTam makes extensive use of CSound, other Activities like Memorize, Pippy, and TurtleBlocks also can make use of CSound bindings. With the introduction of CSound 6 to a number of distributions TamTam needs migration to use the newer version of CSound.
;Expected results: Convert TamTam to use CSound6, possibly other Activities
;Knowledge prerequisite: Strong background in Python, background in CSound

|-
!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|
;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).
;Expected results: Users will use these to explore musical concepts and generate desired
blocks from their experiments.
;Knowledge prerequisite: Strong background in Javascript, Basic knowledge of Music Theory
and/or physics
|}

== Sugar Activities (and Ports) ==

These are existing and new activities we'd like to see enhanced. We expect that the activities will take on new UI features and pedagogical significance.

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! !! Title !! Mentor !! Project

|-
!valign=top | [[File:Music-Blocks.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" |Music Blocks Challenges||valign=top width="15%" | Devin Ulibarri||align=left valign=top|
;Brief explanation: Development of the "Power Piece" concept for teaching music and programming. (Power Pieces introduce rich musical ideas that can be studied, analyzed, transformed, and re-imagined, they are ripe for open-ended explorations.)
;Expected results: A well-documented series of activities for exploring musical and programming concepts using the Music Blocks activity as a foundation.
;Knowledge prerequisite: Strong background in Javascript, Music Theory
|-
!valign=top | [[File:Nutrition-icon.svg|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" |Nutritional Microworld||valign=top width="15%" | w/Dr. Jessica Early||align=left valign=top|
;Brief explanation: We have the basic building blocks (Turtle Nutrition) for programming with food as a datatype. What we are missing is a collection of meaningful activities to use with the tool as exemplars. We want to develop a an open-ended, yet
relevant tool—one that invites learners to explore fundamental concepts of nutrition that are both intrinsic to nutrition yet transcendent of a specific discipline.
;Expected results: A well-documented series of activities for exploring nutrition that use the nutrition plugin as a basis. A series of workshops to study these ideas with children.
;Knowledge prerequisite: Strong background in Javascript, some background in Nutrition.
|-
!valign=top | [[File:Turtle-Flags.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" |Turtle Confusion/Flags JS||valign=top width="15%" | Walter Bender||align=left valign=top|
;Brief explanation: Port of Turtle Confusion and Turlte Flags.
;Expected results: A framework for creating challenges and a few exemplars.
;Knowledge prerequisite: Strong background in Javascript

|-
!valign=top | ||valign=top width="15%" style="background:#e3e4e5;" | Tux Math||valign=top width="15%" | Tony Anderson ||align=left valign=top|
The TuxMath activity is popular with deployments. However, the upstream version appears to be abandoned. This task would be to implement a sugar-web-activity math game comparable to TuxMath.

|}

== Sugar Technology ==

Sugar is based on the Python programming language and the GTK libraries. We also support some web technologies: HTML5, CSS, and JavaScript.

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! !! Title !! Mentor !! Project

|-
!valign=top | [[File:Debugging.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" | Unit Testing ||valign=top width="15%" | TBD ||align=left valign=top|
Deep dive into unit tests. We have a framework but it provides scant coverage for Sugar core and almost no coverage for Sugar activities.
;Brief Description: The goal is to develop tests for many more subsystems in Sugar core and to light a fire under the developer community to write tests for Sugar activities.
;Expected Results: a new test suite and scads of documentation.
;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.
|}

== Sugar on the Ground ==

A number of real-world issues crop up in deployments of Sugar, especially where resources are limited (bandwidth, CPU speed, battery life, local storage, etc.) These tasks are related to making Sugar more usable under such circumstances.

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! !! Title !! Mentor !! Project

|-
!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|

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.
;Note: this approach satisfies the needs referenced in the git task. Git is a little like a hammer looking for a nail. Using git for this function will likely double the size of the data stored in the Journal (based on normal experience using git). Unfortunately, we don't have this space on the XOs. The standard save/save as gives the user the ability to manage versions by using unique names.

|-
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" | Sugar Journal as a service ||valign=top width="15%" | Tony Anderson ||align=left valign=top|

The Journal activity is currently implemented as an activity. It should be changed to a 'service'. This means the Journal icon on the frame should be to the left of the zoom group icons to match the sequence on the keyboard. The Journal is always running as a service when the Sugar is running. It is accessible by the Journal key on the keyboard and also by the Journal button in the frame. When the view is switched to the Journal, clicking on the activity view (right most key of the zoom group) should switch the screen back to the current activity.

|-
!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 Ignacio Rodriguez||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).
;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
;Note: This would essentially accomplish the intent of the group/buddy task. Further, OwnCloud could be provided on a school server or on the internet. as appropriate.
;Note: There is a Sugar interface for saving to other cloud services, such as Google Docs, Dropbox, et al. that could be exploited.

|-
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" | Sugar Journal session data management ||valign=top width="15%" | Tony Anderson ||align=left valign=top|
One goal of Sugar is to record information about user sessions. This is currently accomplished by creating statistics from the metadata stored in the Journal.
Unfortunately, a consequence is that the Journal view fills with essentially meaningless links to this metadata (mine fills with Terminal Activity and Log entries).
This makes it much harder for the user to identify meaningful Journal objects (documents, images, items from the library, ...). A mechanism is needed to that session data can be logged independently of the Journal view (i.e not shown on the screen). This logged information should be transferred to a backup repository (e.g. school server or USB drive) as soon as possible and deleted from the local store to free up space. The available reporting activities should be modified to use this new mechanism.

|-
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" | Sugar Journal quota management ||valign=top width="15%" | Tony Anderson ||align=left valign=top|
The Journal icon provides information the amount of free space in the user's store. if this amount is less than 50MB, a dialog is shown requiring the user to switch to the Journal view and claiming that the 'Journal is Full'. This message is, at best, misleading. The available storage can arise from several causes - the fact that an activities 'instance' store was not deleted, the space required by installed activities, or space required by data files in /home/olpc/Library, or data stored by activities in 'data', 'instance' or 'temp'. Currently, Sugar provides no guidance or help to enable a user to deal with this problem short of reflashing the image. The goal of this task is to provide a quota management system on storage with a way for the user (e.g. by a special Sugar activity) to analyze the usage of storage and to save by usb key or school server or cloud storage large or currently unneeded items and then delete them. The system should show the user the size of items and provide updates on how much storage has been made free by his/her actions.

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

This task should set the Home View default to launch a new instance of the activity. The Alt key should be set to enable resuming a selected instance of the activity. By serendipity, this also shows the Home View with black and white icons. Icons with color signifying a resumable instance use the colors associated with the laptop. Unfortunately many of these color combinations make the icon much more difficult to distinguish than the black and white version.

|-
!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 Ignacio Rodriguez ||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).

|-
!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|
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;" | Sugar "on-boarding" ||valign=top width="15%" | Tony Anderson ||align=left valign=top|
Sugar users are often new to computers and not familiar with other operating systems. We need a mechanism to allow users to more quickly develop skills in using the capabilities of the XO ('onboarding'). One proposal is to develop scripts which lead the user through a series of interactive steps illustrating common usage of the XO with Sugar ([https://www.sam.today/blog/sugar-onboard-design.html]). This task is to implement an interpretive system that allows
deployments or experienced users to create an 'onboard' script that guides the user to carry out a task. The referenced proposal suggests some user tasks where this mechanism could be employed. Since there is no finite list of these tasks, an interpretive approach enables the scripts to be created as necessary.
;For example: how does a user switch to the Gnome desktop? A script could be created guiding the user through the necessary steps. How does the user make a screen shot, use Gimp in the gnome desktop to crop and resize, and then insert it as an image in a Write document? How does the user initiate or join a chat?

|-
!valign=top | [[File:Journal.png|90px|thumb|center]] ||valign=top width="15%" style="background:#e3e4e5;" | 32bit Sugar on Ubuntu||valign=top width="15%" | Tony Anderson ||align=left valign=top|
Sugar is available on the XO and some other platforms. In particular, Sugar is available for 64-bit systems with Ubuntu 14.04 LTS installed (http://wiki.sugarlabs.org/go/Ubuntu). Unfortunately, this procedure does not work with 32-bit systems. There exists an opportunity to deploy Sugar
with relatively inexpensive or refurbished laptops which do not provide 64-bit support. This task is to create a comparable version of Sugar which can
be installed on 32-bit systems as an alternate Ubuntu desktop.

|-
!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 [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.

|}

== Sugarizer ==

[http://sugarizer.org Sugarizer] is a way to use Sugar on any device using web technologies (HTML5/JavaScript). Strictly speaking, Sugarizer is not a port of Sugar. Sugarizer is based on Sugar Web library, which mimics the Sugar UI using HTML5 and CSS3 and reproduces Sugar views (Home, List, ...). Sugarizer reimplements features of Sugar Core (datastore and journal) in JavaScript and integrates a bunch of activities written for Sugar in Sugar Web.

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! !! Title !! Mentor !! Project

|-
!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é 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.

On Android, Sugarizer OS will take the form of an Android Launcher so it will be able to replace the standard Android launcher of the device. So the user will be able to launch both Sugarizer Activities and Android application from the Sugarizer home. The Sugarizer List View screen will let you choose which Android application icons will appear in the favorite view.

Into Sugarizer OS the Neighborhood view will let the user see and connect to a WiFi hotspot as in Sugar. The Sugarizer OS settings will allow to access to Android settings and let the use to switch to the standard Android launcher.

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é 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:
* 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.
* Journal: how many Journals and how many entries in Journal on the server, last Journal and last entries, size of Journals, top Journals, edit a journal (see/update/remove) entries.
* Application: how many applications are available on the server, change application visibility from Client, update order and way to appear in favorite view.
* Graphic and request: display graphics and report on previous data.

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é and Michaël Ohayon ||align=left valign=top|
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.
* Speak: Speak is a talking face. Anything you type will be spoken aloud using the speech synthesizer, espeak.
* Fototoon: Fototoon is an activity that let user create cartoons using pictures from the journal.

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.

|}

==Subpages==
{{Special:PrefixIndex/{{PAGENAMEE}}/}}

Summer of Code

2016-03-06T11:18:48Z

TymonR: Links update

<noinclude>{{TeamHeader|Summer of Code|home=Summer of Code Project Home|xbgColor=ffe792}}</noinclude>

[http://google-opensource.blogspot.com/2016 '''Google Summer of Code'''] Sugar years: | [[Summer of Code/2009|2009]] | [[Summer of Code/2010|2010]] | [[Summer of Code/2011|2011]] | [[Summer of Code/2012|2012]] | [[Summer of Code/2013|2013]] | [[Summer of Code/2014|2014]] | [[Summer of Code/2015|2015]] | [[Summer of Code/2016|2016]]

Sugar Labs is applying to '''Google Summer of Code (GSoC)''' for 2015.

'''Upcoming deadlines:'''

'''February 19'''
:'''Mentoring organization application deadline.'''

'''February 29'''
:'''Mentoring organizations announced.'''

==Links==

*'''[https://summerofcode.withgoogle.com/ Website]'''

*'''[https://developers.google.com/open-source/gsoc/timeline Timeline]'''

*'''[https://developers.google.com/open-source/gsoc/faq FAQs]'''

We look forward to accepting your contributions to support the use of technology in education. Google Summer of Code (GSoC) is "a global program that offers student developers stipends to write code for various open source projects."[http://socghop.appspot.com/ 1]

== How to participate ==

<center>
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! As a student !! As a mentor !! By contributing ideas
|-
| width=34%; valign=top | The most important job of all! Sugar Labs is looking forward to your contribution. To begin, we strongly recommend orienting yourself with the Sugar Labs codebase. Be sure to visit http://bugs.sugarlabs.org/.

Please add your proposal to the wiki on a page called:

Summer_of_Code/2016/'''Proposal_name'''

where Proposal_name is the name of your proposal. Please copy this [[Summer_of_Code/Template|proposal template]].

You also need to apply on the Google Summer of Code website.
| width=33%; valign=top| You can directly benefit a new software developer's coding competency and confidence levels while contributing to Sugar Labs and developing your own first-line management skills.
| width=33%; valign=top| Here you can look for more development ideas – [http://wiki.sugarlabs.org/go/Summer_of_Code/Resources#Project_Ideas projects] [http://wiki.sugarlabs.org/go/Summer_of_Code/20165 GsoC 2016].
|}

</center>

;Note: We are experiencing some issues with account creation both on the wiki and in the bug tracker. If you run into problems, please contact Walter Bender as per below.

== Person to Contact ==

Need help? Contact [[User:Walter| Walter Bender]]. He's responsible for,

* Maintaining this wiki page for the summer 2016 GSoC season (Feb 2016 - Sep 2016),
* Coordinating SL's application to the GSoC program as a mentorship organization,
* Recruiting mentors,
* Recruiting applicants,
* Selecting applicants,
* Supervising mentors, which largely entails making sure mid-term and end-of-summer reports are handed in on time,
* Interfacing with the Sugar Labs Oversight Board members to deal with collection and distribution of funds from Google

== Some external links ==
* [http://summerofcode.withgoogle.com Google Summer of Code Page]
* [https://developers.google.com/open-source/ Google Open Source Programs Office]
* [http://google-opensource.blogspot.com/ Google's Open Source Blog]
<noinclude>

==Subpages==
{{Special:PrefixIndex/{{PAGENAMEE}}/}}
[[Category:Project]]
[[Category:Participate]]
[[Category:GSoC]]
</noinclude>