Changes

;User Interface: Tasks related to user experience research or user interface design and interaction

;User Interface: Tasks related to user experience research or user interface design and interaction

1) Activity Rescue. 

1) Activity Rescue (code)

There are abandoned activities that need to be ported to gtk3 or generally resuscitated.  For example, some have been left behind on https://dev.laptop.org/git and not migrated to Sugar Labs hosting.  Any migration should include i18n (if not already done).

There are abandoned activities that need to be ported to gtk3 or generally resuscitated.  For example, some have been left behind on https://dev.laptop.org/git and not migrated to Sugar Labs hosting.  Any migration should include i18n (if not already done).

2) Activity internationalization.

2) Activity internationalization (code)

There are a number of activities in [activities.sugarlabs.org 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 [activities.sugarlabs.org 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 (or other) programs.

3) Sugarizing good Python (or other) programs (code)

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.

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.

4) Infrastructure tasks

4) Infrastructure tasks (QA)

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 unnoticed 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 unnoticed for more than 24 hours.

5) GTK-3 conversion

5) GTK-3 conversion (code, documentation)

We have migrated Sugar to GTK-3 and introspection, but many activities still use the old GTK-2 framework. Migrating these activities would help to stabilize our code base and make long-term maintenance more tractable. Any port should include i18n (if not already done).

We have migrated Sugar to GTK-3 and introspection, but many activities still use the old GTK-2 framework. Migrating these activities would help to stabilize our code base and make long-term maintenance more tractable. Any port should include i18n (if not already done). Also writing documentation about Sugar-specific issues with the porting process would be of great benefit. Rewriting out [[Development_Team/Almanac|Sugar Almanac]] to reflect GTK-3 would be a task as well. And updating [http://en.flossmanuals.net/make-your-own-sugar-activities/ Make Your Own Sugar Activities].

[[Category: GCI2012]]

[[Category: GCI2012]]