[Sugar-devel] XO on Fedora 20 (was Re: [GSoC] Porting To Python3)

Daniel Narvaez dwnarvaez at gmail.com
Mon May 12 18:12:16 EDT 2014

On 12 May 2014 21:07, Gonzalo Odiard <godiard at sugarlabs.org> wrote:

> First, thanks for doing this work.
Thanks for helping out.

>  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.
>> * 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.
> This is a issue. If we have a Sugar with similar functionalities
>  (settings and activities installed) we can request help from deployments
> and volunteers.

Are you thinking to deployment specific settings and activities here? Or
some kind of subset/reference that is good enough for all the interested

* 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.

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,
> just configurations.

Yes. I don't really have a strong feeling one way or another. I can send
patches for the generic parts if they are wanted.

I think we also need a place where to put reference configurations. I
initially had put them in olpc-os-builder, numbered as 14.0.0 but that
feels wrong... since no official olpc releases are planned. I suppose I
could edit the examples/f18-[model].ini ones instead, but I would need
access to whatever repository we use to change those without needing review
every time.

> * Are interested deployments using olpc-update? If I'm not mistake AU is
>> not.
> We are not using it. I am pretty sure Nicaragua use it.

Is AU using yum?

> * Do we care about maintaining the GNOME "dual boot"? I'm afraid we do,
>> but I want to make sure.
> Yes. Is a important feature for the deployments. In the end deployments
> don't ask for "Gnome", but for a standard desktop,
> for some cases. If Gnome don't work without acceleration in F20, XFCE,
> mate or similar can work.

I've seen screenshots of GNOME fallback in F20, so I'm hopeful it's still
there. But yeah, in the worst case there are alternatives.

* 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?
> I am not sure if do a complete build for every sugar commit have sense,
> maybe yes do weekly builds, or automatic rpms.

Yeah, weekly images and one rpm per commit was pretty much what I had in
mind. (With yum based updates doing frequent builds is less important by
the way). Well, it's probably good to have one image per commit to the
build configurations repository, but that's different.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.laptop.org/pipermail/devel/attachments/20140513/92f9a59e/attachment.html>

More information about the Devel mailing list