1,157
edits
Changes
Jump to navigation
Jump to search
Line 25:
Line 25: + − 3) Infrastructure tasks+ + + + + + +
Google Code-In 2012/GCI2012 Brainstorming (view source)
Revision as of 02:28, 26 October 2012
, 02:28, 26 October 2012no edit summary
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. See [[File:ASLO_spreadheet_Oct_2012.ods]]
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. See [[File:ASLO_spreadheet_Oct_2012.ods]]
3) Sugarizing good Python programs.
There are nice packages out there that could be readily ported to run as Sugar Activities by various means. Identifying a number of candidate packages to be sugarized as a GCI task would enhance the Sugar user experience in ways we have not had adequate time to do.
For example, it would be wonderful to empower "bootstrapping" of L10n on the XO from within Sugar itself by porting a version [http://translate.sourceforge.net/wiki/virtaal/index|Virtaal] as a Sugar Activity capable of reading and writing the PO/MO files already present in the source code (if coupled with glibc locale availability),
4) 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.
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.