Hi Anish,<br><br>that's interesting.<br><br>First impressions from a quick look. There isn't really much documentation so I won't promise this is fully accurate :)<br><br>Ubuntu is running in a chroot on the top of a modified android kernel. That's a bit of an hack and I wouldn't recommend it if we had to maintain the thing. Though having a company, and another community, deal with the mess makes it more viable.<br>
<br>They don't have X11 but apparently they ported gtk3 to mir. So at least gtk activities should be fine. It's not possible to run Android applications along linux ones but an OLPC like dual desktop thing might be possible in the future.<br>
<br>I think this should be investigated. It might be possible to run Sugar on it without major modifications.<br><br><div class="gmail_quote">On 13 April 2013 00:28, Anish Mangal <span dir="ltr"><<a href="mailto:anish@sugarlabs.org" target="_blank">anish@sugarlabs.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Daniel, et. al.,<div><br></div><div>Do you think Ubuntu could be an (easier) option for sugar to piggyback upon...</div>
<div><br></div><div>This is not a because-i-think-ubuntu-is-cool opinion, but testament to the fact that canonical have been working to get ubuntu running on tablets and smartphones. </div>
<div><br></div><div><a href="https://wiki.ubuntu.com/Nexus7/Installation" target="_blank">https://wiki.ubuntu.com/Nexus7/Installation</a></div><div><br></div><div>Even I'm not sold on the idea, but I guess it should be part a discussion and research efforts concerning sugar's future.</div>
<div><br></div><div>Best,</div><div>Anish<br><br><div class="gmail_quote"><div><div class="h5">On Fri, Apr 12, 2013 at 6:09 PM, Daniel Narvaez <span dir="ltr"><<a href="mailto:dwnarvaez@gmail.com" target="_blank">dwnarvaez@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div>On 12 April 2013 22:52, Sean DALY <span dir="ltr"><<a href="mailto:sdaly.be@gmail.com" target="_blank">sdaly.be@gmail.com</a>></span> wrote:<br>
</div><div class="gmail_quote"><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">The initial work seems very encouraging, yet it seems Sugar Labs doesn't currently have the resources to make an Android offer available anytime soon. But: now is the time. I believe fundraising is vital to achieve this goal, at the very least to facilitate face to face Sugar Camps for the community. I have ideas how to go about this, but I agree the community needs to be clear about where we are going. An Android offer would of course be of great interest to OLPC.
</div></blockquote></div><div><br>To be completely honest, I think a migration to HTML/Android is never going to happen unless someone invests in it *and* the community rallies around that effort.<br><br>Even a small team of experienced, full time developers could lay the framework foundations. And then writing enough activities for the framework to be of any interest would take a *lot* of work from the community.<br>
<br>But are there the conditions for that to happen? <br><br></div><div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>
</div><div>There are also initiatives we could take to multiply the size of the community. In particular, support for the Raspberry Pi (which has topped 1 million units in sales - half of these since September -, is shipped without an OS, and is arriving in junior high and high school computer science classes) could be an ideal "OEM" platform for Sugar.</div>
</div></blockquote></div><div><br>I also see Raspberry PI as a tempting opportunity. Though I think there is some conflict between trying to extend the reach of the current platform and bootstrapping a new one.<br><br><br>
I think it's important for people to understand that porting to Android is not really porting but a full rewrite. We can reuse designs, artwork, ideas and some of the experience we made so far, but no code at all.<br>
</div></div>
<br></div></div>_______________________________________________<br>
IAEP -- It's An Education Project (not a laptop project!)<br>
<a href="mailto:IAEP@lists.sugarlabs.org" target="_blank">IAEP@lists.sugarlabs.org</a><br>
<a href="http://lists.sugarlabs.org/listinfo/iaep" target="_blank">http://lists.sugarlabs.org/listinfo/iaep</a><span class="HOEnZb"><font color="#888888"><br></font></span></blockquote></div><span class="HOEnZb"><font color="#888888"><br>
<br clear="all"><div><br></div>-- <br>Anish | <a href="mailto:anish@sugarlabs.org" target="_blank">anish@sugarlabs.org</a>
</font></span></div>
</blockquote></div><br><br clear="all"><br>-- <br>Daniel Narvaez<br>