<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I generally think of the olpc mission as:<br>
<br>
Provide a laptop computer to every student at a community school
which is on the wrong side of the digital divide.<br>
<br>
This mission implicitly includes providing a school server as a
means to make some internet content available locally and some <br>
local orientation to teachers and staff to enable effective use of
the computers.<br>
<br>
The OLPC approach was to convince the national Ministry of Education
to provide XOs to every school in a country. However, at our <br>
less exalted olpc level, it has meant school by school. The typical
school deployment has involved a sponsor who provides the funds to <br>
purchase the equipment and a dedicated volunteer to go to the school
and install the equipment and provide the initial orientation. The <br>
sponsor and volunteer typically come from the right side of the
digital divide. <br>
<br>
OLPC came up with the brilliant marketing scheme G1G1. Sadly, the
associated sales campaign was based on the disastrous 'helicopter'
notion that <br>
all that was required was to deliver the computer to the students. <br>
<br>
No effort has ever been directed at community building because the
OLPC model was direct interaction with Ministries. The associated
model of indvidual sponsors (e.g. Rotary Clubs, M+W Groups Care for
Kids, a dedicated former Peace Corps volunteer, or an expatriate
wanting to pay forward) has never been well served. <br>
<br>
I such a sponsor approaches me, the first message is that you can't
just write a check to get laptops. The next is that you will need to
find a well-qualified computer specialist to get the system
installed and set up. Finally, you have to transport the laptops to
the deployment solving problems with customs (I even once had to go
to Rwanda's FCC counterpart to get the XO-1.5 certified).<br>
<br>
For marketing, our objective should be to attract sponsors for
deployments. For this, we need a good story which shows the benefits
of Sugar to improve <br>
the educational opportunity offered by the community school and a
simple process for the sponsor to carry out the deployment. I don't
think we have that story today. <br>
<br>
Naturally, making Sugar visible to a wider population in the
'sponsoring' world is beneficial. Telling the story of working olpc
deployments is important. Having a readily available laptop for
deployment is essential. <br>
<br>
For example, does anyone have current information on the Uruguay
deployment? These students have been using the XO for nearly a
decade. What impact has that had? What needs for Sugar have resulted
from that experience. Does the Sugar community have a deep and
ongoing relationship with Plan Ceibal?<br>
How are they keeping the inventory of XOs viable as the equipment
ages? How has Plan Ceibal handled the transition from primary school
to secondary school, taking advantage of the primary school students
skills and knowledge?<br>
<br>
Tony<br>
<br>
<div class="moz-cite-prefix">On 04/08/2016 07:34 AM, Dave Crossland
wrote:<br>
</div>
<blockquote
cite="mid:CAEozd0ykhzDmqkx0QOQrYF9fLr48s8U8+cc3_LUa9_Fsg4k7TA@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 6 April 2016 at 17:24, Sean DALY <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:sdaly.be@gmail.com" target="_blank">sdaly.be@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div dir="ltr"><span>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Apr 6, 2016 at 5:39
PM, Dave Crossland <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:dave@lab6.com" target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:dave@lab6.com">dave@lab6.com</a></a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px
0px 0px
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div>How many kids is Sugar targetting?</div>
<div><br>
</div>
<div>Low millions? Or billions?</div>
</blockquote>
</div>
<br>
A few years ago, I estimated at around 10 million
the number of teachers in classrooms with younger
children, and I suggested we target them. Any
teacher-friendly, ultrasimple, reliable setup and
maintenance Sugar solution could work towards that
goal. </div>
</span></div>
</blockquote>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div dir="ltr"><span>
<div class="gmail_extra"> </div>
</span></div>
</blockquote>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div dir="ltr"><span>
<div class="gmail_extra">...<br>
</div>
</span>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">In my view Sugarizer has a very
key role to play - overcoming the unfamiliarity
barrier for teachers. Which could, ironically, boost
the opportunities of the Sugar/GNU solutions.<br>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>I agree with all of the above<br>
</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div class="gmail_extra">I do feel that View Source is a
key differentiator of Sugar, and I subscribe to the
"low floor, no ceiling" idea.</div>
</div>
</blockquote>
</div>
<div><br>
I think the fact that "View Source" is a famous web browser
menu item is poignant for this discussion, especially given
the power of the Firebug-style web developer modes of all
the big browsers today.</div>
<div><br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">I
believe the very simplest and most reliable is ...</blockquote>
<div><br>
</div>
<div>I think we ought to think in terms of addressable market,
and for me with that perspective the ranking is,</div>
<div><br>
</div>
<div>Sugarizer in a browser,<br>
</div>
<div><br>
</div>
<div>Sugarizer installed via packages for existing mobile
systems,<br>
</div>
<div><br>
</div>
<div>Sugar/GNU in a VM (which I wonder could be ideally
bundled with VM software and presented as a "desktop app"),<br>
</div>
<div><br>
</div>
<div>Sugar/GNU on a stick,</div>
<div><br>
</div>
<div>Sugar installed via packages for existing GNU systems,</div>
<div>
<div><br>
</div>
<div>Sugarizer/Android preinstalled on hardware<br>
</div>
<div><br>
</div>
<div>Sugar/GNU preinstalled on hardware<br>
</div>
<div><br>
</div>
<div>Sugar/GNU preinstalled on rugged hardware<br>
</div>
</div>
<div><br>
</div>
<div> </div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Sugar-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a>
<a class="moz-txt-link-freetext" href="http://lists.sugarlabs.org/listinfo/sugar-devel">http://lists.sugarlabs.org/listinfo/sugar-devel</a>
</pre>
</blockquote>
<br>
</body>
</html>