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, |
− | 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 developer of the activity, this is true for non-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 ==
| |
− | | |
− | Some points that should be considered during activity review, some activities could be removed at all.
| |
| | | |
| + | == Removing, reviewing, sandboxing activities == |
| | | |
| + | 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 === |
| | | |
− | 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. | + | '''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 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. | + | '''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. |