Deployment Team/Peru
|
NOTICE: This page is a draft in active flux... Please contribute to these contents and discuss issues on the discussion page. |
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 home page. This page also contains technical details of implementation that might be helpful for other deployments.
Layers
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 labs, not laptop per child, model;
- skilled technical personnel;
- good connectivity;
- good hardware equipment.
Deployment team
Peru Local Lab members.
TODO
Upstream
The rest of Sugar community.
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.
Teachers Trainer
Lab students
Lab teachers
Network coordinators
- Merge data
- Moderate date
- Connect downstream needs and upstream implementation
- TODO more specific
Upstream
- The rest of Sugar community.
- TODO concretize.
Infrastructure
Major components are:
They are spread within the Roles as:
XO students have:
- XO image of SomosAzúcar Sugar Distribution;
- Activity Library
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 SD card;
- Distributed copy of the Wiki;
- Distributed copy of the Action Tracker;
- Distributed copy of the Activity Library;
- A copy of XO updates repository;
- XO strudents' Statistics;
- (?) Jabber server;
- (?) Journal backups;
- (?) Anti-thief support.
Synchronization USB key
- Sync data as a singular file that might be uploaded in any way,
- the script to upload data,
- Live image to boot to the hw and upload data.
Lab students
- Trisqule image of SomosAzúcar Sugar Distribution;
Mothership
- Centralized copy of the Wiki;
- Centralized copy of the Action Tracker;
- Centralized copy of the Activity Library;
- XO updates repository;
- Centralized Statistics collection;
Activities
These are kinds of activities that Roles can take part in. The particular activity might involve several Players and several Roles.
Synchronization
- A Chaski travels between a school that needs to be synchronized and a place with the connectivity.
- The process is only about carrying the USB key, the rest should be done automatically.
- TODO describe the process.
Training teachers
- A process of teaching XO Teachers to use the system.
- TODO describe the process.
Maintaining the Sugar Network
- Network Coordinators
- TODO describe the process.
- Maintain XO system updates repository;
Sugar Network's activities
- The activities that relate to Sugar Network.