Changes

== 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 [[Activity_Library/Editors/Policy|Policy]].

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]].

* Subscribe to [http://lists.sugarlabs.org/listinfo/aslo editors mailing list] to informed of all review threads

* Subscribe to [http://lists.sugarlabs.org/listinfo/aslo editors mailing list] to informed of all review threads

 

* Follow [[Activity_Library/Editors/Policy|Policy]] while pushing activities to public

* Check that activity runs on declared Sugar Platforms.

**** [[Sugar_on_a_Stick|SoaS-2]] or [[Community/Distributions/Mandriva|Mandriva2009.1]] or [http://en.opensuse.org/Sugar openSUSE] for environments that fully satisfy SP-0.84

** If activity entirely(not just minor glitches like screen resolution) depends on hardware/software properties of particular environment(XO for example), this activity could not be pushed to the public and should be left in [[Glossary#Experimental_activity|Experimental]] stage. In that case editors could collect these activities in collections e.g. "Experimental XO activities" until they are fixed to run in common environment which satisfy Sugar Platform specification.

 

== Hints ==

== Hints ==