<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, May 12, 2014 at 3:02 PM, Daniel Narvaez <span dir="ltr"><<a href="mailto:dwnarvaez@gmail.com" target="_blank">dwnarvaez@gmail.com</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div><div>Hello,<br><br> </div>things are looking good so far, we already have all the models booting into sugar 0.101 with wif apparentlyi working. </div></div></div></div></div></div></blockquote><div><br></div><div>First, thanks for doing this work. </div> <div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><div><div> <div> <div>I would like to take a step back and understand a bit better where we want to go with this. Some random thoughts and questions.<br> <br>* To really understand how much work is left I think we need some good testing, especially on the hardware related bits. I expect there will be lots of small things to fix, but it would be good to understand as early as possible if there are roadblocks. I'm a bad tester and I've never used the XO much, so I'm often not sure what is a regression and what is not... thus helping with this would be particularly appreciated.<br> </div></div></div></div></div></div></blockquote><div><br></div><div>This is a issue. If we have a Sugar with similar functionalities (settings and activities installed) we can request help from deployments and volunteers. </div> <div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div> </div>* Which deployments are planning to ship 0.102 soon and hence are interested in this work? I know of AU. Maybe Uruguay?<br></div></div></div></div></div></blockquote><div><br></div><div>AU sure, if w don't have serious regressions. We need ask to Uruguay. Other deployments usually update slowly.</div> <div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><div><div><div></div><div> * Do we need to support all the XO models?<br></div></div></div></div></div></blockquote><div><br></div><div>In a ideal world, that would make our life easier, we can define a eond of line to our support of F18. </div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><div><div><div></div>* Should we contribute the olpc-os-builder changes back to OLPC or fork it? I don't know if OLPC will do any active development on the linux side of things, if not maybe better to turn this into a sugarlabs thing.<br> </div></div></div></div></blockquote><div><br></div><div>Probably James would know better respect of this issue. The changes we did for AU are in a fork [1], but are not low level stuff,</div><div>just configurations.</div> <div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><div><div> </div>* Are interested deployments using olpc-update? If I'm not mistake AU is not.<br></div></div></div></blockquote><div><br></div><div>We are not using it. I am pretty sure Nicaragua use it.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"> <div dir="ltr"><div><div></div>* Do we care about maintaining the GNOME "dual boot"? I'm afraid we do, but I want to make sure.<br></div></div></blockquote><div><br></div><div>Yes. Is a important feature for the deployments. In the end deployments don't ask for "Gnome", but for a standard desktop,</div> <div>for some cases. If Gnome don't work without acceleration in F20, XFCE, mate or similar can work.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"> <div dir="ltr"><div></div>* As I mentioned in some other thread I'm interested in setting up automated builds from sugar master. I have some vague plan of what it would look like and wrote bits of it. The basic idea is that you would push changes to github and get images automatically built. I think this is good for upstream testing but the same infrastructure could be used by deployments. Are people interested in using this?<br> </div> </blockquote></div><br>I am not sure if do a complete build for every sugar commit have sense, maybe yes do weekly builds, or automatic rpms. </div><div class="gmail_extra">The deployments usually make their own customizations, and will deploy one or two images in a year.</div> <div class="gmail_extra"><div><br></div>-- <br><div dir="ltr">Gonzalo Odiard<br><br><div>SugarLabs - Software for children learning <br></div><div><br></div><div>[1] <a href="https://github.com/godiard/olpc-os-builder/tree/au1b" target="_blank">https://github.com/godiard/olpc-os-builder/tree/au1b</a></div> </div> </div></div>