Google Code In 2014
This is the project page for the Sugar Labs application to Google Code In 2014. Sugar Labs community members: please feel free to add tasks below. We'll do an edit before final applications are due in late Oct 2014.
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/gci2014/help_page#eligible
Please see the Contest Rules for Eligibility and Registration process.
http://www.google-melange.com/gci/document/show/gci_program/google/gci2014/terms_and_conditions
Details regarding the required forms and paperwork are here: Google Code In 2014/Participate#Students.
Also, you will likely need to set up the Sugar development environment. See http://developer.sugarlabs.org/dev-environment.md.html for details. Further information about contributing to the project can be found here: http://developer.sugarlabs.org/
Please don't hesitate to ask questions on our irc channel (#sugar on irc.freenode.net) or on the sugar-devel list: sugar-devel AT lists.sugarlabs DOT org
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.
Tasks
Note: This is our preliminary list of tasks. We can add more as the contest progresses.
Mentors: please feel free to add more tasks and/or add yourself as a potential mentor to an existing task.
Tasks must fall within one of these five categories: #Documentation/Training; #Outreach/Research; #User Interface; #Quality Assurance; and #Code.
Documentation/Training
Tasks related to creating/editing documents and helping others learn more
| Title | Description | Hours | Mentor | Tag |
|---|
Outreach/Research
Tasks related to community management, outreach/marketing, or studying problems and recommending solutions
| Title | Description | Hours | Mentor | Tag |
|---|
User Interface
Tasks related to user experience research or user interface design and interaction
| Title | Description | Hours | Mentor | Tag |
|---|
Quality Assurance
Tasks related to testing and ensuring code is of high quality.
| Title | Description | Hours | Mentor | Tag |
|---|
Code
Tasks related to writing or refactoring code
| Title | Description | Hours | Mentor | Tag |
|---|
Mentors
- NOTES TO MENTORS
- Please refer to Google Code In 2014/Participate#Mentors for details regarding enrolling as a mentor.
- Please add yourself to the list below.
- Feel free to add new tasks to the table above.
Depending on the project, we will assign multiple mentors from our various development and support teams.
- Walter Bender - also org admin for GCI