Difference between revisions of "Google Code-In 2012"
m (moved GoogleCodeIn2012 to Google Code-In 2012: Add white-space for readability) |
Tonyforster (talk | contribs) (→TASKS) |
||
| Line 12: | Line 12: | ||
''Please be sure to include at least 5 tasks from each of the 5 categories.'' | ''Please be sure to include at least 5 tasks from each of the 5 categories.'' | ||
| − | This [[GoogleCodeIn2012/GCI2012_Brainstorming|brainstorming]] page lists some | + | This [[GoogleCodeIn2012/GCI2012_Brainstorming|brainstorming]] page lists some general categories from which specific individual tasks can be specified. (Note: We had [[Summer_of_Code/2012#Project_candidates|a number of tasks]] listed in our GSOC application that may be relevant to GCI.) |
| Line 47: | Line 47: | ||
# Development of a new Maliit keyboard files for additional languages (beyond those already developed by garycmartin) | # Development of a new Maliit keyboard files for additional languages (beyond those already developed by garycmartin) | ||
# Leveraging accelerometer ??? | # Leveraging accelerometer ??? | ||
| − | # | + | # Assessing how Sugar is used by students. What is learnt? Survey students and teachers. How well does it deliver its goals. |
# | # | ||
[[Category: GCI2012]] | [[Category: GCI2012]] | ||
Revision as of 01:37, 30 October 2012
Sugar Labs is applying to Google Code-in for 2012.
Why we are applying
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
Please be sure to include at least 5 tasks from each of the 5 categories.
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.)
- Code
- Tasks related to writing or refactoring code
- New pootle-helper script for doing preventative msgfmt checks.
- Sugarizing Virtaal for L10n "bootstrapping"
- Documentation/Training
- Tasks related to creating/editing documents and helping others learn more
- Turtle Art introductory tutorial
- Identify and document a generalized (ideally automated) method for taking nearly identical screenshots with the desktop set to a selected list of different languages. (Possibly Orca?).
- Outreach/Research
- Tasks related to community management, outreach/marketing, or studying problems and recommending solutions
- Research internationalization of SVG images.
- 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
- Sugar Touch
- Development of a new Maliit keyboard files for additional languages (beyond those already developed by garycmartin)
- Leveraging accelerometer ???
- Assessing how Sugar is used by students. What is learnt? Survey students and teachers. How well does it deliver its goals.