5,705
edits
Changes
Jump to navigation
Jump to search
Line 8:
Line 8: − + Line 15:
Line 15: +
Activity Library/Editors/Policy (view source)
Revision as of 11:54, 7 March 2010
, 11:54, 7 March 2010→Additional technical policy for editors
* ''license'' activity.info field value has short names that conform fedora good licences lists: [http://fedoraproject.org/wiki/Licensing#Good_Licenses software], [http://fedoraproject.org/wiki/Licensing#Good_Licenses_2 documentation] and [http://fedoraproject.org/wiki/Licensing#Good_Licenses_3 content].
* ''license'' activity.info field value has short names that conform fedora good licences lists: [http://fedoraproject.org/wiki/Licensing#Good_Licenses software], [http://fedoraproject.org/wiki/Licensing#Good_Licenses_2 documentation] and [http://fedoraproject.org/wiki/Licensing#Good_Licenses_3 content].
== Additional technical policy for editors ==
== Technical policy ==
* Check that activity runs on declared Sugar Platforms.<br>Major sugar environments are [[Development Team/Packaging]]
* Check that activity runs on declared Sugar Platforms.<br>Major sugar environments are [[Development Team/Packaging]]
** x86_64 architecture (looks like we have x86_64 only for SP-0.84+)
** 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 [[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 it there is a component for activity on bugs.sugarlabs.org, if not, ask uploader about maintainer and create(request for creation) one
* For all bugs that were found during review
* For all bugs that were found during review
** create tickets on http://bugs.sugarlabs.org/ for component ActivityTeam
** create tickets on http://bugs.sugarlabs.org/ for component ActivityTeam