Hi Flavio,<div><br></div><div>I'm not sure what you are flagging as a mistake exactly, there is quite a bit of confusion around android and html5, it means very different things to different people. So it would be good if you could clarify.</div>
<div><br></div><div>And I'm not sure what you are proposing. Certainly everyone in this thread would be glad if the XO development continued as usual, but that's not what seems to be happening, independently from our will.</div>
<div><br></div><div>I'm seeing a lot of educators vs developers rhetoric lately and I don't think it's useful. It would be better if we focused on improving the communication channels. Feedback is not taken in account because it's not heard, most of the time.</div>
<div><br></div><div>I'm just a volunteer trying to help out, one of the many on this list :)</div><div><br>On Tuesday, 5 November 2013, Flavio Danesse wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div>My humble opinion (please stick to one):</div><div><br></div><div>To put into perspective the opinion, I should remember that besides developing for sugar since 2009, I am also a teacher in high school, so I've been inside ceibal classrooms during this time.</div>
<div><br></div><div>From the beginning, I said I saw the fate of sugar linked to the xo, the one without the other does not seem to make sense. Now, OLPC xo 4 and manufactures their away strip.</div><div><br></div><div>For those who did the port to gtk3 last year, and we have also had to deal with the problems of arm processors, etc.. . ., We do not easily see how much time is lost in these "strategic decisions" while it ignores the feedback from deployments.</div>
<div><br></div><div>I think this whole issue of android and html5, is a very grave mistake, probably the last.</div><div><br></div><div>But hey, I'm just a teacher, probably the only one in this list.</div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">2013/11/5 Daniel Narvaez <span dir="ltr"><<a href="javascript:_e({}, 'cvml', 'dwnarvaez@gmail.com');" target="_blank">dwnarvaez@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Oh, awesome, COPR seems to be exactly what we need.<div><div><br><br>On Tuesday, 5 November 2013, Peter Robinson wrote:<br><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Tue, Nov 5, 2013 at 1:40 PM, Daniel Narvaez <<a>dwnarvaez@gmail.com</a>> wrote:<br>
> Going a bit off topic, but a pretty major issue I see in our workflow with<br>
> Fedora is that we don't have a good way to develop unstable Sugar on a<br>
> stable Fedora. Rawhide is, or at least is perceived as, unstable. And I'm<br>
> not sure what would be a good way to, for example, produce and distribute<br>
> 0.100 rpms for Fedora 19. We can setup our custom automated build system and<br>
> repository of course, but I'm not sure that's a good approach? Part of the<br>
> problem here is that upstream tends to depend strongly on very recent<br>
> libraries which are not yet available in the stable fedora, though maybe now<br>
> that the gi conversion is over we can avoid that.<br>
<br>
Actually a lot of that will be solved perfectly with COPR (similar in<br>
style to Ubuntu PPA) which is being worked upon at the moment and it<br>
should solve all the problems you see by enabling newer versions to be<br>
built for older releases while maintaining the stable shipped release<br>
in mainline.<br>
<br>
Peter<br>
<br>
> On Tuesday, 5 November 2013, Peter Robinson wrote:<br>
>><br>
>> On Tue, Nov 5, 2013 at 2:14 AM, Walter Bender <<a>walter.bender@gmail.com</a>><br>
>> wrote:<br>
>> > On Mon, Nov 4, 2013 at 7:42 PM, Daniel Narvaez <<a>dwnarvaez@gmail.com</a>><br>
>> > wrote:<br>
>> >> On 4 November 2013 22:53, Sean DALY <<a>sdaly.be@gmail.com</a>> wrote:<br>
>> >>><br>
>> >>> * It's not clear to me where we are going. The OLPC/Sugar development<br>
>> >>> ecosystem seems to be at a crossroads. I am encouraged by the web<br>
>> >>> activity<br>
>> >>> work, but don't understand the path of transposing the value<br>
>> >>> proposition of<br>
>> >>> Sugar (interface, Journal, collaboration, Activities) to handheld<br>
>> >>> tactile<br>
>> >>> devices (tablets to smartphones). PCs (of any size) with keyboards are<br>
>> >>> no<br>
>> >>> longer competitive with tablets for grade-school classroom use.<br>
>> >>> Perhaps the<br>
>> >>> XO-4 could still be in the running; there is no clear message from<br>
>> >>> OLPC.<br>
>> >><br>
>> >><br>
>> >><br>
>> >> I'll try to express briefly my feelings about the directions the<br>
>> >> project<br>
>> >> could take. Note that I might be missing a lot of what is going on<br>
>> >> above the<br>
>> >> technical level.<br>
>> >><br>
>> >> * The XO is not a viable hardware platform other than for existing<br>
>> >> deployments. OLPC is pretty clearly going in a different direction.<br>
>> ><br>
>> > I may be alone in thinking that there will be some runway left with<br>
>> > the XO. But deployments need alternatives regardless.<br>
>> ><br>
>> >> * Sugar web activities on the top of a full Android loses too much of<br>
>> >> the<br>
>> >> Sugar value proposition. It's great to have it in addition to<br>
>> >> Sugar-the-OS,<br>
>> >> but it's not enough alone.<br>
>> ><br>
>> > I agree.<br>
>> ><br>
>> >> * From the technical point of view there are several ways to get<br>
>> >> Sugar-the-OS running on tactile devices. Unfortunately it's not clear<br>
>> >> to me<br>
>> >> that any of these devices is open enough to be viable for deployments<br>
>> >> or<br>
>> >> "ordinary" users.<br>
>> ><br>
>> > We looked at ChromeOS a few years back, but at the time it was too<br>
>> > heavy for our hardware. Today, it is a different story. Might be a<br>
>> > viable option. Certainly running GNU/Linux/Sugar on a ChromeBook is<br>
>> > not a bad starting point.<br>
>><br>
>> Given that ChromeOS is locked down I don't believe it's viable to ask<br>
>> a School to have to break/hack the HW to get it working OOTB.<br>
>><br>
>> Having been involved in the OLPC OS side of things I believe you would<br>
>> be much better taking the work done by OLPC with things like<br>
>> olpc-os-builder and the work upstream with Fedora to use it to build<br>
>> out OS images that will work in a similar way across both XOs and<br>
>> other HW be it x86 netbook or cheap ARM devices rather than<br>
>> reinventing the wheel!<br></blockquote></div></div>_______________________________________________<br>
Sugar-devel mailing list<br>
<a href="javascript:_e({}, 'cvml', 'Sugar-devel@lists.sugarlabs.org');" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
<br></blockquote></div><br></div>
</blockquote></div><br><br>-- <br>Daniel Narvaez<br><br>