There are roughly 58 million primary school students in Latin America, according to UNESCO’s latest dataÂ from theirÂ Education For AllÂ initiative. Â 5% of children in that age range are not in school. Â And 5% of them use XOs: 1.5 million children have their own, and Peru’s urban initiative is giving another 1.5 million students in urban schools access to XOs through a program where groups of 3-5 students share a laptop.
Today 4/5 of these students are in Uruguay, Peru, Argentina, and Mexico. Â But new programs are growing rapidly, inÂ Nicaragua,Â Costa Rica,Â Colombia, and elsewhere.
That’s a lot of budding Pythonistas, Scratcheros, and Linux users!
Now if only my own home country would start providing computers and connectivity to its students as a matter of course…
cscott just rejoined our team from distant lands, to much rejoicing.Â His first blog post covers his work this month to explore of software development paths for the XO-3. Welcome back!
Last Monday I rejoined One Laptop Per Child as Director, New Technologies. My mandate is hardware and software for the XO-3, OLPC’s upcoming ARM-based tablet computer for education in the developing world. The new machine should be lower cost, lower power, more indestructible, more powerful, and potentially more expandable than ever. There are about two million machines in the XO-1 family (XO-1, XO-1.5) in the hands of kids today. The XO-3 will build upon this impressive foundation to reach further into the poorest and least-connected regions of the world.
I will kick-off my work with a series of four week-long sprints between now and eduJAM Uruguay to investigate possible directions for the educational software stack on the XO-3 tablet. On the XO-1 machines, OLPC ships Sugar, an impressive collection of educational software developed by Sugar Labs. How can we keep the best of Sugar while yanking the UI forward into a touch-friendly tablet world?
This week (April 4-8) I’ll begin by working on a port of the GTK3 UI library to Android. The GTK3 library contains touch support missing from the GTK2 library (on which Sugar is currently based). The goal here is a port of the Python/GTK-based Sugar APIs, running on something like the Honeycomb Android OS.Â Existing educational activities could be ported to new APIs without much difficulty, but we’d largely use existing Android OS facilities instead of Sugar’s low-level system management.Â This is a preliminary explorationâ€”we haven’t decided to base tablet software on Android (or anything else) yet.
The week of April 11-15 I will start porting Python/GTK3 to Chrome or ChromeOS via the Google NativeClient plugin. This path would result in activities which more fully integrate with web technologiesâ€”even in disconnected regions of the world. On desktop machines, Sugar activities could run inside the Chrome browser, while ChromeOS (or another embedded OS running chrome/webkit) would provide system management functions on tablets like the XO-3. As with the Android port, this is exploration, not a definite software direction.
The week of April 18-22 I hope to focus on mesh networking. This has a checkered history in our deployments; I hope to identify remaining roadblocks and map a way forward to make this a flagship feature of the XO-3.
The week of April 25-29 is for the existing Python-based Sugar codebase. To continue moving forward, it needs to migrate to GTK3, gobject-introspection, and other key enabling technologies. It would also benefit from language-independent APIs and better modularization, to allow a more incremental migration path.
The following week is Conozco Uruguayand theUruguay EduJAM â€” where I’ll present progress on these exploratory projects and discuss the path ahead with the OLPC and Sugar communities.Â A week is not enough time to finish any of these projects! But the focused effort should help to identify the promise, roadblocks, and challenges in each path, which will help us plan the future.