Sugar Labs is applying to participating in Google Code-in for 2012.
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.
http://www.google-melange.com/gci/document/show/gci_program/google/gci2012/help_page#eligibility
Please see the Contest Rules for Eligibility and Registration process.
http://www.google-melange.com/gci/document/show/gci_program/google/gci2012/terms_and_conditions
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.
About GCI
Tasks
This brainstorming page lists some general categories from which specific individual tasks can be specified. (Note: We had a number of tasks listed in our GSOC application that may be relevant to GCI. We also have many Features that are still pending.)
Key:
- Code
- Tasks related to writing or refactoring code
- Documentation/Training
- Tasks related to creating/editing documents and helping others learn more
- Outreach/Research
- Tasks related to community management, outreach/marketing, or studying problems and recommending solutions
- Quality Assurance
- Tasks related to testing and ensuring code is of high quality.
- User Interface
- Tasks related to user experience research or user interface design and interaction
(File:GCI.csv Please make your edits below, they will be migrated to the CSV list and uploaded to the GCI site.)
| Project | Title | Category | Notes |
|---|---|---|---|
| i18n | Pootle helper-script | code | Write a new pootle-helper script for doing preventative msgfmt checks. |
| i18n | Sugarize Virtaal | code | Sugarize Virtaal for L10n "bootstrapping" |
| gtk3 | GTK2-to-GTK3 conversion | code | Convert Sugar activities from GTK-2 to GTK-3 framework. |
| touch | On-screen keyboard support | code | Enable touch for activities that use direct keyboard input. |
| ui | Set background image | code | Implement the set background image on Home View Feature. |
| ui | Multiple Homeviews | code | Implement the multiple homeview feature |
| toolkit | Package toolbar utils | code | Package Sugar activity utilities (e.g. [1]) for inclusion in the Sugar toolkit. |
| activity | Infoslicer enhancement (wikislices) | code | Extend the Infoslicer activity to be able to use the local content in the Wikislices project. |
| activity | Infoslicer enhancement (journal images) | code | Extend the Infoslicer activity to be able to use images from the Sugar Journal |
| activity | Sugarize Python Turtle module | code | Will require port of the Python turtle module to GTK (currently it is QT) |
| activity | Turtle Art tutorial | documentation/training | Write a Turtle Art introductory tutorial |
| i18n | Multilanguage screenshots | documentaton/training | Identify and document a generalized (ideally automated) method for taking nearly identical screen shots with the desktop set to a selected list of different languages. (Possibly Orca?). |
| gtk3 | GTK3 conversion guide | documentation/training | Flesh out the GTK-2 to GTK-3 conversion documentation to include more comprehensive coverage of Pango. |
| soas | Sugar on a Stick guide | documentation/training | Better document the process of creating and using Sugar on a Stick the LiveUSB version of Sugar. |
| www | Create new Sugar Labs home page | documentation/training | We have some detailed designs of a new website that need to be implemented. |
| soas | Sugar VM | documentation/training | Better document the process of running Sugar in a virtual machine (VM). |
| doc | How to videos | documentation/training | Create videos on how to use Sugar and how to use core Sugar activities. |
| doc | How to create a collection | documentation/training | Create a guide to creating and using collections. |
| doc | Sugar FLOSS Manual | documentation/training | Update and add new content to the manual Make Your Own Sugar Activities! (details here). |
| i18n | SVG internationalization | outreach/research | Research internationalization of SVG images. |
| assessment | Sugar assessment tools | outreach/research | Research what metadata about Sugar activity usage would be helpful to teachers for assessment purposes. |
| outreach | Sugar in your school (opportunities) | outreach/research | Research what opportunities/roadblocks exist for running Sugar in your local schools. |
| outreach | Sugar in your school (roadblocks) | outreach/research | Research what is missing from Sugar that makes it unused by your local schools. |
| future | Sugar in the Cloud | outreach/research | Research the issues involved with porting Sugar to "the Cloud". |
| future | Sugar on Android | outreach/research | Research the issues involved with porting Sugar to Android. |
| cgg | Copyleft Games | outreach/research | Research how Sugar Labs might leverage the work of [copyleftgames.org CGG] and CGG might leverage the work of Sugar Labs. |
| maintenance | Orphaned activities | quality assurance | Do an analysis of which Sugar activities are are orphaned. |
| maintenance | Sugar Touch | quality assurance | Do an analysis of which Sugar activities are touch-enabled or need modifications to support touch. |
| doc | Sugar Documentation | quality assurance | Do an analysis of which Sugar activities are lacking in documentation (e.g. Activity wiki page). |
| arm | Sugar on ARM | quality assurance | Do an analysis of which Sugar activities are have issues running on non-x86 architectures (e.g. ARM). |
| i18n | Sugar i18n | quality assurance | Do an analysis of which Sugar activities are lacking i18n support. |
| ui | Special Needs | user interface | Analyze Sugar from the point of view of special needs and make recommendations for improvements. |
| ui | Touch UI | user interface | Help us design the Sugar affordances for Sugar on tablet computers (Sugar Touch). |
| ui | On-screen Keyboard | user interface | Develop new Maliit keyboard files for additional languages(beyond those already developed by garycmartin). |
| ui | Accelerometer | user interface | Think of ways to further leverage the use of an accelerometer in Sugar (and other common sensors found in portable computing devices). |
| ui | Assessment | user interface | Assessing how Sugar is used by students. What is learnt? Survey students and teachers. How well does it deliver its goals? |
| ui | New Features | user interface | Survey Sugar users to find out what UI features they want from Sugar in the future. |
Mentors
NOTE TO MENTORS: Please create an account on [2] and fill out the Request to be a Mentor form.
Depending on the project, we will assign multiple mentors from our various development and support teams.
- Chris Leonard
- Walter Bender
- Claudia Urrea
- Pacita Pena
- Rosamel Ramirez
- Sdenka Salas
- Sam Greenfeld
- Gonzalo Odiard
- Simon Schampijer
- Manuel Quiñones
- Tony Forster
- Guzman Trinidad
- Adam Holt
- Sean Daly
- Manuel Kaufmann
- Mark Battley
- Alan Aguiar
- Bernie Innocenti
- Daniel Drake
- Martin Abente
- Raul Guttierrez Segales
- C Scott Ananian
- James Simmons
- Luis Gustavo Lira
- Andres Aguirre
et al.