Activity Library/Editors/Policy

Technical policy
All technical checks will happen automatically while uploading activities.

Guidelines for accepting an activity
--RafaelOrtiz 20:48, 18 February 2011 (EST) We must focus in testing for diferent versions of sugar, olpc. soas an use different sugar versions, generally newer than Sugar 0.82
 * Must Start/Stop cleanly
 * When stopping must stop gracefully - not stay in memory.
 * CPU and Memory usage
 * Usage must be proportional to functionality
 * Must not completely tie up the machine
 * Interface
 * Conform to Sugar standards?
 * Icons to meet sugar colour guidelines
 * Frame key must work from within the activity
 * Must fit within screen size of the XO’s
 * Journal
 * Is there save functionality and does it interact with the Journal well?
 * Are file types registered with SugarOS correctly?
 * Checks
 * Black and white (high contrast screen)
 * Sound
 * Does sound behave?
 * Stutter
 * lock up sound card
 * Collaboration
 * Must work if button is there
 * Maximum number of collaborators
 * Test with 3 or more?
 * Bugs (for updated activities)
 * Are there any regressions in old functionality?
 * How functional is new functionality?
 * Download size of application must be reasonable compared to similar applications
 * functionality
 * For activities webpage
 * Must have reasonable explanation of purpose for the “more about this activity” field
 * Must have release notes
 * Must be categorised correctly
 * Versions of Sugar
 * Do we assume the developer has tested on all versions they say it works on? --RafaelOrtiz 20:48, 18 February 2011 (EST) At least that he sets the flag correctly on ASLO.
 * Tester approving activity tests on olpc stable builds?
 * Who tests on SoaS and what version?
 * Must tell user if the activity is using web? collecting user data?
 * Must have I18n support (i.e gettext generated .POT with ./setup.py genpot)

Sorry, but keeping all these "Must"s, what ASLO is supposed to be? A place to host activities developed by well skilled coders, QAed by well skilled engineers, released by well skilled project managers? Is it about Sugar or something else? If I got Sugar purpose right, Sugar is about learning via doing, it is mostly impossible to do something well formed right after starting. ASLO should respect experimenters and their decision about quality (ready to share) of the code. At the same time, there are bunch of side ways how to mark activities that satisfy all these "Must"s - editors pick up and special collections. alsroot 07:29, 26 September 2011 (EDT)

Resources

 * Original AMO policy