Activity Library/Editors
Introduction
ASLO leverages volunteer reviewers/editors to look over pending and nominated add-ons for publication on the site. With the launch of ASLO and the sandbox, aspects of this role have changed significantly.
In ASLO, anyone is considered a reviewer. Users can install activities as soon as the author submits them. We hope that these users will then return to write a review of their experience with the activity, whether it be good or bad.
What's an editor?
Editors have access to the queue of pending and nominated activities, and their main role is to assess the existing reviews and determine whether the activity should be pushed to the public side based on criteria in the Policy.
What editor should do?
- Subscribe to editors mailing list to informed of all review threads
- Check that activity runs on declared Sugar Platforms.
- Major sugar environments are:
- SP-0.82
- SP-0.84
- SoaS-2 or Mandriva2009.1 or openSUSE for environments that fully satisfy SP-0.84
- If activity has binary blobs, check it on:
- x86 architecture
- x86_64 architecture (looks like we have x86_64 only for SP-0.84+)
- If activity entirely(not just minor glitches like screen resolution) depends on hardware/software properties of particular environment(XO for example), this activity could not be pushed to the public and should be left in Experimental stage. In that case editors could collect these activities in collections e.g. "Experimental XO activities" until they are fixed to run in common environment which satisfy Sugar Platform specification.
- Major sugar environments are:
- For all bugs that were found during review
- create tickets on http://dev.sugarlabs.org/ for component ActivityTeam
- mention all found tickets in review comments(in place editable response string is in progress)
Hints
Q: How to feature activity
A: go to http://activities.sugarlabs.org/editors/featured
- start typing activity name(you should type at least 4 symbols) to edit entry which belongs to proper category
- choose full activity name from popup list
- or type activity id in format: [<activity_id>]