Difference between revisions of "Google Code In 2013"
(→Tasks) |
m (→Tasks) |
||
| Line 22: | Line 22: | ||
Tasks must fall within one of these five categories: | Tasks must fall within one of these five categories: | ||
| − | + | ===Documentation/Training=== | |
| + | Tasks related to creating/editing documents and helping others learn more | ||
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;" | {| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;" | ||
| Line 35: | Line 36: | ||
|} | |} | ||
| − | + | ===Outreach/Research=== | |
| + | Tasks related to community management, outreach/marketing, or studying problems and recommending solutions | ||
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;" | {| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;" | ||
| Line 54: | Line 56: | ||
|} | |} | ||
| − | + | ===User Interface=== | |
| + | Tasks related to user experience research or user interface design and interaction | ||
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;" | {| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;" | ||
| Line 97: | Line 100: | ||
|} | |} | ||
| − | + | ===Quality Assurance=== | |
| + | Tasks related to testing and ensuring code is of high quality. | ||
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;" | {| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;" | ||
| Line 108: | Line 112: | ||
|} | |} | ||
| − | + | ===Code=== | |
| + | Tasks related to writing or refactoring code | ||
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;" | {| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;" | ||
Revision as of 14:56, 24 October 2013
This is the project page for the Sugar Labs application to Google Code In. 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
Tasks must fall within one of these five categories:
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 accepted | 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 |
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 | Wiki pages for best-of-web learning sites wiki.sugarlabs.org | activity | ||
| Bug reporting | easier bug reporting | activity | ||
| Research R2L issues | Ticket to track Arabic bugs | activity | ||
| Enhanced Mindmap links | Allow more node and relationship attributes | activity | ||
| Color-coded devices | Removable storage devices and in general entities with their own identities should have unique colors | design |
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 | We need better data on how many users can collaborate across the various Sugar activities (independent of network load | walterbender | activity | |
| Complete i18n of ASLO | Aslo still has un-translated ES strings. | activity |
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