<html> <head> <style></style></head> <body class='hmmessage'><div dir='ltr'> <div>Hi Guys and Gals,</div><div><br></div><div>Thanks for all of the good ideas and information to help us do a good job representing OLPC and Sugar Labs at SCaLE 11X. In addition to some local folks who are involved with olpc-SoCal, we will have George Hunt, Tony Anderson, Aaron Borden, Manu Gupta, Ed Bigenho, and myself. The weather this SCaLE weekend, unlike the past couple of years, is going to be beautiful! Maybe we will even have a chance to take an XO-1.75 up to the roof and demo it running without the battery, entirely on solar power!</div><div><br></div>There is one thing I couldn't resist commenting on in this thread. Speaking as an educator, I suggest we not sell the RPi short! With the new emphasis (and rightly so) on STEM (Science, Technology, Engineering, and Math), and given the right curriculum, I can see the RPis as a wonderful tool that teachers and districts are probably going to embrace. Consider the low cost, the ability to use old cast-off keyboards, monitors, and even TVs, the flexibility, the thrill of the student who puts it all together and makes it work to do a task of his choosing... it is hard to beat.<div><br></div><div>I can see a scenario where districts would buy RPi kits for upper grade students to build, and have them build extra ones for the younger ones to run Sugar (or Nell?) on. But still, the Android is also attractive... the devices, although not as STEM oriented, are ubiquitous. What an opportunity to get millions more students using Sugar!</div><div><br></div><div>Caryl<br><br><div><div id="SkyDrivePlaceholder"></div><hr id="stopSpelling">From: sdaly.be@gmail.com<br>Date: Thu, 21 Feb 2013 14:39:17 +0100<br>To: docdtv@gmail.com<br>CC: dwnarvaez@gmail.com; iaep@lists.sugarlabs.org; testing@lists.laptop.org; support-gang@lists.laptop.org<br>Subject: Re: [Testing] [IAEP] Sugar on Android (was Questions for SCaLE 11X)<br><br>The Sugar Labs Oversight Board confirmed Android compatibility as a strategic goal at the January 14 meeting [1].<br><br>It goes without saying that this is far easier said than done.<br><br>There are several technical approaches possible, and coming to a decision how to proceed is itself a challenge.<br> <br>Sean.<br><br>1. <a href="http://wiki.sugarlabs.org/go/Oversight_Board/Meeting_Minutes-2013-01-14" target="_blank">http://wiki.sugarlabs.org/go/Oversight_Board/Meeting_Minutes-2013-01-14</a><br><br><br><br><div class="ecxgmail_quote">On Thu, Feb 21, 2013 at 1:30 PM, Ron Feigenblatt <span dir="ltr"><<a href="mailto:docdtv@gmail.com">docdtv@gmail.com</a>></span> wrote:<br> <blockquote class="ecxgmail_quote" style="border-left:1px #ccc solid;padding-left:1ex"><div class="ecxim">> On 21 February 2013 09:35, Ron Feigenblatt <<a href="mailto:docdtv@gmail.com">docdtv@gmail.com</a>> wrote:<br> >> The big news is that OLPC reports potential buyers have expressed<br> </div>>> interest in Android, so it has a plan to move the XO-4 that way...<br> <div class="ecxim">>> could Sugar sit on top of Android rather than Linux Fedora by then?<br> <br> </div><div class="ecxim">On 2/21/13, Daniel Narvaez <<a href="mailto:dwnarvaez@gmail.com">dwnarvaez@gmail.com</a>> wrote:<br> > I think that's never going to happen unless we come up with a plan.<br> </div>>... I just hope people will realize<br> > that it's urgent to do something about this...<br> <br> Let me hazard mockery by citing a very obvious incentive to getting<br> Sugar to run on Android. If Sugar could be an Android .apk, it could<br> not merely run on some future Android-based OLPC, but on over a<br> million new devices EVERY DAY, closing in on a total of a billion -<br> and be trivial to install in the bargain. Isn't that worth lots more<br> attention than a million Raspberry Pi's, which aren't even full<br> appliances, but merely boards mainly of interest to DIY embedded<br> system guys?<br> <br> Moving to Android would also address OLPC's new Android-tablet line.<br> (Perhaps one might even partner with profit-seeking hardware keyboard<br> aftermarket vendors, by encouraging them to conceptually bundle<br> Sugar.)<br> <br> The game console market has been off-limits to Sugar due to large<br> developer license fees. But what if an Android-based project like the<br> Ouya (cf. <a href="http://en.wikipedia.org/wiki/Ouya" target="_blank">http://en.wikipedia.org/wiki/Ouya</a> ), with zero fees, can<br> prove successful?<br> <br> On the other hand, with limited developer staffing, maybe Sugar Labs<br> should just dig in its heels and concentrate on supporting the nearly<br> 3 million units to which the educational systems of at least two<br> nations have made deep and expensive commitments. Few things have<br> given the information technology industry a worse name than the rate<br> at which it often tries to force users to migrate away from legacy<br> systems, rather than perfect their flaws.<br> <br> The REALLY BIG CHANGE is not from one electronic learning system to a<br> newer one, but from one based on printed matter, blank paper and<br> pencils, to one based on electronics - thereby enabling audio,<br> animation, photography, interactivity, zero-inventory-zero-unit-cost<br> courseware, and total portability.<br> <div class="ecxHOEnZb"><div class="h5">_______________________________________________<br> IAEP -- It's An Education Project (not a laptop project!)<br> <a href="mailto:IAEP@lists.sugarlabs.org">IAEP@lists.sugarlabs.org</a><br> <a href="http://lists.sugarlabs.org/listinfo/iaep" target="_blank">http://lists.sugarlabs.org/listinfo/iaep</a><br> </div></div></blockquote></div><br> <br>_______________________________________________ Testing mailing list Testing@lists.laptop.org http://lists.laptop.org/listinfo/testing</div></div> </div></body> </html>