[IAEP] [Server-devel] gathering use cases

[Dr. Gerald Ardito]

Sameer,

Thanks for doing this work.
Here are some thoughts In the deployment I have been managing we have used
the server in two ways:
1. As a jabber server only. We have about 140 XO-1s, and without the jabber
server, the cross-talk slowed down the devices dramatically when more than
about 30 were running simultaneously.

2. As a wireless network access point. This was especially important in the
dark times before our school reconfigured our wireless network to work
properly with the XOs.

When we began, Moodle was less important to us, but now that I have been
Moodle with my 7th and 8th grade students (who are not using the XOs), I
can see the benefit of using it with an XO deployment.

I hope this is helpful.

Thanks again.
Gerald


On Sat, Nov 3, 2012 at 12:07 AM, Chris Leonard <cjlhomeaddress at gmail.com>wrote:

> Sameer,
>
> You should talk to SomosAzucar and Aleksey Lim about the use case for
> Sugar Network being developed for a pilot in LimaNorte.
>
> cjl
>
> On Fri, Nov 2, 2012 at 4:15 PM, Sameer Verma <sverma at sfsu.edu> wrote:
> > There are several use cases that may or may not get addressed when
> designing
> > a particular software stack to address a requirement.
> >
> > The XS 0.7 is designed to be a single image install and comes with
> Moodle.
> > Given that I work with Moodle everyday, I see the pros and cons of it
> being
> > central on the XS. I am in fact fairly happy with its current design, but
> > also realize that it was built for a specific use case or three that OLPC
> > needed at the time.
> >
> > There is also an effort (currently dubbed XS Community Edition) that is
> > attempting to address certain other use cases where Moodle and other
> > services could possibly become optional. We saw this at the OLPC SF
> > Community Summit. I hope it will grow up to be the next XS (but that's
> > another thread).
> >
> > My concern is that perhaps, if we don't do our homework right, we will
> once
> > again build something that will fail to address a use case or two. Can
> one
> > design address all use cases? Maybe not. But it's good to know what those
> > use cases are.
> >
> > To this end, I would like to collect data on different possible use cases
> > from all kinds of deployments. I have a student (cc'd) who is working on
> > this project currently. She will gather data from various deployments
> > (suitcase, boutique, MoE etc) as much as possible (with the cooperation
> of
> > projects, of course) and write a report on what we see out there. We'll
> > gladly make the report available once it is done.
> >
> > Is this useful?
> >
> > What should the scope be? Initially I had thought of the server side, but
> > that may be limiting. What should we gather?
> > Location, school, size, personnel, skills, electricity, Internet access,
> > language, sugar version, ...
> >
> > Feedback?
> >
> > cheers,
> > Sameer
> > --
> > Sameer Verma, Ph.D.
> > Professor, Information Systems
> > San Francisco State University
> > http://verma.sfsu.edu/
> > http://commons.sfsu.edu/
> > http://olpcsf.org/
> > http://olpcjamaica.org.jm/
> >
> > _______________________________________________
> > Devel mailing list
> > Devel at lists.laptop.org
> > http://lists.laptop.org/listinfo/devel
> >
> _______________________________________________
> Server-devel mailing list
> Server-devel at lists.laptop.org
> http://lists.laptop.org/listinfo/server-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/iaep/attachments/20121103/470321c7/attachment.html>