Activity Library/Editors/Policy/Non-Technical - Revision history

FGrose: categorize

2011-11-01T15:12:20Z

categorize

← Older revision		Revision as of 11:12, 1 November 2011
Line 1:		Line 1:
			<noinclude>[[Category:Policy]]</noinclude>
	=== 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,

FGrose: update link to Oversight Board notes

2011-09-15T20:00:08Z

update link to Oversight Board notes

← Older revision		Revision as of 16:00, 15 September 2011
Line 18:		Line 18:

	* 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 ===

RafaelOrtiz: /* Reasons for keeping or moving to the Sandbox */

2011-02-23T17:47:56Z

Reasons for keeping or moving to the Sandbox

← Older revision		Revision as of 13:47, 23 February 2011
Line 26:		Line 26:
	* '''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.

RafaelOrtiz: /* Removing, reviewing, sandboxing activities */

2011-02-19T01:40:52Z

Removing, reviewing, sandboxing activities

← Older revision		Revision as of 21:40, 18 February 2011
Line 13:		Line 13:
	== 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/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 ===

FGrose at 00:22, 19 February 2011

2011-02-19T00:22:00Z

← Older revision		Revision as of 20:22, 18 February 2011
Line 1:		Line 1:
	=== 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,
	we only advise that the editor can't be the ~~same~~ developer of the activity, this is ~~truth~~ for ~~not~~-trusted activities. (see definitions bellow)		we only advise that the editor can't be the developer of the activity, this is true for non-trusted activities. (see definitions bellow)

	* ''Trusted Activities''		* ''Trusted Activities''

Tabitha: /* Who can be an editor ? */

2011-02-19T00:19:42Z

Who can be an editor ?

← Older revision		Revision as of 20:19, 18 February 2011
Line 1:		Line 1:
	=== 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,
	we only ~~advice~~ that the editor can't be the same developer of the activity, this is truth for not-trusted activities. (see definitions bellow)		we only advise that the editor can't be the same developer of the activity, this is truth for not-trusted activities. (see definitions bellow)

	* ''Trusted Activities''		* ''Trusted Activities''

FGrose at 04:27, 18 February 2011

2011-02-18T04:27:38Z

← Older revision		Revision as of 00:27, 18 February 2011
Line 11:		Line 11:
	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.


Line 20:		Line 20:

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

	~~: Please define retaining in this context. Is it locked from distribution, but kept on server? --[[User:FGrose\|FGrose]] 20:07, 17 February 2011 (EST)~~
	* '''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)

RafaelOrtiz: /* Who can be an editor ? */

2011-02-18T04:17:56Z

Who can be an editor ?

← Older revision		Revision as of 00:17, 18 February 2011
Line 3:		Line 3:
	we only advice that the editor can't be the same developer of the activity, this is truth for not-trusted activities. (see definitions bellow)		we only advice that the editor can't be the same developer of the activity, this is truth for not-trusted activities. (see definitions bellow)

	* Trusted Activities		* ''Trusted Activities''
	These are activities that don't need an editor approval for publicize new updated versions.		These are activities that don't need an editor approval for publicize new updated versions.

	* Not-trusted Activities		* ''Not-trusted Activities''
	These are activities that need an editor approval in order to publicize new updated versions of the activities		These are activities that need an editor approval in order to publicize new updated versions of the activities

	Maintained activities are entitled to be trusted, and all activities that fulfill technical and non-~~tecnical~~ 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, removing activities ==

RafaelOrtiz: /* Who can be an editor ? */

2011-02-18T04:16:44Z

Who can be an editor ?

← Older revision		Revision as of 00:16, 18 February 2011
Line 4:		Line 4:

	* Trusted Activities		* Trusted Activities
	These are activities that don't need an editor approval for publicize new updated versions.		These are activities that don't need an editor approval for publicize new updated versions.

	* Not-trusted Activities		* Not-trusted Activities
	These are activities that need an editor approval in order to publicize new updated versions of the activities		These are activities that need an editor approval in order to publicize new updated versions of the activities

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

	== Removing, reviewing, removing activities ==		== Removing, reviewing, removing activities ==

RafaelOrtiz: draft

2011-02-18T04:15:58Z

draft

← Older revision		Revision as of 00:15, 18 February 2011
Line 1:		Line 1:
	=== Who ~~should~~ be an editor ? ===		=== Who can be an editor ? ===
			Any sugar learner should and can be an editor of the Activity Library,
			we only advice that the editor can't be the same developer of the activity, this is truth for not-trusted activities. (see definitions bellow)

			* Trusted Activities
			These are activities that don't need an editor approval for publicize new updated versions.

			* Not-trusted Activities
			These are activities that need an editor approval in order to publicize new updated versions of the activities

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

	== Removing, reviewing, removing activities ==		== Removing, reviewing, removing activities ==