Organizing organizing

Clarify current volunteer roles/opportunities/processes

• Syndicate intern opportunities in one space on wiki
• ...and from various countries and organizations.
• Help redirect orgal interest away from donating funds and towards hosting and mentoring interns.

  (Which requires info on how they might mentor said intern, and what s/he might do).

• Merge OPLCwiki volunteer pages, which are:

  ?

Online “welcome wagon" packet... what would this include?

• Basic checklist for getting started
• Model/templates for creating a local wiki, blog, & photojournal (see below).
• Links to (or pdfs of) some of the crucial OLPCwiki pages

  OLPC_Human_Interface_Guidelines

  ?

• OLPC video documentary

  From OLPC-open:

 What I'm looking for is a fairly systematic presentation of the XO computer and how it is being used.  There are some basic pieces of information that I want to see, in addition to the scenes of children demonstrating various activities.  These include:
 * What kind of Internet connection does the school have?  How fast?  What does it cost?
 * When the children take the XO computers home, does the mesh network really keep them connected to the Internet?  At what distances, and what speeds?
 * If hundreds of XOs are distributed at a school, do icons for all of them appear on the screen in Neighborhood view?  
 * Which icons will appear in Neighborhood view in an urban area that might have several schools?
 * Which icons appear in Friends view?  How does the user control this?
 * Does the school or teacher have to agree to apply the Constructivist approach to education before they get XO computers for their students?

OLPC blog & photojournal

Ideally, this would document our own organizing/development process, and could be a model for others.

• Templates for creating OLPC user "homepage" (currently wikipage) w/ instructions on how to set up a free blog (blogger/wordpress) etc.
• Who is everyone, and what are they working on
• Have users take pix w/ XO
• 3D tour of XO
• Anecdotal users like the "Poster Child"

How to document pilot programs (Category:Pilot site)

Globally...

• Aggregate existing self-documentation, including:

  Uruguay (blog): http://olpc-ceibal.blogspot.com

  Brazil (YouTube): http://www.youtube.com/profile?user=lecufrgs

  Thailand (on wiki): Thailand/trial-200705

• Some sort of OurStories project?
• XO map

Locally...

• Photos
• Stories/anecdotes
• Examples of use
• Profiles of kids and their laptops (maybe via the OurStories project)
• Screenshot app-- develop + have kids take a screenshot of their laptop in its favorite use/config

Roles and Teams

Define and document...

• Install Team
  • Instructions on getting the emulator installed
  • A core team of people that help others to install the emulator
    • IRC Channel, Private chat on AIM, whatever it takes.
• Facilitators
  • Direct volunteers toward projects they might be interested in by making themselves available for private chat or in a group chat. Someone comes in and says, hey I want to help, these are my skills. A director can help direct them where to go.
  • Facilitators are most likely people who just lurk all the time on IRC or something along those lines.
• Candy Stripers
  • coating community members and their computers in fine layers of Sugar... until the emulators are really good.
  • helping launch locos

Todo List for Vols

• Todo list should have difficulty levels, like the art of computer programming. E.g., If you know Python then a problem is a:
  • 10 if you could do debug/fix/add feature in a couple minutes,
  • 17 if you could do it in one sitting, but it may take a few hours,
  • 20, means you could do it in a few days
  • 29, means you could do it in a couple weeks with a lot of creativity.
  • 30, maybe a couple weeks to a couple of months, but it's hard.
  • 34, maybe a couple of months with a lot of creativity and innovation
  • 40, Maybe a couple of years
  • 50, you may be lucky to knock the problem into the 40s in a couple years.
  • 51, first find a new base and reduce to a previous problem
• Todo list should indicate the urgency of the item for the project.
• ... and the necessity of the item to the project.
• Should maybe be sorted by skill and subject?
• One possible model is the mysociety volunteer list. Might be people worth talking to.
• Another is a bugtracker (or more user-friendly version thereof). Should we use the current OLPC bugtracker for these tasks as well?