On Fri, Sep 05, 2008 at 03:00:35PM -0300, Erik Garrison wrote: > -= Question =- > > How are we planning on obtaining simple information such as [1] > which activities are most used/downloaded, [2] which ones generate > the most data, [3] common software failures, [4] bug manifestation > rate etc.? > > -= Proposal =- > > The diagnostic process could be as simple from the country's perspective > as: > > 1) dropping a USB key containing the system-copier script into the > machine in question booting, and waiting for shutdown, > > 2) then inserting the system-copier key (now containing an image of the > target system) into an XO running an XS build with a diagnostic > script attached, > > 3) which produces a report and automatically sends it to a server on > our end for further analysis. [...] > Thoughts?
How about: 1) Teaching the Sugar Control Panel System updater how to patch Sugar (Glucose) 2) Patching Sugar (Glucose) to collect/maintain [1] and [2] - this feels like a very minor amount of data that are very useful 3) Developing any number of ways to get those data home to 1cc (new XO activity, XS script, USB stick with a collector script that copied the collected data to itself and then was used as in your step #2). I seem to remember a discussion about automatically sending somethign back to 1cc, but I think it was just "before my time". Any pointers to that discussion welcome (so as not to needlessly repeat it...). > Best, > Erik Martin
pgpHCiObHx16l.pgp
Description: PGP signature
_______________________________________________ Devel mailing list [email protected] http://lists.laptop.org/listinfo/devel
