[IAEP] [Sugar-devel] Xoos Special Interest Group

[David Farning]

The core focus of the Sig is to be an upstream for the the deployment releases.

My guess is that while the project is not identical to either Sugar on
a Stick, or Martin's work on making the sugar on a Stick run on the
XO, we will have a very significant code overlap.

I am planning on starting from Steven M. Parrish's F11 on XO1.5 tree
and seeing what happens.

david

On Fri, Oct 2, 2009 at 5:04 PM, Sebastian Dziallas <sebastian at when.com> wrote:
> David Farning wrote:
>>
>> As promised, we have started work on the XO operating system SIG at
>> Sugar Labs.  The SIG pages are at http://wiki.sugarlabs.org/go/Xoos .
>>
>> Based on feedback from the current developers working in this space,
>> the most valuable starting point will be to start making daily Xoos
>> builds.  The next step will be to work with others in this space to
>> create a release cycle which includes alphas, betas, and final
>> releases.  These releases will enable more users and testers to
>> participate in the development cycle.
>
> Martin Dengler has been incredibly pushing an effort to make SoaS run on the
> XO. In fact, for some time now, the "normal" SoaS builds and the SoaS-XO
> builds are using the same code-base. The plan was and is to build and
> announce these snapshots jointly in the very near future. Setting up a cron
> job to have builds should probably be not too hard...
>
> There has even been a feature proposal for that in Launchpad:
> https://blueprints.launchpad.net/soas/+spec/joint-soas-release
>
> Will this SIG's work be incorporated in the SoaS-XO files (I can't even
> speak of GIT branches anymore, because it's all in mainline now, which is
> just awesome!) or will it create another solution?
>
> --Sebastian
>
>> Initially, communication will happen on the devel at lists.laptop.org,
>> sugar-dev at lists.sugarlabs.org, and fedora-olpc-list at redhat.com mailing
>> lists.
>>
>> We have received initial support from the OLPC contributor program in
>> the form of developer machines.
>>
>> david
>