Google Code In 2013
This is the project page for the Sugar Labs application to Google Code In 2013. Sugar Labs community members: please feel free to add tasks below. We'll do an edit before final applications are due on 28 Oct 2013.
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/gci2013/help_page#eligibility
Please see the Contest Rules for Eligibility and Registration process.
http://www.google-melange.com/gci/document/show/gci_program/google/gci2013/terms_and_conditions
Details regarding the required forms and paperwork are here: Google Code In 2013/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.
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 |
|---|---|---|---|---|
| Activity links to documentation | All activity pages on ASLO should provide links to trac and git activities.sugarlabs.org | activity | ||
| Sensor designs | Measure sensor schematics | activity | ||
| Use latest toolbars in MYOSA examples | Make Your Own Sugar Activities! describes our current toolbar code as "new" and uses the old style in examples. Correct this. | James Simmons | activity | |
| How to videos 1 | Make a video showing how to use the Sugar Home view to launch activities | sugar | ||
| How to videos 2 | Make a video showing how to use the Sugar Neighborhood view to share activities | sugar | ||
| How to videos 3 | Make a video showing how to use the Sugar Journal | sugar | ||
| How to videos 4 | Make a video showing how to use the Sugar View Source | sugar | ||
| How to videos 5 | Make a video showing how to use the Sugar Write activity | activity | ||
| How to videos 6 | Make a video showing how to use the Sugar Record activity | activity | ||
| How to videos 7 | Make a video showing how to use the Sugar Turtle Art activity | activity | ||
| How to videos 8 | Make a video showing how to use the Sugar Portfolio activity | activity |
Outreach/Research
Tasks related to community management, outreach/marketing, or studying problems and recommending solutions
| Title | Description | Hours | Mentor | Tag |
|---|---|---|---|---|
| Learn to read website | Proposed activity for best English-language learn-to-read website | activity | ||
| Best of web collection | Research wiki pages for best-of-web learning sites wiki.sugarlabs.org | activity | ||
| Bug reporting | Design an easier bug reporting mechanism for Sugar | activity | ||
| Research R2L issues | Research into Arabic (R2L) bugs in Sugar | activity | ||
| Enhanced Mindmap links | Research how Mindmaps tools are used and recommend more node and relationship attributes | activity |
User Interface
Tasks related to user experience research or user interface design and interaction
Quality Assurance
Tasks related to testing and ensuring code is of high quality.
| Title | Description | Hours | Mentor | Tag |
|---|---|---|---|---|
| Sharing QA | Gather data on how many users can collaborate across various Sugar activities. | walterbender | activity | |
| Complete i18n of ASLO | ASLO still has un-translated ES strings. Identify these strings for translation. | activity | ||
| Sugar Triage | Organize a triage meeting to review/assign open sugar bugs [1] | sugar | ||
| Activities Triage | Organize a triage meeting to review/assign open activity bugs [2] | activities | ||
| Untriaged | Organize a triage meeting to review/assign untriaged bugs [3] | sugar |
Code
Tasks related to writing or refactoring code
Mentors
- NOTES TO MENTORS
- Please refer to Google Code In 2013/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
- Martin Abente
- Sandra Thaxter
- James Simmons
- Sebastian Silva
- Laura Vargas