Activity Library/Editors/Policy/Non-Technical

Who can be an editor ?
Any sugar learner should and can be an editor of the Activity Library, we only advise that the editor can't be the developer of the activity, this is true for non-trusted activities. (see definitions bellow)

These are activities that don't need an editor approval for publicize new updated versions.
 * Trusted Activities

These are activities that need an editor approval in order to publicize new updated versions of the activities
 * Not-trusted Activities

Maintained activities are entitled to be trusted, and all activities that fulfill technical and non-technical policies can be trusted.

Removing, reviewing, sandboxing activities
Some points that should be considered during activity review, some activities might be entirely removed.

Reasons for removing

 * Inappropriate (violent, sexual, subversive) content
 * Inappropriate license, see Oversight Board meeting notes for details.

Reasons for keeping or moving to the Sandbox
Activities that are experimental are kept in Activity's Library sandbox (i.e., only registered users can download them).


 * Any confusion with already-published activities

Action: Make the difference more clear, by obvious renaming, providing notice in the description, or not launching activity, etc.

If the activity is proving to not start or is having serious functionality problems, it should be moved to the sandbox or removed.
 * Buggy activities

Action: Contact the maintainer or Developer to notify them of the issue.


 * At the same time we should stimulate experiments, changing existing activities and, very importantly, sharing results of these experiments. A new ASLO code base might support having several implementations ("forks" might be too hard a word for them) of the same activity. Need to think how this can be achieved. alsroot 07:32, 25 October 2010 (EDT)

Action: Contact the uploader to clarify the category choice.
 * Obvious misuse of categories, e.g., FireFox activity in Teaching tools