Difference between revisions of "Google Code-In 2012"
| Line 141: | Line 141: | ||
|- | |- | ||
|Port to Python3 || align=left | [[GoogleCodeIn2012/Python3|Research the issues we will encounter in porting to Python 3]] || 40 || || Outreach/Research || future | |Port to Python3 || align=left | [[GoogleCodeIn2012/Python3|Research the issues we will encounter in porting to Python 3]] || 40 || || Outreach/Research || future | ||
| − | |||
| − | |||
|- | |- | ||
|Orphaned activities || align=left | [[GoogleCodeIn2012/Sugar_orphan_status|Do an analysis of which Sugar activities are are orphaned.]] || 20 || gonzalo || Quality Assurance || maintenance | |Orphaned activities || align=left | [[GoogleCodeIn2012/Sugar_orphan_status|Do an analysis of which Sugar activities are are orphaned.]] || 20 || gonzalo || Quality Assurance || maintenance | ||
| Line 165: | Line 163: | ||
|- | |- | ||
|New Features || align=left | [[GoogleCodeIn2012/Feature_requests|Survey Sugar users to find out what UI features they want from Sugar in the future.]] || 120 || || User Interface || future | |New Features || align=left | [[GoogleCodeIn2012/Feature_requests|Survey Sugar users to find out what UI features they want from Sugar in the future.]] || 120 || || User Interface || future | ||
| − | + | |- | |
| + | |Manage on-line credentials || align=left | [[GoogleCodeIn2012/OnlineAccounts|What's the best way to handle on-line credentials in Sugar (i.e.: Facebook Twitter Google)]] || 120 || rgs || User Interface || future | ||
|} | |} | ||
Revision as of 02:24, 26 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 - also org admin for GCI
- Walter Bender - also org admin for GCI
- Andrés Aguirre Dorelo
- Claudia Urrea
- Gonzalo Odiard
- Adam Holt
- Manuel Kaufmann
- Jeffrey Elkner
- John Tierney
- JerryV
- Alan Aguiar
- Luke Faraone
- Luis Gustavo Lira
- James Simmons
- Sam Greenfeld
- Tom Gilliard
- Martín Abente Lahaye
- Tony Forster
Possible additional mentors:
- Pacita Pena
- Rosamel Ramirez
- Sdenka Salas
- Simon Schampijer
- Manuel Quiñones
- Tony Forster
- Guzman Trinidad
- Sean Daly
- Mark Battley
- Bernie Innocenti
- Daniel Drake
- Raul Guttierrez Segales
- C Scott Ananian
et al.