[Sugar-devel] ASLO QA process

[Bernie Innocenti]

El Thu, 29-04-2010 a las 09:54 -0300, Daniel Drake escribió:

> 3. Reproducibility in low-connectivity deployments, or even for cases
> such as paraguay where connectivity is good but going to ASLO will
> really be sloooow and it's much more desirable to set up some simple
> infrastructure to run it within the school. i.e. that simple
> infrastructure needs to be developed and good documentation needs to
> be written.

This is easily done by tuning Squid to cache large files if they
have .xo extensions. The update panel only does one uncachable query to
ASLO.


> (easiest approach for #3: support OLPC activity microformat. clean,
> simple format, well documented, designed for low connectivity
> situations, simple infrastructure is already developed and has been
> replicated around the world.)

I also liked the OLPC microformat a lot more than the as-hoc rpc
protocol provided by ASLO. It was simple to implement with any web
technology, including static html files, wikis and web applications like
ASLO.

ASLO already outputs all the information required by the microformat.
With some luck, it could be implemented without even touching the php
code.

-- 
   // Bernie Innocenti - http://codewiz.org/
 \X/  Sugar Labs       - http://sugarlabs.org/