Difference between revisions of "Google Code-In 2012/GCI2012 Brainstorming"
| Line 1: | Line 1: | ||
| − | These are genereal concepts and areas of opportunity from which individual GCI2012 tasks can be developed and submitted. | + | These are genereal concepts and areas of opportunity from which individual GCI2012 tasks can be developed and submitted. We need at least 5 tasks in each category, but beyond tha we can have as many as we can think up. |
The GCI categories are: | The GCI categories are: | ||
Revision as of 23:11, 25 October 2012
These are genereal concepts and areas of opportunity from which individual GCI2012 tasks can be developed and submitted. We need at least 5 tasks in each category, but beyond tha we can have as many as we can think up.
The GCI categories are:
- Code
- Tasks related to writing or refactoring code
- Documentation/Training
- Tasks related to creating/editing documents and helping others learn more
- Outreach/Research
- Tasks related to community management, outreach/marketing, or studying problems and recommending solutions
- 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
1) Activity Rescue.
There are abandoned actvitites tha need to be ported to gtk3 or generally resuscitated. For example, some have been left behind on dev.l.o and not migrated to Sugar Labs hosting.
2) Activity internationalization.
There are a number of activities in ASLO that are either English only or Spanish only. Each one could of these could be listed as an individual task to refactor for i18n and submit for Pootle hosting.
3) Infrastructure tasks
For example, I'll be creating a task for a new pootle-helper script to do msgfmt checks on PO files as part fo our regular Pootle cron jobs to prevent build-breakers in PO files from going un-noticed for more than 24 hours.