Activity Library/Editors - Revision history

FGrose at 18:08, 30 October 2011

2011-10-30T18:08:37Z

← Older revision		Revision as of 14:08, 30 October 2011
Line 1:		Line 1:
	== Introduction ==		== Introduction ==
	The Sugar Activity Library leverages volunteer reviewers/editors to look over pending and nominated ~~add-ons~~ for publication on the site. With the launch of [http://activities.sugarlabs.org activities.sugarlabs.org] (ASLO) and the sandbox, aspects of this role have changed significantly.		The Sugar Activity Library leverages volunteer reviewers/editors to look over pending and nominated activities for publication on the site. With the launch of [http://activities.sugarlabs.org activities.sugarlabs.org] (ASLO) and the sandbox, aspects of this role have changed significantly.

	In ASLO, anyone is considered a reviewer. Users can install activities as soon as the author submits them. We hope that these users will then return to write a review of their experience with the activity, whether it be good or bad.		In ASLO, anyone is considered a reviewer. Users can install activities as soon as the author submits them. We hope that these users will then return to write a review of their experience with the activity, whether it be good or bad.

FGrose at 18:07, 30 October 2011

2011-10-30T18:07:22Z

← Older revision		Revision as of 14:07, 30 October 2011
Line 1:		Line 1:
	~~{{TOCright}}~~
	== Introduction ==		== Introduction ==
	~~ASLO~~ leverages volunteer reviewers/editors to look over pending and nominated add-ons for publication on the site. With the launch of ASLO and the sandbox, aspects of this role have changed significantly.		The Sugar Activity Library leverages volunteer reviewers/editors to look over pending and nominated add-ons for publication on the site. With the launch of [http://activities.sugarlabs.org activities.sugarlabs.org] (ASLO) and the sandbox, aspects of this role have changed significantly.

	In ASLO, anyone is considered a reviewer. Users can install activities as soon as the author submits them. We hope that these users will then return to write a review of their experience with the activity, whether it be good or bad.		In ASLO, anyone is considered a reviewer. Users can install activities as soon as the author submits them. We hope that these users will then return to write a review of their experience with the activity, whether it be good or bad.
Line 9:		Line 8:
	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]].

	== What editor ~~should~~ do? ==		== What should an editor do? ==

	* Subscribe to [http://lists.sugarlabs.org/listinfo/aslo editors mailing list] to informed of all review threads		* Subscribe to the [http://lists.sugarlabs.org/listinfo/aslo editors mailing list] to be informed of all review threads.
	* Follow [[Activity_Library/Editors/Policy\|Policy]] ~~while~~ pushing activities to public		* Follow the [[Activity_Library/Editors/Policy\|Activity Library Policy]] before pushing activities to the public.

	== Hints ==		== Hints ==

	'''Q:''' How to feature activity<br>		'''Q:''' How does one 'feature' an activity?<br>
	'''A:''' go to http://activities.sugarlabs.org/editors/featured		'''A:''' Go to http://activities.sugarlabs.org/editors/featured
	# ~~start~~ typing activity name(you should type at least 4 ~~symbols~~) to edit entry which belongs to proper category		# Start typing the activity name (you should type at least 4 characters) to edit the entry which belongs to the proper category.
	# ~~choose~~ full activity name from popup list		# Choose the full activity name from the popup list,
	# or ~~type~~ activity id in format: ''[<activity_id>]''		# or enter the activity id in this format: ''[<activity_id>]''

	== Resources ==		== Resources ==

Alsroot at 13:53, 15 November 2009

2009-11-15T13:53:39Z

← Older revision		Revision as of 09:53, 15 November 2009
Line 6:		Line 6:

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

Line 11:		Line 12:

	* 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.~~
	** Major sugar environments are:
	*** SP-0.82
	**** [http://download.laptop.org/xo-1/os/official/767/ XO-767]
	*** SP-0.84
	**** [[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 has binary blobs, check it on:
	*** x86 architecture
	*** x86_64 architecture (looks like we have x86_64 only for 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.

	* For all bugs that were found during review
	** create tickets on http://dev.sugarlabs.org/ for component ActivityTeam
	** mention all found tickets in review comments(in place editable response string is in progress)

	== Hints ==		== Hints ==

Alsroot: /* What editor should do? */

2009-11-15T13:45:13Z

What editor should do?

← Older revision		Revision as of 09:45, 15 November 2009
Line 10:		Line 10:
	== What editor should do? ==		== What editor should do? ==

	* Subscribe ~~to broadcast events to handle all nominating/pending requests:~~		* Subscribe to [http://lists.sugarlabs.org/listinfo/aslo editors mailing list] to informed of all review threads
	** go to [http://~~activities~~.sugarlabs.org/~~en-US/sugar/users~~/~~edit Account page~~]
	** switch to ~~''Notifications'' tab~~
	** select ''Broadcast events'' check box

	* Check that activity runs on declared Sugar Platforms.		* Check that activity runs on declared Sugar Platforms.

Alsroot: /* What's an editor? */

2009-11-15T13:43:48Z

What's an editor?

← Older revision		Revision as of 09:43, 15 November 2009
Line 6:		Line 6:

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

	== What editor should do? ==		== What editor should do? ==

Alsroot: /* What's an editor? */

2009-11-15T13:43:21Z

What's an editor?

← Older revision		Revision as of 09:43, 15 November 2009
Line 6:		Line 6:

	== 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 [~~http:~~//~~activities.sugarlabs.org/pages/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]].

	== What editor should do? ==		== What editor should do? ==

Alsroot: /* Hints */

2009-09-15T08:31:38Z

Hints

← Older revision		Revision as of 04:31, 15 September 2009
Line 33:		Line 33:

	'''Q:''' How to feature activity<br>		'''Q:''' How to feature activity<br>
	'''A:''' go to http://activities.sugarlabs.org~~/en-US~~/editors/featured		'''A:''' go to http://activities.sugarlabs.org/editors/featured
	# start typing activity name(you should type at least 4 symbols) to edit entry which belongs to proper category		# start typing activity name(you should type at least 4 symbols) to edit entry which belongs to proper category
	# choose full activity name from popup list		# choose full activity name from popup list

Alsroot: /* Hints */

2009-09-15T08:30:57Z

Hints

← Older revision		Revision as of 04:30, 15 September 2009
Line 36:		Line 36:
	# start typing activity name(you should type at least 4 symbols) to edit entry which belongs to proper category		# start typing activity name(you should type at least 4 symbols) to edit entry which belongs to proper category
	# choose full activity name from popup list		# choose full activity name from popup list
	# or ~~just time~~ activity id in format: ''[<activity_id>]'' ~~(in current version there is a bug and you'll have to refresh page to see name of added activity)~~		# or type activity id in format: ''[<activity_id>]''
	~~In current version to see all featured activities you should click "See All Recommended Activities" on the right sidebar of category page.~~

	== Resources ==		== Resources ==

Alsroot: /* What editor should do? */

2009-09-15T08:28:29Z

What editor should do?

← Older revision		Revision as of 04:28, 15 September 2009
Line 24:		Line 24:
	*** x86 architecture		*** x86 architecture
	*** x86_64 architecture (looks like we have x86_64 only for SP-0.84+)		*** x86_64 architecture (looks like we have x86_64 only for 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.		** 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.

	* For all bugs that were found during review		* For all bugs that were found during review

Alsroot: /* What editor should do? */

2009-09-15T08:27:02Z

What editor should do?

← Older revision		Revision as of 04:27, 15 September 2009
Line 25:		Line 25:
	*** x86_64 architecture (looks like we have x86_64 only for SP-0.84+)		*** x86_64 architecture (looks like we have x86_64 only for 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.		** 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.

			* For all bugs that were found during review
			** create tickets on http://dev.sugarlabs.org/ for component ActivityTeam
			** mention all found tickets in review comments(in place editable response string is in progress)

	== Hints ==		== Hints ==