Changes

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

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

== Removing, reviewing, removing activities ==

== Removing, reviewing, sandboxing activities ==

Some points that should be considered during activity review, some activities could be removed at all.

Some points that should be considered during activity review, some activities may be entirely removed.

* inappropriate (violent, sexual, subversive) content

* inappropriate (violent, sexual, subversive) content

* inappropriate license, see Oversight Board [[Oversight_Board/Meeting_Minutes-2009-12-11#Non-FOSS_content|meeting notes]] for details

* inappropriate license, see Oversight Board [[Oversight_Board/Meeting_Minutes-2009-12-11#Non-FOSS_content|meeting notes]] for details.

=== Reasons for keeping or moving to the Sandbox ===

=== Reasons for keeping or moving to the Sandbox ===

Activities that are experimental are keeped in Activity's Library sandbox (i.e only registered users can download them)

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'''<br>

* '''Any confusion with already-published activities'''<br>

'''A''': Make difference more clear, obvious renaming, making notice in description, not launching activity, etc.  

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

* '''Buggy activities'''<br>

* '''Buggy activities'''<br>

If the activity is proving to not start or is having serious functionality problems, it should be retained and/or moved to the sandbox.

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

'''A''': Contact the maintainer Developer to notify the issue.

'''A''': 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.<br>[[User:Alsroot|alsroot]] 07:32, 25 October 2010 (EDT)

** 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.<br>[[User:Alsroot|alsroot]] 07:32, 25 October 2010 (EDT)