Difference between revisions of "Activity Library/Editors/Policy/Non-Technical"
< Activity Library | Editors | Policy
Jump to navigation
Jump to search
RafaelOrtiz (talk | contribs) |
(not sure what retained means in this context) |
||
| Line 1: | Line 1: | ||
| − | |||
=== Who should be an editor ? === | === Who should be an editor ? === | ||
| Line 14: | Line 13: | ||
=== Reasons for retaining or moving to the sandbox === | === Reasons for retaining or moving to the sandbox === | ||
| − | + | : 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> | ||
| Line 20: | Line 19: | ||
* '''Buggy activities'''<br> | * '''Buggy activities'''<br> | ||
| − | If the activity is proving not | + | If the activity is proving to not start or is having serious functionality problems, it should be retained and/or moved to the sandbox. |
'''A''': Contact the maintainer Developer to notify the issue. | '''A''': Contact the maintainer Developer to notify the issue. | ||
| Line 27: | Line 26: | ||
* '''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 | + | '''A''': Contact the uploader to clarify the category choice. |
Revision as of 21:07, 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
- Please define retaining in this context. Is it locked from distribution, but kept on server? --FGrose 20:07, 17 February 2011 (EST)
- 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 to not start or is having serious functionality problems, it should be retained and/or moved to the 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)
- 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.
- Obvious misuse of categories, e.g., FireFox activity in Teaching tools
A: Contact the uploader to clarify the category choice.