Difference between revisions of "Google Code-In 2012"
(→Tasks) |
(→Tasks) |
||
Line 112: | Line 112: | ||
|GTK3 conversion guide || align=left | [[GoogleCodeIn2012/GTK3_guide|Flesh out the GTK-2 to GTK-3 conversion documentation to include more comprehensive coverage of Pango.]] || 40 || || Documentation/Training || gtk3 | |GTK3 conversion guide || align=left | [[GoogleCodeIn2012/GTK3_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 || align=left | [[GoogleCodeIn2012/SOAS_guide|Better document the process of creating and using Sugar on a Stick the LiveUSB version of Sugar.]] || 40 || | + | |Sugar on a Stick guide || align=left | [[GoogleCodeIn2012/SOAS_guide|Better document the process of creating and using Sugar on a Stick the LiveUSB version of Sugar.]] || 40 || satellit || Documentation/Training || soas |
|- | |- | ||
|Create new Sugar Labs home page || align=left | [[GoogleCodeIn2012/SugarLabs.org|We have some detailed designs of a new website that need to be implemented.]] || 120 || || Documentation/Training || www | |Create new Sugar Labs home page || align=left | [[GoogleCodeIn2012/SugarLabs.org|We have some detailed designs of a new website that need to be implemented.]] || 120 || || Documentation/Training || www | ||
|- | |- | ||
− | |Sugar VM || align=left | [[GoogleCodeIn2012/VM|Better document the process of running Sugar in a virtual machine (VM).]] || 40 || | + | |Sugar VM || align=left | [[GoogleCodeIn2012/VM|Better document the process of running Sugar in a virtual machine (VM).]] || 40 || satellit || Documentation/Training || soas |
|- | |- | ||
|How-to videos || align=left | [[GoogleCodeIn2012/Videos|Create videos on how to use Sugar and how to use core Sugar activities.]] || 20 || || Documentation/Training || doc | |How-to videos || align=left | [[GoogleCodeIn2012/Videos|Create videos on how to use Sugar and how to use core Sugar activities.]] || 20 || || Documentation/Training || doc |
Revision as of 10:14, 25 November 2012
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
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
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.