Activity Library/Editors/Policy: Difference between revisions

Line 11:

* Must Start/Stop cleanly

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

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

* CPU and Memory usage

o Usage must be proportional to functionality

oo Usage must be proportional to functionality

o Must not completely tie up the machine

oo Must not completely tie up the machine

* Interface

o Conform to Sugar standards?

oo Conform to Sugar standards?

o Icons to meet sugar colour guidelines

oo Icons to meet sugar colour guidelines

o Frame key must work from within the activity

oo Frame key must work from within the activity

o Must fit within screen size of the XO’s

oo Must fit within screen size of the XO’s

* Journal

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

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

o Are file types registered with SugarOS correctly?

oo Are file types registered with SugarOS correctly?

* Checks

o Black and white (high contrast screen)

oo Black and white (high contrast screen)

o Sound

oo Sound

+ Does sound behave?

# Stutter

# lock up sound card

o Collaboration

oo Collaboration

+ Must work if button is there

+ Maximum number of collaborators

+ Test with 3 or more?

* Bugs (for updated activities)

o Are there any regressions in old functionality?

oo Are there any regressions in old functionality?

o How functional is new functionality?

oo How functional is new functionality?

* Download size of application must be reasonable compared to

o similar applications

oo similar applications

o functionality

oo functionality

* For activities webpage

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

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

o Must have release notes

oo Must have release notes

o Must be categorised correctly

oo Must be categorised correctly

* Versions of Sugar

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

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

o Tester approving activity tests on olpc stable builds?

oo Tester approving activity tests on olpc stable builds?

o Who tests on SoaS and what version?

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