5,705
edits
Changes
Activity Library/Editors/Policy (view source)
Revision as of 06:29, 26 September 2011
, 06:29, 26 September 2011→Guidelines for accepting an activity
* Must have I18n support (i.e gettext generated .POT with ./setup.py genpot)
* Must have I18n support (i.e gettext generated .POT with ./setup.py genpot)
--[[User:RafaelOrtiz|RafaelOrtiz]] 20:48, 18 February 2011 (EST) We must focus in testing for diferent versions of sugar, olpc. soas an use different sugar versions, generally newer than Sugar 0.82
--[[User:RafaelOrtiz|RafaelOrtiz]] 20:48, 18 February 2011 (EST) We must focus in testing for diferent versions of sugar, olpc. soas an use different sugar versions, generally newer than Sugar 0.82
----
Sorry, but keeping all these "Must"s, what ASLO is supposed to be? A place to host activities developed by well skilled coders, QAed by well skilled engineers, released by well skilled project managers? Is it about Sugar or something else? If I got Sugar purpose right, Sugar is about learning via doing, it is mostly impossible to do something well formed right after starting. ASLO should respect experimenters and their decision about quality (ready to share) of the code. At the same time, there are bunch of side ways how to mark activities that satisfy all these "Must"s - editors pick up and special collections. [[User:Alsroot|alsroot]] 07:29, 26 September 2011 (EDT)
== Non-technical policy ==
== Non-technical policy ==