57
edits
Changes
Jump to navigation
Jump to search
Line 59:
Line 59: + + + + + + + + + + + + + + +
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
Visual improvements on some of the flagship activities such as enhancing the display with new graphics, visual aids functionality and improved sound effects.
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]]