Activity Library/Editors/Policy: Difference between revisions
Sascha silbe (talk | contribs) →Technical policy: make bugs.sugarlabs.org a link |
|||
| Line 17: | Line 17: | ||
* If activity entirely(not just minor glitches like screen resolution) depends on hardware/software properties of particular environment(XO for example), this activity can 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 can 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. | ||
* Check if activity has correct link to bugs tracker | * Check if activity has correct link to bugs tracker | ||
* Check it there is a component for activity on bugs.sugarlabs.org(or whatever was set as bugs tracker), if not, ask uploader about maintainer and create(request for creation) one | * Check it there is a component for activity on [https://bugs.sugarlabs.org/ bugs.sugarlabs.org] (or whatever was set as bugs tracker), if not, ask uploader about maintainer and create(request for creation) one | ||
* For all bugs, that were found during review, create bug tickets | * For all bugs, that were found during review, create bug tickets | ||