<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi,<br>
<br>
A server provides services to client computers. These services
enable and shape the interaction of users with the client. For
example, web pages are delivered to the user by a browser.
However, the web pages are delivered to the browser by a service
on the server side, e.g. Apache. <br>
<br>
Suppose that a deployment wants email capability (a use case). The
standard server side service is pop3 and smtp. Thunderbird is a
possible client-side application for these services.<br>
Most discussions on the lists are based on direct login to gmail
which does not requires only httpd (Apache) on the server side.
However, this means that email access only when the XO is
connected to the internet. A client-side email client could enable
email to be prepared offline and to be read offline. How would
email capability be provided by sneaker-net with a usb drive, e.g.
for someone to periodically take the usb key to an internet cafe
and send/receive email?<br>
<br>
Tony<br>
<br>
<br>
On 11/09/2012 12:09 AM, Sameer Verma wrote:<br>
</div>
<blockquote
cite="mid:CAFoGK8HDjRH=m5ibv9Cb=r=3+H9jpJCSBv3u=h+kGH94HqhXWw@mail.gmail.com"
type="cite">To clarify, by use case, we mean a way to describe the
interaction of people with a system. In this case, it may be how a
child interacts with the XO, and the XS (via XO) or how a teacher
may interact with the XS (via XO or otherwise) by using Moodle. <br>
<br>
As you may have noticed, pretty much every response on this thread
focuses on the system, with the assumption that the user end of it
is understood well. I am not so sure. <br>
<br>
Take a look at <a moz-do-not-send="true"
href="http://www.gatherspace.com/static/use_case_example.html">http://www.gatherspace.com/static/use_case_example.html</a>
to see if it helps you understand the idea behind use cases and
user stories. <br>
<br>
Here's another example of how use cases can vary by being very
high level (which is what we are aiming for) and can be user
centric or system centric. <a moz-do-not-send="true"
href="http://www.agilemodeling.com/artifacts/systemUseCase.htm">http://www.agilemodeling.com/artifacts/systemUseCase.htm</a><br>
<br>
Our focus is user centric, in a way where we would like to
describe the actors (children, parents, teachers, admin, etc) and
their actions (access class information, read books, send email)
without the XS as the focus. Networking topology, storage, UI,
LMS, DNS, etc. should flow from the storytelling exercise. <br>
<br>
We are a bunch of technologists and it is easy to get carried away
by designing from the tech and not the user end. Sometimes that
misses the mark. We may build it and they may not come.<br>
<br>
cheers,<br>
Sameer<br>
<div class="gmail_extra">
<br>
<br>
<div class="gmail_quote">On Thu, Nov 8, 2012 at 4:07 PM, Sridhar
Dhanapalan <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:sridhar@laptop.org.au" target="_blank">sridhar@laptop.org.au</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div class="im">On 9 November 2012 10:19, Tony Anderson <<a
moz-do-not-send="true" href="mailto:tony@olenepal.org">tony@olenepal.org</a>>
wrote:<br>
> Hi, Sridhar<br>
><br>
> Thanks for the clarification. I guess I was mislead
by statements such as:<br>
><br>
> The platform for the One Network server is an
ARMv7-based XO, running the<br>
> One Education OS (based on OLPC OS). This makes
development, and deployment<br>
> and support far simpler than a standalone
distribution. The OS can be<br>
> extended with server capabilities using a bootable
USB Customisation Stick<br>
> (offline) or yum.<br>
><br>
> Please accept my apology if any statement I have made
seemed uncivil, that<br>
> was certainly not my intention. Communicating by
email in certainly much<br>
> more hazardous in this regard than face-to-face.<br>
<br>
</div>
Thank you, Tony. I was quite careful to take your needs into
account<br>
when I wrote the design doc, so I had trouble understanding
your<br>
opposition to the idea.<br>
<br>
Maybe we can make the doc clearer somehow? I structured it
as:<br>
<br>
1. context<br>
2. Community XS design<br>
3. One Network server<br>
<br>
The Community XS design itself is flexible enough to handle
a variety<br>
of different deployments' needs. One Network server is
merely one<br>
configuration of the Community XS, mentioned as an example
of what can<br>
be done.<br>
<div class="im"><br>
<br>
> Just as the deployments you are supporting have
specific and urgent needs,<br>
> so do the ones I am working with. I don't believe
either of us is pursuing<br>
> personal desires. We certainly can easily differ on
which is the appropriate<br>
> technical approach to solving the problems of a
deployment.<br>
<br>
</div>
I think we generally want the same thing in the end. I'm
happy to<br>
continue the conversation to improve the design and
implementation. I<br>
sincerely believe that this design can accommodate your
needs.<br>
<div class="im"><br>
<br>
> I really appreciate this specification:<br>
><br>
><br>
> * this is a flexible design, built on Fedora<br>
> * it will run anywhere where x86 or ARM Fedora will
work<br>
> * it can be installed on top of an existing Fedora
installation<br>
> using 'yum groupinstall xsce'<br>
> * being designed in this way provides extreme
flexibility for deployments<br>
> * all current features of the XS (Moodle, etc.)
will be ported, but<br>
> will be optional<br>
> * installation and configuration will be easy, but
sysadmins will be<br>
> able to treat it like any Fedora installation<br>
<br>
</div>
Awesome. I hope this also satisfies your desire to have it
rebased to<br>
Fedora to work on ARM systems. That's a key goal of this
project,<br>
while maintaining compatibility with x86.<br>
<div class="im"><br>
<br>
> There is clearly a great deal to be gained by a
community taking<br>
> responsibility for the ongoing development and
maintenance of the school<br>
> server as neither Daniel Drake nor Martin Langhoff
are likely to have<br>
> adequate time for this in the foreseeable future.<br>
<br>
</div>
Indeed. A motivating factor was to take some of the load off
some of<br>
these prolific people and spread it out to the community in
a<br>
sustainable way.<br>
<br>
<br>
Cheers,<br>
<div class="">
<div class="h5">Sridhar<br>
_______________________________________________<br>
Devel mailing list<br>
<a moz-do-not-send="true"
href="mailto:Devel@lists.laptop.org">Devel@lists.laptop.org</a><br>
<a moz-do-not-send="true"
href="http://lists.laptop.org/listinfo/devel"
target="_blank">http://lists.laptop.org/listinfo/devel</a><br>
<br>
<br>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<br>
<br>
</div>
</blockquote>
<br>
</body>
</html>