5,705
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
no edit summary
{{Draft}}
== Summary ==
This page is an overview of a pilot program that will happen in 2012 in Puno region of Peru. This effort is being led by Peru Local Lab. The detailed information (in Spanish) will be shared on the Peru Local Lab [http://pe.sugarlabs.org/ home page]. This page also contains technical details of implementation that might be helpful for other deployments.
This page is an overview of a pilot program that will happen in 2012 in Puno region of Peru. This effort is being led by Peru Local Lab. The detailed information (in Spanish) will be shared on the Peru Local Lab [http://pe.sugarlabs.org/ home page]. This page also contains technical details of implementation that might be helpful for other deployments.
== Layers ==
[[File:puno-map.png|right]]
The whole picture is split into three layers: Schools, Deployment team, Upstream. The current section briefly characterize all of them.
'''Schools'''
The are two types of schools:
* schools, one-teacher schools in villages:
** laptop per child model;
** about 10 students of different ages;
** no technical personnel, only teachers with basic computers skills;
** mostly no connectivity;
** only XO laptops, no wireless access points, no dedicated hardware for school servers.
* town schools:
** computer classes, not laptop per child, model;
** skilled technical personnel;
** good connectivity;
** good hardware equipment.
'''Deployment team'''
Peru Local Lab members.
<br>''TODO''
'''Upstream'''
The rest of Sugar community.
<br>''TODO''
== Roles ==
All involved people might be categorized by the following roles.
''XO students''
: Students from one-teacher village schools. They have XOs in personal usage.
''XO teachers''
: Teachers from one-teacher village schools. They have XOs in personal usage as well. They are the only who maintain XO related workflows at schools on daily basis.
''Chaski''
: A person who travels around to visit village schools.
''Lab students''
:
''Lab teachers''
:
''CRT''
: Centros de Recursos Tecnológicos. The rest of deployment team.
: ''TODO'' concretize.
''Upstream''
: The rest of Sugar community.
: ''TODO'' concretize.
== Object model ==
''XO students'' have:
* ''XO image''<br>Dextrose-3 properly localized
* ''Activity Library''<br>An application that is intended to concentrate all Sugar activities related behaviour in one place.
* ''Statistics'' monitor
''XO teachers'''s XOs operate as school servers and contain:
* Additional storage on CD card
* ''Wiki''
* ''Actions tracker''
* ''Activity Library'' hosting
* ''XO system updates''
* ''Statistics'' collector
* (?) ''Jabber server''
* (?) ''Journal backups''
''Chaski''
* ''Synchronization USB key''
== Activity ==
''XO students''
: Being at school, ''XO students'' can:
::* Browse ''Wiki'' from ''XO teacher'''s server
::* Populate ''Actions tracker'' on ''XO teacher'''s server
::* Use all activities hosted on ''XO teacher'''s server
::* Get system updates from ''XO teacher'''s server
::* Send statistics to ''XO teacher'''s server
::* (?) Collaborate on ''XO teacher'''s jabber server
::* (?) Do Journal backups to ''XO teacher'''s server
: Being at home, ''XO students'' can:
::* Open objects downloaded from the ''Wiki'' to Journal
::* Use activities cached on a XO
''XO teachers''
* ''XO teachers'''s XO serve ''XO stidents'' around.
''Chaski''
* Brings ''Synchronization USB key'' to a school and plug it into ''XO teacher'''s XO to automatically:
** Synchronize ''Wiki'' content,
** Synchronize ''Actions tracker'' content,
** Synchronize ''Activity Library'' content,
** Upload new ''XO system updates'',
** Download collected ''Statistics''.