Difference between revisions of "Activity Library/Editors"

Revision as of 02:15, 27 July 2009

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 broadcast events to handle all nominating/pending requests:
- go to Account page
- switch to Notifications tab
- select Broadcast events check box

Check that activity runs on declared Sugar Platforms.
- Major sugar environments are:
  - SP-0.82
    - XO-767
  - 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 [[Glossary#Experimental_activity|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.

Hints

Q: How to feature activity
A: go to http://activities.sugarlabs.org/en-US/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 just time activity id in format: [<activity_id>] (in current version there is a bug and you'll have to refresh page to see name of added activity)

In current version to see all featured activities you should click "See All Recommended Activities" on the right sidebar of category page.

Resources

@@ Line 24: / Line 24: @@
 *** 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 [[Glossary#Experimental_activity|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.
 == Hints ==