Difference between revisions of "Deployment Team/Peru"

From Sugar Labs
Jump to navigation Jump to search
 
(30 intermediate revisions by 3 users not shown)
Line 1: Line 1:
−
{{Draft}}
 
−
 
 
== Summary ==
 
== 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 Peru. This effort is being led by Peru Local Lab. The detailed information (in Spanish) is [http://pe.sugarlabs.org/go/Proyecto_Piloto_Hexoquinasa located] 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 ==
 
== Layers ==
Line 17: Line 15:
 
* schools, one-teacher schools in villages:
 
* schools, one-teacher schools in villages:
 
** laptop per child model;
 
** laptop per child model;
−
** about 10 students of different ages;
+
** about 10-20 students of different ages;
−
** no technical personnel, only teachers with basic computers skills;
+
** lack of technical support, only teachers;
−
** mostly no connectivity;
+
** no connectivity;
 
** only XO laptops, no wireless access points, no dedicated hardware for school servers.
 
** only XO laptops, no wireless access points, no dedicated hardware for school servers.
−
* town schools:
+
* town schools (CRT):
 
** computer labs, not laptop per child, model;
 
** computer labs, not laptop per child, model;
 
** skilled technical personnel;
 
** skilled technical personnel;
Line 29: Line 27:
 
'''Deployment team'''
 
'''Deployment team'''
  
−
Peru Local Lab members.
+
*Aleksey Lim
 +
*Bernie Innocenti
 +
*Chris Leonard
 +
*Juan Camilo Lema
 +
*Koke Contreras
 +
*Laura Vargas
 +
*Sebastian Silva
 +
 
 
<br>''TODO''
 
<br>''TODO''
  
Line 36: Line 41:
 
The rest of Sugar community.
 
The rest of Sugar community.
 
<br>''TODO''
 
<br>''TODO''
 +
 +
== The problem ==
 +
 +
The problems with one-teacher schools are:
 +
 +
* Lack of technical support, only teachers;
 +
* No connectivity;
 +
* Only XO laptops, no wireless access points, no dedicated hardware for school servers to provide additional content;
 +
* No translation to local languages.
 +
 +
References:
 +
 +
* [http://somosazucar.org/2010/11/20/informe-sobre-la-investigacion-de-las-laptop-xo/ Informe sobre la investigaciòn de las laptop XO en el Perú].
 +
* [[Talk:Deployment_Team/Peru/Puno#Visit_to_school_in_Lacachi|Visit to school in Lacachi]]
  
 
== Roles ==
 
== Roles ==
Line 42: Line 61:
  
 
''XO students''
 
''XO students''
−
: Students from one-teacher village schools. They have XOs in personal usage.
+
: Students from one-teacher multi-grade schools. They have XOs in personal usage.
  
 
''XO teachers''
 
''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.
+
: Teachers from one-teacher multi-grade schools. They have XOs in personal usage as well. They are the only who maintain XO related workflows at schools on daily basis.
  
 
''Chaski''
 
''Chaski''
−
: A person who travels around to visit village schools.
+
: Any person who can travel from one-teacher multi-grade schools to an internet access point and back.  
 +
 
 +
''Teachers Trainer''
 +
:
  
 
''Lab students''
 
''Lab students''
Line 56: Line 78:
 
:
 
:
  
−
''CRT''
+
''Network coordinators / Community Managers''
−
: Centros de Recursos Tecnológicos. The centers of qualified software support for the region where it is located. In case of software support, it tends to be as self-sufficient as possible and delegate the work to upper level CRT in the rest cases.
+
* Activate Network
−
 
+
* Merge data
−
''Mothership''
+
* Moderate data
−
: Located in the main CRT. It is intended to centralize all efforts within the deployment that need to be centralized.
+
* Monitor metrics
 +
* Connect downstream needs and upstream implementation
 +
: TODO more specific
  
 
''Upstream''
 
''Upstream''
Line 66: Line 90:
 
: ''TODO'' concretize.
 
: ''TODO'' concretize.
  
−
== Object model ==
+
== Infrastructure ==
 +
 
 +
Major components are:
 +
 
 +
* [[Deployment_Team/Peru/Puno/Sugar_Distribution|SomosAzúcar Sugar Distribution: Hexoquinasa]],
 +
* [[Platform_Team/Sugar_Network|Sugar Network]],
 +
* [[Deployment_Team/Peru/Puno/Teachers_Server|SomosAzúcar Teacher's Server]].
 +
 
 +
They are spread within the [[#Roles|Roles]] as:
  
 
''XO students'' have:
 
''XO students'' have:
−
* ''XO image''<br>Dextrose-3 properly localized;
+
* XO image Hexoquinasa;
−
* ''Activity Library''<br>An application that is intended to concentrate all Sugar activities related behaviour in one place;
+
* [[Platform_Team/Sugar_Network|Sugar Network]] frontend;
 
* ''Statistics'' monitor.
 
* ''Statistics'' monitor.
  
 
''XO teachers'''s XOs operate as school servers and contain:
 
''XO teachers'''s XOs operate as school servers and contain:
 
* Additional storage on SD card;
 
* Additional storage on SD card;
−
* Distributed copy of the ''Wiki'';
+
* School [[Platform_Team/Sugar_Network|Sugar Network]] server;
−
* Distributed copy of the ''Action Tracker'';
 
−
* Distributed copy of the ''Activity Library'';
 
 
* A copy of ''XO updates'' repository;
 
* A copy of ''XO updates'' repository;
−
* ''XO strudents''' ''Statistics'';
 
 
* (?) ''Jabber server'';
 
* (?) ''Jabber server'';
 
* (?) ''Journal backups'';
 
* (?) ''Journal backups'';
 
* (?) ''Anti-thief'' support.
 
* (?) ''Anti-thief'' support.
  
−
''Chaski''
+
''Synchronization USB key''
−
* ''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''
 +
* Trisquel image of Hexoquinasa;
  
 
''Mothership''
 
''Mothership''
−
* Centralized copy of the ''Wiki'';
+
* Center [[Platform_Team/Sugar_Network|Sugar Network]] server;
−
* Centralized copy of the ''Action Tracker'';
 
−
* Centralized copy of the ''Activity Library'';
 
 
* ''XO updates'' repository;
 
* ''XO updates'' repository;
−
* Centralized ''Statistics'' collection;
 
  
−
== Activity ==
+
== Workflows ==
 +
 
 +
These are kinds of workflows that [[#Roles|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 workflows''
 +
: The [[Platform_Team/Sugar_Network#Workflows|workflows]] that relate to Sugar Network.
  
 +
<!--
 
''XO students''
 
''XO students''
 
: Being at school, ''XO students'' can:
 
: Being at school, ''XO students'' can:
 
::* In Browse activity, get access to ''Wiki'' on ''XO teacher'''s server;
 
::* In Browse activity, get access to ''Wiki'' on ''XO teacher'''s server;
−
::* Populate ''Actions tracker'' on ''XO teacher'''s server;
+
::* Populate ''Action Tracker'' on ''XO teacher'''s server;
 
::* In their ''Activity Library'', use all activities hosted on ''XO teacher'''s server;
 
::* In their ''Activity Library'', use all activities hosted on ''XO teacher'''s server;
 
::* Get system updates from ''XO teacher'''s server;
 
::* Get system updates from ''XO teacher'''s server;
Line 115: Line 166:
 
* Brings ''Synchronization USB key'' to a school and plug it into ''XO teacher'''s XO to automatically:
 
* Brings ''Synchronization USB key'' to a school and plug it into ''XO teacher'''s XO to automatically:
 
** Synchronize distributed ''Wiki'' content;
 
** Synchronize distributed ''Wiki'' content;
−
** Synchronize ''Actions tracker'' content;
+
** Synchronize ''Action Tracker'' content;
 
** Synchronize ''Activity Library'' content;
 
** Synchronize ''Activity Library'' content;
 
** Upload new ''XO system updates'';
 
** Upload new ''XO system updates'';
 
** Download collected ''Statistics''.
 
** Download collected ''Statistics''.
 
* Being in the place with good connectivity, plug ''Synchronization USB key'' to any computer with not too old GNU/Linux distribution and run a script from this key to synchronize USB content with the Mothership to be prepared to visit the next school.
 
* Being in the place with good connectivity, plug ''Synchronization USB key'' to any computer with not too old GNU/Linux distribution and run a script from this key to synchronize USB content with the Mothership to be prepared to visit the next school.
 +
-->
 +
== References ==
 +
 +
* [http://sites.google.com/site/nuestrocrt/ Nuestro Centro de Recursos Tecnológicos].
 +
* [http://pe.sugarlabs.org/go/Proyecto_Piloto_Hexoquinasa Proyecto Piloto Hexoquinasa].
  
−
''Mothership''
+
== Subpages ==
−
* Moderate the central ''Wiki'' content, based on collected contributions from schools;
+
 
−
* Moderate ''Actions tracker'' content, based on collected contributions from schools;
+
{{Special:PrefixIndex/Deployment_Team/Peru/Puno/}}
−
* Moderate ''Activity Library'' content, based on collected contributions from schools;
 
−
* Work with ''Upstream'' on solving issues gotten from ''Actions tracker'' and ''Activity Library'';
 
−
* Maintain ''XO system updates'' repository;
 
−
* Maintain gotten ''Statistics'' to share with proper audience.
 

Latest revision as of 00:41, 12 May 2012

Summary

This page is an overview of a pilot program that will happen in 2012 in Peru. This effort is being led by Peru Local Lab. The detailed information (in Spanish) is located on the Peru Local Lab home page. This page also contains technical details of implementation that might be helpful for other deployments.

Layers

Puno-map.png

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-20 students of different ages;
    • lack of technical support, only teachers;
    • no connectivity;
    • only XO laptops, no wireless access points, no dedicated hardware for school servers.
  • town schools (CRT):
    • computer labs, not laptop per child, model;
    • skilled technical personnel;
    • good connectivity;
    • good hardware equipment.

Deployment team

  • Aleksey Lim
  • Bernie Innocenti
  • Chris Leonard
  • Juan Camilo Lema
  • Koke Contreras
  • Laura Vargas
  • Sebastian Silva


TODO

Upstream

The rest of Sugar community.
TODO

The problem

The problems with one-teacher schools are:

  • Lack of technical support, only teachers;
  • No connectivity;
  • Only XO laptops, no wireless access points, no dedicated hardware for school servers to provide additional content;
  • No translation to local languages.

References:

Roles

All involved people might be categorized by the following roles.

XO students

Students from one-teacher multi-grade schools. They have XOs in personal usage.

XO teachers

Teachers from one-teacher multi-grade schools. They have XOs in personal usage as well. They are the only who maintain XO related workflows at schools on daily basis.

Chaski

Any person who can travel from one-teacher multi-grade schools to an internet access point and back.

Teachers Trainer

Lab students

Lab teachers

Network coordinators / Community Managers

  • Activate Network
  • Merge data
  • Moderate data
  • Monitor metrics
  • 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 Hexoquinasa;
  • Sugar Network frontend;
  • Statistics monitor.

XO teachers's XOs operate as school servers and contain:

  • Additional storage on SD card;
  • School Sugar Network server;
  • A copy of XO updates repository;
  • (?) 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

  • Trisquel image of Hexoquinasa;

Mothership

Workflows

These are kinds of workflows 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 workflows

The workflows that relate to Sugar Network.

References

Subpages

Retrieved from "https://wiki.sugarlabs.org/index.php?title=Deployment_Team/Peru&oldid=78339"