Organizing organizing

• Clarify volunteer roles/opportunities/processes

  Syndicate intern opportunities in one space?

  ...from various countries and organizations.

  Help redirect orgal interest away from donating funds and towards hosting and mentoring interns

  Merge volunteer pages

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

  Checklist for getting started

  Templates for creating a local wiki

  Links to (or pdfs of) some of the crucial OLPCwiki pages

• OLPC blog & photojournal

  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

  Pix w/ XO

  3D tour of XO

  "Poster Child"ren

• How to document pilot programs (Category:Pilot site)

  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

• XO map

• Roles and Teams
  • 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
  • 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.
  • 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?