On Mon, Nov 26, 2012 at 4:53 AM, Bastien <b...@laptop.org> wrote: > Chris Leonard <cjlhomeaddr...@gmail.com> writes: > >> I have found instances of bad compatibility info in ASLO. I asked the >> maintainer about it and they fixed it. > > This is also what I do. > > But we're not all hardcore geeks. Some teachers are being > frustrated by this -- let's also think about "normal" users.
I was not suggesting that such errors were acceptable or to be considered normal, only confirming that they do occur and can be fixed. This sounds like an ideal set of QA task(s) to be written up for GCI. 1) Starting form a given version of Sugar, and given a provided list of activities as defined by ASLO links and version numbers), confirm compatibility as listed on ASLO and provide data for developing a compatibily matrix (version of Sugar versus release number of activity). 2) Highlight instances where the data provided in ASLO is wrong. 2) Define similar tasks for each of several (recent) releases of Sugar. Please write it up on the wiki and we will try to get some GCI contributors to work on it. http://wiki.sugarlabs.org/go/GoogleCodeIn2012/ http://wiki.sugarlabs.org/go/GoogleCodeIn2012/GCI2012_Brainstorming cjl _______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel