Google Code-In 2012

Revision as of 08:03, 20 November 2012 by Walter (talk | contribs) (→‎Tasks)

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

Details regarding the required forms and paperwork are here: GoogleCodeIn2012/Participate#Students.

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

Code-in FAQ

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

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
Title Description Hours Mentor Category Tag
Pootle helper-script Write a new pootle-helper script for doing preventative msgfmt checks. 20 cjl code i18n
Sugarize Virtaal Sugarize Virtaal for L10n bootstrapping 60 cjl code i18n
GTK2-to-GTK3 conversion Convert Sugar activities from GTK-2 to GTK-3 framework. 10 code gtk3
On-screen keyboard support Enable touch for activities that use direct keyboard input. 20 code touch
Set background image Implement the set background image on Home View Feature. 40 walter code sugar
Multiple Homeviews Implement the multiple homeview feature 60 walter code sugar
Package toolbar utils Package Sugar activity utilities 2 walter code toolkit
Infoslicer enhancement (wikislices) Extend the Infoslicer activity to be able to use the local content in the Wikislices project. 20 humitos code activity
Infoslicer enhancement (journal images) Extend the Infoslicer activity to be able to use images from the Sugar Journal 20 humitos code activity
Sugarize Python Turtle module Will require port of the Python turtle module to GTK (currently it is QT) 60 code activity
Turtle Art nutrition Further develop the prototype Turtle Nutrition plug-in into a stand-alone activity. 60 walter code activity
Portfolio videos Add a mechanism for exporting .ogv (voice over still images) of a portfolio presentation 40 walter code activity
Unified journal view Rather than viewing the details of a Journal entry on a separate page make the details appear in an expandable in-line format 120 code sugar
Plugin support Design a uniform plug-in bundle type and modify the activity installer to recognize this new type. 80 code activity
End-user modifications of Sugar source We have a mechanism for viewing the Sugar toolkit source but no such convenient way for making changes without risking messing up the system. 120 code sugar
Implement collaboration in Paint Activity Paint Activity does not implement collaboration yet. 40 gonzalo code activity
Implement a presentation mode in Fototoon Fototoon should have a view to edit and view one cell at a time using the full screen. 40 gonzalo code activity
Port GBrainy to Python GBrainy have many good logic games 60 code activity
Implement help mechanism for activities using Mallard Mallard is a markup language that makes it easy to provide user help. It would be a nice feature to add Mallard-like help to activities but is programmed in Mono. It would nice to have a native Python version accessed through a mechanism similar to the view source mechanism. 60 code sugar
Turtle Art tutorial Write a Turtle Art introductory tutorial 60 walter documentation/training activity
Multilanguage screen-shots 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?). 60 documentation/training i18n
GTK3 conversion guide Flesh out the GTK-2 to GTK-3 conversion documentation to include more comprehensive coverage of Pango. 40 documentation/training gtk3
Sugar on a Stick guide Better document the process of creating and using Sugar on a Stick the LiveUSB version of Sugar. 40 documentation/training soas
Create new Sugar Labs home page We have some detailed designs of a new website that need to be implemented. 120 documentation/training www
Sugar VM Better document the process of running Sugar in a virtual machine (VM). 40 documentation/training soas
How-to videos Create videos on how to use Sugar and how to use core Sugar activities. 20 documentation/training doc
How to create a collection Create a guide to creating and using collections. 5 documentation/training doc
Sugar FLOSS Manual Update and add new content to the manual Sugar Manual 20 documentation/training doc
Make your own Sugar activity Update and add new content to the manual Make Your Own Sugar Activities 40 James Simmons documentation/training doc
SVG internationalization Research internationalization of SVG images. 120 outreach/research i18n
Sugar assessment tools Research what metadata about Sugar activity usage would be helpful to teachers for assessment purposes. 40 outreach/research assessment
Sugar in your school (opportunities) Research what opportunities/roadblocks exist for running Sugar in your local schools. 40 outreach/research outreach
Sugar in your school (roadblocks) Research what is missing from Sugar that makes it unused by your local schools. 40 outreach/research outreach
Sugar in the Cloud Research the issues involved with porting Sugar to the Cloud. 60 outreach/research future
Sugar on Android Research the issues involved with porting Sugar to Android. 120 outreach/research future
Copyleft Games Research how Sugar Labs might leverage the work of copyleftgames.org and CGG might leverage the work of Sugar Labs. 20 outreach/research activity
Port to Python3 Research the issues we will encounter in porting to Python 3 40 outreach/research future
Manage on-line credentials What's the best way to handle on-line credentials in Sugar (i.e.: Facebook Twitter Google) 120 outreach/research future
Orphaned activities Do an analysis of which Sugar activities are are orphaned. 20 quality assurance maintenance
Sugar Touch Do an analysis of which Sugar activities are touch-enabled or need modifications to support touch. 20 quality assurance maintenance
Sugar Documentation Do an analysis of which Sugar activities are lacking in documentation (e.g. Activity wiki page). 20 quality assurance doc
Sugar on ARM Do an analysis of which Sugar activities are have issues running on non-x86 architectures (e.g. ARM). 20 quality assurance arm
Sugar i18n Do an analysis of which Sugar activities are lacking i18n support. 20 quality assurance i18n
Special Needs Analyze Sugar from the point of view of special needs and make recommendations for improvements. 40 user interface sugar
Touch UI Help us design the Sugar affordances for Sugar on tablet computers (Sugar Touch). 40 user interface sugar
On-screen Keyboard Develop new Maliit keyboard files for additional languages(beyond those already developed by garycmartin). 20 cjl, garymartin user interface sugar
Accelerometer Think of ways to further leverage the use of an accelerometer in Sugar (and other common sensors found in portable computing devices). 40 user interface sugar
How are we doing? Assessing how Sugar is used by students. What is being learned? Survey students and teachers. How well does it deliver its goals? 120 user interface learning
New Features Survey Sugar users to find out what UI features they want from Sugar in the future. 120 user interface future

Mentors

NOTES TO MENTORS
Please refer to GoogleCodeIn2012/Participate#Mentors for details regarding enrolling as a mentor.
Please add yourself to the table above.
Feel free to add new tasks to the table.

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.