gathering use cases
tony at olenepal.org
Thu Nov 8 17:10:33 EST 2012
On 11/08/2012 05:01 PM, Jerry Vonau wrote:
> Hi Tony and all,
> On Thu, 2012-11-08 at 13:32 -0500, Tony Anderson wrote:
>> Hi, Sridhar
>> One of the important potential benefits from gathering use cases is to
>> clarify the roles of the Community XS project and XS-0.7.
> Why is that an issue at at all? The "Community XS" (think XS-0.8 here)
> is going to address the current shortcomings of XS-0.7.
This is my greatest concern. The ability of a server to deliver content
is central. It is my understanding that your Community XS does not
support a LAMP stack or Moodle. Please do not refer to the Community XS
as XO-0.8 until there is a chance that it can deliver the essential
capabilities of XS-0.7. My other concern is that a lot of very talented
people are spending a lot of time solving a non-problem.
Naturally, the network problem you mention is solved by connecting the
XS-0.7 to that network as the WAN.
>> From my perspective, if you can afford to deploy a server with 2GB or
>> more main memory and 500GB or more hard drive capacity, XS-0.7 serves
>> well and easily supports adding or customizing services. The
>> configuration shown in SF costs less than $350 and draws 18w (based on
>> measurements taken by George Hunt). With a large hard drive, it is
>> perfectly to keep Moodle even if it is not used.
>> In my experience, the school server is installed in the school ready
>> with XS-07 installed along with the available content. Barring hardware
>> failure, the only interaction at the school is to turn the server on at
>> the start of day and turn it off at the end. With modern computers, both
>> functions require only a push on the power button.
> I'm not thinking about an XO here at all but on a server that you
> spec'd. Tell me how do you deploy the 0.7 version on a network where you
> don't have control over the DNS and have everything work? I have an idea
> on how to pull that off with avahi, I would like to hear about how you
> would implement that situation.
>> Community XS serves a valuable role where only XOs are available or
>> where power constraints are critical. It may also have a role in
>> supporting special network requirements.
> Not to mention better hardware support for the latest hardware available
> and ARM support by using Fedora. You can get on board with the future
> and have a say in your pet interests but please don't get in the way of
> The other XS-CE developer
>> On 11/08/2012 10:55 AM, devel-request at lists.laptop.org wrote:
>>> Message: 2
>>> Date: Thu, 8 Nov 2012 13:57:12 +1100
>>> From: Sridhar Dhanapalan<sridhar at laptop.org.au>
>>> To: Holt<holt at laptop.org>
>>> Cc: Devel's in the Details<devel at lists.laptop.org>, Maryam Rehan El
>>> Baz<melbaz at mail.sfsu.edu>, iaep<iaep at lists.sugarlabs.org>, XS Devel
>>> <server-devel at lists.laptop.org>, Support Gangsters
>>> <support-gang at laptop.org>
>>> Subject: Re: gathering use cases
>>> <CABPDnXn8Xz9BwRD_zy_PUr43CG=_rKXv8u6=zLjD0f+Juk=XEQ at mail.gmail.com>
>>> Content-Type: text/plain; charset=ISO-8859-1
>>> On 3 November 2012 07:46, Holt<holt at laptop.org> wrote:
>>>>> Thanks much Sameer. Am includingsupport-gang at laptop.org to make sure we
>>>>> gather microdeployment and support volunteer feedback too.
>>>>> While our XS Community Edition experiment ain't quite ready for
>>>>> showtime/download yet, its white paper & code repository are here:
>>> The white paper that Adam is referring to can be found at
>>> I am the primary author, but it was written by canvassing feedback and
>>> opinions from schools and XS community members (including Jerry Vonau,
>>> George Hunt, Adam Holt and many others). The paper discusses several
>>> use cases and design goals, and outlines the underlying principles
>>> behind how we do things in OLPC Australia.
>>> There is some miscommunication being spread around that I'd like to
>>> clear up. Firstly, this is not a 'secret' project. The white paper
>>> explains our mission, and the code repo and issues trackers are open.
>>> Secondly, the intent is to create a flexible framework that can be
>>> adapted to suit local needs. This is*not*, as some keep asserting, a
>>> project to have the XS work only on the XO. The community XS will work
>>> on any x86 or ARM based hardware that works with Fedora. The white
>>> paper explains this in depth.
>> Devel mailing list
>> Devel at lists.laptop.org
More information about the Devel