Difference between revisions of "Google Code-In 2012"
Jump to navigation
Jump to search
| Line 13: | Line 13: | ||
;Code: Tasks related to writing or refactoring code | ;Code: Tasks related to writing or refactoring code | ||
# New pootle-helper script for doing preventative [[GoogleCodeIn2012/MsgfmtChecker|msgfmt checks]]. | # New pootle-helper script for doing preventative [[GoogleCodeIn2012/MsgfmtChecker|msgfmt checks]]. | ||
| − | # Sugarizing [GoogleCodeIn2012/Virtaal| Virtaal] for L10n "bootstrapping" | + | # Sugarizing [[GoogleCodeIn2012/Virtaal|Virtaal]] for L10n "bootstrapping" |
# | # | ||
# | # | ||
Revision as of 03:35, 26 October 2012
Sugar Labs is applying to Google Code-in for 2012.
TASKS
Please be sure to include at least 5 tasks from each of the 5 categories.
We had a number of tasks listed in our GSOC application.
This brainstorming page lists some geeneral categories from which specific individual tasks can be specified.
- 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
- 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 ???