Talk:Deployment Guide

Jump to: navigation, search

I wonder where I can see the stages of XO deployment all in one place. What I mean is, Where did they go first, and how many? How many countries now, and how many kids own them?

Some day I will find the time to update the map... Uruguay has been rolling out in rural communities since last November; Peru is just starting—with a target of reaching 6000 one-room school houses in the most rural regions by Q3 2008; Mexico is just gearing up, as is Mongolia, Haiti, etc. --Walter 12:02, 21 March 2008 (EDT)
Walter, I believe that you need to hire some staff. We have been getting conflicting stories about the Mexican purchase and deployment. Where is the straight story on this Wiki? How many units, on what schedule?--Mokurai 20:21, 24 March 2008 (EDT)
Not sure how staffing and rumor control are correlated. 50K laptops to Mexico; deployment starts soon. --Walter 20:44, 24 March 2008 (EDT)

A Spanish version of the deployment guide would be very useful. There was a question about buying laptops from an NGO in Argentina. --Cbigenho23:26, March 24 2008 (PDT)

FYI, we are trying to work out a related algorithm for deployment decisions, mostly related to infrastructure and the school server.

Preliminary ideas are posted at:


Gregorio 09:24, 27 March 2008 (EDT)


This is clearly intended to be read sequentially, so I'm going to add Next Section links at the bottom of each sub-page to improve read-through navigation. This will work for every page but Glossary, so I'll leave that one out. Cjl 20:49, 26 March 2008 (EDT)

It would work for Glossary if I made a Deployment Guide/Glossary page with Deployment Guide header and footer with the body of Glossary as a transcluded page. I'll put an example of this at Deployment Guide/Glossary/temp to test the transclusion formatting. I have not linked it into the navigation yet. Cjl 19:04, 31 March 2008 (EDT)

Good idea. I think should work by inclusion. If it doesn't work, try making the Glossary a subpage like the others and then use a redirect from the original. --Walter 19:06, 31 March 2008 (EDT)

The result is not exactly as I would like it to appear. It would be nice to -noinclude- the templates and TOC from Glossary, but I'm not exactly sure how to arrange that. If someone with more wiki transclusion experience could make some edits, this might just work out. It's less than pretty as it is right now Cjl 19:23, 31 March 2008 (EDT)

I did some testing and I think I have it. By bracketing the body of Glossary with <onlyinclude> and </onlyinclude>, just inside the template assignments, the desired effect is achieved, without any impact on Glossary. I'm going to be bold and make these edits as there is agreement on principle. Cjl 22:11, 31 March 2008 (EDT)

Content Development?

Shouldn't content development be part of the deployment guide? Every country wants to be able to develop constructivist content that meets their particular needs. Berrybw 11:49, 8 April 2008 (EDT)

It is a good point, but I am not sure what to say except: See Content bundles for details on how you can convert existing media assests—books, websites, multimedia, Etoy project files, etc.—into a content bundle that can be installed on the XO laptop. --Walter 12:50, 8 April 2008 (EDT)
Maybe we should include more references to collections, a la, [1]. --Walter 15:17, 11 April 2008 (EDT)

10 Communication - email lists

Membership on a list or wiki should be no more than one form, one email confirmation, and hitting "reply" should by default get your answer to the whole list. This might change for some very special lists that need controlled traffic, but nothing more complicated that this should be the default. For existing lists you can participate in see

BTW, would be nice to have there info on how to contact each list admin, and how to request a list (yes, those on the know are told to contact, and those even more in the know get Samuel direct. If a noob makes to the lists page, it is not clear what to do. Or emailing mailman is the way? I'll test that right now)

A key element of deployment success is to establish a communication channel with OLPC. Use the e-mail lists (server and devel have been the most useful for me) and you can try help and too.

I also recommend that you establish some relationships and communication channels with people working for OLPC and build a community of volunteers that can provide support. I'm not sure exactly how you make contacts with OLPC workers but you can try scraping e-mail addresses off the lists and contacting people directly. Gregorio 08:53, 2 May 2008 (EDT)

School Server Suggestions

Decide if you need a school server. Make sure you have a budget and power in the school to support it. See also connectivity suggestion above. If you want a school server (recommended), build a list of software that you will use on the XS. Here is one link to what it can do:

Here is a long list of possible uses for the XS. Its a rough working page where we flushed out ideas for what the XS would do in Nepal:

Here's a better formatted explanation of what Nepal deployed:

Here's a link to installing the XS:

Here's a link to how to build a Fedora machine with LAMP modules:

More school server links available at:

Make sure to use the server list communicating what you do and any questions you have.

Gregorio 09:15, 2 May 2008 (EDT)

Logistics Suggestions

Put a plan in place to test the XOs when they arrive. Here is an example:

Don't underestimate the effort needed to create a custom image. Unless you are using the supported build (either 656 or 703 as of this writing) with absolutely no changes you will need to research how to make any changes.

Check the appendices on this guide. Lots of good added detail is there.


Gregorio 09:22, 2 May 2008 (EDT)

Deployment communication and grassroots steps

See deployment reports for open communication related to a deployment -- much of which can start before the beginning of this guide, some of which can help lead to a successful country partnership. --Sj talk 13:57, 29 May 2008 (EDT)

There should be a separate page in the guide for preparation in advance of a full partnership; and a separate section and page for grassroots developments and community-building around a deployment.

Improving the Deployment Toolkit

I am working with a small team to improve the deployment toolkit including this guide and the associated google doc and spreadsheets for budget planning (you can see our goals and approach in the page Improving the Deployment Toolkit). This is part of some pro bono work we are doing for OLPC between now and December 2010. We would greatly value any input from the community using the wiki on what's important to you and what material should be included in the new sections we are planning. We will be reviewing the existing content to make sure its consistent and easily navigable as well as adding some new content. Please feel free to add your thoughts below or contact me directly.

Mark.Burnett 10:21, 8 September 2010 (UTC)

We are planning to:

  1. Improve the existing Deployment Guide section in the wiki
  2. Consolidate and improve the Deployment Toolkit (the spreadsheets used for budget planning)
  3. Create a Deployment Tracker showing which teams are currently deploying and what stages they are at so they can share problems and solutions and collaborate more effectively
  4. Create a new version of the google doc version of the Deployment Guide once we have finished updating the wiki

The Draft Deployment Guide wiki page currently contains the following sections (new sections marked with a *).

Please add comments as indented text like this (by adding :: before your text) beneath each section if you have ideas or links to content we should incorporate
If you have a comment on a comment, start a conversation by adding another :!
  1. How to customize the deployment guide* to create a deployment plan for your specific deployment
  2. Funding decision tree*
  3. Consultation
  4. Core Team skills and competencies necessary for a successful deployment
  5. Team setup and deployment management*
  6. How to align with national & regional education policy* (including sponsorship)
  7. Logistics
  8. Localization
  9. Connectivity
  10. Power Infrastructure
  11. School Server
  12. Teacher Preparation/Student Facilitation
  13. Support
  14. Service/Repairs
  15. Internet-safety Training
  16. End-of-life Planning
  17. Appendices
    1. Links to related documents* such as training guides
    2. Templates*, e.g. training & deployment timetables
    3. Lessons learned*, e.g. Don’t rely on solar power, ...
    4. A teachers perspective*... on how to facilitate learning with the XO
    5. How to edit this wiki version of the deployment guide* (e.g. during deployments to add lessons learned and further information to help other deployments)
    6. Process for creating a new release of the Deployment Guide document* - how to review and refine the wiki content and produce an updated release of the google doc from it
    7. Related organizations* that are involved with OLPC or may have supporting resources or be able to help
    8. Links to related websites* and where they are OLPC websites, a description of which ones are used for what purpose

Mark.Burnett 10:21, 8 September 2010 (UTC)