71
edits
Changes
Activity Library/Editors/Policy (view source)
Revision as of 19:25, 18 February 2011
, 19:25, 18 February 2011→Guidelines for accepting an activity
* Must Start/Stop cleanly
* Must Start/Stop cleanly
oo When stopping must stop gracefully - not stay in memory.
* CPU and Memory usage
* CPU and Memory usage
oo Usage must be proportional to functionality
oo Must not completely tie up the machine
* Interface
* Interface
oo Conform to Sugar standards?
oo Icons to meet sugar colour guidelines
oo Frame key must work from within the activity
oo Must fit within screen size of the XO’s
* Journal
* Journal
oo Is there save functionality and does it interact with the Journal well?
oo Are file types registered with SugarOS correctly?
* Checks
* Checks
oo Black and white (high contrast screen)
oo Sound
+ Does sound behave?
+ Does sound behave?
# Stutter
# Stutter
# lock up sound card
# lock up sound card
oo Collaboration
+ Must work if button is there
+ Must work if button is there
+ Maximum number of collaborators
+ Maximum number of collaborators
+ Test with 3 or more?
+ Test with 3 or more?
* Bugs (for updated activities)
* Bugs (for updated activities)
oo Are there any regressions in old functionality?
oo How functional is new functionality?
* Download size of application must be reasonable compared to
* Download size of application must be reasonable compared to
oo similar applications
oo functionality
* For activities webpage
* For activities webpage
oo Must have reasonable explanation of purpose for the “more about this activity” field
oo Must have release notes
oo Must be categorised correctly
* Versions of Sugar
* Versions of Sugar
oo Do we assume the developer has tested on all versions they say it works on?
oo Tester approving activity tests on olpc stable builds?
oo Who tests on SoaS and what version?
* Must tell user if the activity is using web? collecting user data?
* Must tell user if the activity is using web? collecting user data?