Difference between revisions of "Summer of Code/2016"

From Sugar Labs
Jump to navigation Jump to search
Line 6: Line 6:
  
 
;Note 0: These are project ideas from Sugar Labs contributors. '''Students, feel free to propose your ideas as well.'''
 
;Note 0: These are project ideas from Sugar Labs contributors. '''Students, feel free to propose your ideas as well.'''
−
;Note 1: We are focusing on the Javascript components within Sugar this summer. It means that you've got to write activities for Sugar Web and Sugarizer. More information: on Sugar Web [https://github.com/sugarlabs/sugar-docs/blob/master/web-architecture.md][https://github.com/sugarlabs/sugar-docs/blob/master/activity.md] and on Sugarizer [http://sugarizer.org]
+
;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 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 3: Potential students, more project ideas can be found on our [[Features]] page.
+
;Note 3: Accepted projects are in '''<font color="#00bb00">Green</font>'''
−
;Note 4: Accepted projects are in '''<font color="#00bb00">Green</font>'''
 
  
 
== Sugar Core ==
 
== Sugar Core ==

Revision as of 09:08, 16 February 2016

Students: See our guide on 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.
Note 3
Accepted projects are in Green

Sugar Core

Title Mentor Project
Git logo.png
Git backend Martin Abente Lahaye and Walter Bender
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.
Performance tuning on machines with limited memory Samuel Greenfeld and James Cameron
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
Re-design collaboration with web technologies Martin Abente Lahaye and Walter Bender
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

Title Mentor Project
Confusion.png
Beyond Flashcards: Programming to ReadJS Walter Bender
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
Covert Record, Clock, Speak and Measure to gstreamer 1.0 <TBD>
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
Covert TamTam to Csound6 <TBD>
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

Sugar Activities (Ports)

These are existing Python activities we'd like to see ported to JavaScript. In porting we expect that the activities will take on new UI features and pedagogical significance.

Title Mentor Project
Turtle-Flags.png
Turtle Confusion/Flags JS Walter Bender
Brief explanation
Port of Turtle Confusion and Turlte Flags.
Expected results
Knowledge prerequisite
Strong background in Javascript

Sugar Technology

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

Title Mentor Project

Subpages

Retrieved from "https://wiki.sugarlabs.org/index.php?title=Summer_of_Code/2016&oldid=96966"