gathering use cases
tony at olenepal.org
Thu Nov 8 18:19:10 EST 2012
Thanks for the clarification. I guess I was mislead by statements such as:
The platform for the One Network server is an ARMv7-based XO, running
the One Education OS (based on OLPC OS). This makes development, and
deployment and support far simpler than a standalone distribution. The
OS can be extended with server capabilities using a bootable USB
Customisation Stick (offline) or yum.
Please accept my apology if any statement I have made seemed uncivil,
that was certainly not my intention. Communicating by email in certainly
much more hazardous in this regard than face-to-face.
Just as the deployments you are supporting have specific and urgent
needs, so do the ones I am working with. I don't believe either of us is
pursuing personal desires. We certainly can easily differ on which is
the appropriate technical approach to solving the problems of a deployment.
I really appreciate this specification:
* this is a flexible design, built on Fedora
* it will run anywhere where x86 or ARM Fedora will work
* it can be installed on top of an existing Fedora installation
using 'yum groupinstall xsce'
* being designed in this way provides extreme flexibility for deployments
* all current features of the XS (Moodle, etc.) will be ported, but
will be optional
* installation and configuration will be easy, but sysadmins will be
able to treat it like any Fedora installation
There is clearly a great deal to be gained by a community taking responsibility for the ongoing development and maintenance of the school server as neither Daniel Drake nor Martin Langhoff are likely to have adequate time for this in the foreseeable future.
On 11/08/2012 05:59 PM, Sridhar Dhanapalan wrote:
> On 9 November 2012 09:10, Tony Anderson <tony at olenepal.org> wrote:
>> 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.
> It appears that no matter what we say, you are cemented in some
> strange notions about the community XS:
> * that it is intended to run only on XOs
> * that it cannot (and will not) serve content
> * that your personal desires from an XS are shared by every other
> deployment in the world
> I think we've been quite clear about what we're intending to achieve.
> If you're going to criticise, at least be civil enough to do so based
> on the facts:
> * this is a flexible design, built on Fedora
> * it will run anywhere where x86 or ARM Fedora will work
> * it can be installed on top of an existing Fedora installation
> using 'yum groupinstall xsce'
> * being designed in this way provides extreme flexibility for deployments
> * all current features of the XS (Moodle, etc.) will be ported, but
> will be optional
> * installation and configuration will be easy, but sysadmins will be
> able to treat it like any Fedora installation
> We've tried hard to be inclusive and constructive. I ask you to do the same.
More information about the Devel