Difference between revisions of "Activity Library/Editors/Policy/Non-Technical"

From Sugar Labs
Jump to navigation Jump to search
Line 1: Line 1:
  
== Who should be an editor ? ==
+
=== Who should be an editor ? ===
 
 
 
 
 
 
  
 
== Removing, reviewing, removing activities ==
 
== Removing, reviewing, removing activities ==

Revision as of 19:55, 17 February 2011

Who should be an editor ?

Removing, reviewing, removing activities

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


Reasons for removing

  • inappropriate (violent, sexual, subversive) content
  • inappropriate license, see Oversight Board meeting notes for details

Reasons for retaining or moving to the sandbox

  • Any confusion with already-published activities

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

  • Buggy activities

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

A: Contact the maintainer Developer to notify 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)


  • Obvious misuse of categories, e.g., FireFox activity in Teaching tools

A: Contact the uploader to clarify the categories choice.