Activity Library/Editors/Policy
< Activity Library | Editors
Revision as of 09:48, 15 November 2009 by Alsroot (talk | contribs) (→Additional technical policy for editors)
ASLO auto checking
- unique bundle_id activity.info field value
- unique name activity.info field value
- unique icon activity.info image file
- license activity.info field value has short names that conform fedora good licences lists: software, documentation and content.
Additional technical policy for editors
- Check that activity runs on declared Sugar Platforms. Major sugar environments are [Team/Packaging]
- 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 can not be pushed to the public and should be left in 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.
Non-technical policy
- ...
Resources
- Original AMO policy