Difference between revisions of "Activity Library/Editors"

Latest revision as of 13:08, 30 October 2011

Introduction

The Sugar Activity Library leverages volunteer reviewers/editors to look over pending and nominated activities for publication on the site. With the launch of activities.sugarlabs.org (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 should an editor do?

Subscribe to the editors mailing list to be informed of all review threads.
Follow the Activity Library Policy before pushing activities to the public.

Hints

Q: How does one 'feature' an activity?
A: Go to http://activities.sugarlabs.org/editors/featured

Start typing the activity name (you should type at least 4 characters) to edit the entry which belongs to the proper category.
Choose the full activity name from the popup list,
or enter the activity id in this format: [<activity_id>]

Resources

@@ Line 1: / Line 1: @@
-{{TOCright}}
 == 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.
+The Sugar Activity Library leverages volunteer reviewers/editors to look over pending and nominated activities for publication on the site. With the launch of [http://activities.sugarlabs.org activities.sugarlabs.org] (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 [[Activity_Library/Editors/Policy Policy]].
-== What editor should do? ==
+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 [[Activity_Library/Editors/Policy|Policy]].
-* Subscribe to broadcast events to handle all nominating/pending requests:
+== What should an editor do? ==
-** go to [http://activities.sugarlabs.org/en-US/sugar/users/edit Account page]
-** switch to ''Notifications'' tab
-** select ''Broadcast events'' check box
-* Check that activity runs on declared Sugar Platforms.
+* Subscribe to the [http://lists.sugarlabs.org/listinfo/aslo editors mailing list] to be informed of all review threads.
-** Major sugar environments are:
+* Follow the [[Activity_Library/Editors/Policy|Activity Library Policy]] before pushing activities to the public.
-*** SP-0.82
-**** [http://download.laptop.org/xo-1/os/official/767/ XO-767]
-*** SP-0.84
-**** [[Sugar_on_a_Stick|SoaS-2]] or [[Community/Distributions/Mandriva|Mandriva2009.1]] or [http://en.opensuse.org/Sugar 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.
-* 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<br>
+'''Q:''' How does one 'feature' an activity?<br>
-'''A:''' go to http://activities.sugarlabs.org/editors/featured
+'''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
+# Start typing the activity name (you should type at least 4 characters) to edit the entry which belongs to the proper category.
-# choose full activity name from popup list
+# Choose the full activity name from the popup list,
-# or type activity id in format: ''[<activity_id>]''
+# or enter the activity id in this format: ''[<activity_id>]''
 == Resources ==