57
edits
Changes
Google Code-In 2012/GCI2012 Brainstorming (view source)
Revision as of 10:43, 26 November 2012
, 10:43, 26 November 2012Add an idea about testing Activities' compatibility against various versions of Sugar
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 that we can have as many as we can think up.
These are general 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 that we can have as many as we can think up.
The GCI categories are:
The GCI categories are:
;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
Examples of tasks created by other organizations participating in GCI2011 can be found here:
http://www.google-melange.com/gci/homepage/google/gci2011
=== Your ideas here ===
=== Your ideas here ===
1) Activity Rescue (code)
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). The spreadsheet linked below would be a good place to look for specific activities from ASLO.
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]]
This idea is being fleshed out so it can be broken into individual taks on this page [[Google_Code-In_2012/Activity_i18n]].
We are also migrating to Gstreamer 1.0, which better supports introspection. Lots of coding to be done to refactor existing programs. Also documentation about Sugar-specific issues.
We are also migrating to Gstreamer 1.0, which better supports introspection. Lots of coding to be done to refactor existing programs. Also documentation about Sugar-specific issues.
7) User eXperience (code, documentation)
Visual improvements on some of the flagship activities such as enhancing the display with new graphics, visual aids functionality and improved sound effects.
8) Wiki clean up (documentation)
see http://pe.sugarlabs.org/go/Wiki_Clean_Up
9) Systematically test compatibility of Activities given for various versions of Sugar
When browsing http://activities.sugarlabs.org with the Browse activity, Activities are filtered by compatible versions. I.e. you are be automatically exposed to the version of the activity that is running fine on your system. But this is not always the case, either because an Activity developer/maintainer gave a wrong compatibility information, or because some other issue.
The task is to (1) list versions of Sugar that needs to be tested for this (high priority first - e.g. Sugar on a Stick could be high on that list) and (2) test the most popular activities for these versions.
When problems are encountered: 1) describe the problem (activity freezes, activity crash, etc.); 2) try to fix it; 3) report to the maintainer and the sugar-devel mailing list.
The benefit for Sugar is to fix problems in this area. The benefit for the student is to draft and refine the testing procedure.
[[Category: GCI2012]]
[[Category: GCI2012]]