Activity Library/Editors/Policy: Difference between revisions

Line 11:

* Must Start/Stop cleanly

oo When stopping must stop gracefully - not stay in memory.

** When stopping must stop gracefully - not stay in memory.

* CPU and Memory usage

oo Usage must be proportional to functionality

** Usage must be proportional to functionality

oo Must not completely tie up the machine

** Must not completely tie up the machine

* Interface

oo Conform to Sugar standards?

** Conform to Sugar standards?

oo Icons to meet sugar colour guidelines

** Icons to meet sugar colour guidelines

oo Frame key must work from within the activity

** Frame key must work from within the activity

oo Must fit within screen size of the XO’s

** Must fit within screen size of the XO’s

* Journal

oo Is there save functionality and does it interact with the Journal well?

** Is there save functionality and does it interact with the Journal well?

oo Are file types registered with SugarOS correctly?

** Are file types registered with SugarOS correctly?

* Checks

oo Black and white (high contrast screen)

** Black and white (high contrast screen)

oo Sound

** Sound

+ Does sound behave?

# Stutter

# lock up sound card

oo Collaboration

** Collaboration

+ Must work if button is there

+ Maximum number of collaborators

+ Test with 3 or more?

* Bugs (for updated activities)

oo Are there any regressions in old functionality?

** Are there any regressions in old functionality?

oo How functional is new functionality?

** How functional is new functionality?

* Download size of application must be reasonable compared to

oo similar applications

** similar applications

oo functionality

** functionality

* For activities webpage

oo Must have reasonable explanation of purpose for the “more about this activity” field

** Must have reasonable explanation of purpose for the “more about this activity” field

oo Must have release notes

** Must have release notes

oo Must be categorised correctly

** Must be categorised correctly

* Versions of Sugar

oo Do we assume the developer has tested on all versions they say it works on?

** Do we assume the developer has tested on all versions they say it works on?

oo Tester approving activity tests on olpc stable builds?

** Tester approving activity tests on olpc stable builds?

oo Who tests on SoaS and what version?

** Who tests on SoaS and what version?

* Must tell user if the activity is using web? collecting user data?

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