Difference between revisions of "Activity Library/Editors"
Jump to navigation
Jump to search
(→Hints) |
|||
| (21 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
== Introduction == | == 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 [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. | 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? == | == 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 [http:// | + | |
| + | 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 should an editor do? == | ||
| + | |||
| + | * Subscribe to the [http://lists.sugarlabs.org/listinfo/aslo editors mailing list] to be informed of all review threads. | ||
| + | * Follow the [[Activity_Library/Editors/Policy|Activity Library Policy]] before pushing activities to the public. | ||
== Hints == | == Hints == | ||
| − | '''Q:''' How | + | '''Q:''' How does one 'feature' an activity?<br> |
| − | '''A:''' | + | '''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 | + | # or enter the activity id in this format: ''[<activity_id>]'' |
| − | |||
== Resources == | == Resources == | ||
| Line 27: | Line 31: | ||
* [http://activities.sugarlabs.org/pages/policy Add-on Policy] (on ASLO) | * [http://activities.sugarlabs.org/pages/policy Add-on Policy] (on ASLO) | ||
* [http://activities.sugarlabs.org/pages/sandbox Sandbox Information] (on ASLO) | * [http://activities.sugarlabs.org/pages/sandbox Sandbox Information] (on ASLO) | ||
| + | |||
| + | [[Category:Activity Library]] | ||
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>]