Changes

=== Who can be an editor ? ===

=== Who can be an editor ? ===

Any sugar learner should and can be an editor of the Activity Library,  

Any sugar learner should and can be an editor of the Activity Library,  

== Removing, reviewing, sandboxing activities ==

== Removing, reviewing, sandboxing activities ==

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

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

 

 

=== Reasons for removing ===

=== Reasons for removing ===

* 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/2009/Meeting_Log-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 ===

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

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

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

'''Action''': 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 moved to the sandbox or removed.

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 or Developer to notify them of the issue.

'''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.<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)

* '''Obvious misuse of categories, e.g., FireFox activity in Teaching tools'''<br>

* '''Obvious misuse of categories, e.g., FireFox activity in Teaching tools'''<br>

'''A''': Contact the uploader to clarify the category choice.

'''Action''': Contact the uploader to clarify the category choice.