Organizing organizing: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
(..)
Line 16: Line 16:
*[[XO map]]
*[[XO map]]


*Rolls and Teams
*Pecan Rolls and Teams
**Install Team
** Install Team
***Instructions on getting the emulator installed
*** Instructions on getting the emulator installed
***A core team of people that help others to install the emulator
*** A core team of people that help others to install the emulator
****IRC Channel, Private chat on AIM, whatever it takes.
**** IRC Channel, Private chat on AIM, whatever it takes.
** Facilitators
**Directors
***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.
*** 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.
***Directors are most likely people who just lurk all the time on IRC or something along those lines.
*** 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
**Todo list should have difficulty levels, like the art of computer programming. E.g., If you know Python then a problem is a:
** 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,
*** 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 hour,
*** 17 if you could do it in one sitting, but it may take a few hour,
***20, means you could do it in a few days
*** 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.
*** 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.
*** 30, maybe a couple weeks to a couple of months, but it's hard.
***38, maybe a couple of months with a lot of creativity and innovation
*** 34, maybe a couple of months with a lot of creativity and innovation
***40, Maybe a couple of years
*** 40, Maybe a couple of years
***50, you may be lucky to knock the problem into the 40s in a couple 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.
**Todo list should indicate the urgency of the item for the project.
**Todo list should indicate necessity of the item to the project.
**... and the necessity of the item to the project.

Revision as of 03:29, 30 May 2007

  • Syndicate intern opportunities in one space?
  • Merge volunteer pages
  • Online “welcome wagon" packet
    • What would this look like?
  • OLPC blog
    • Who is everyone, and what are theyworking on
    • Pix w/ XO
    • 3D tour of XO
    • "Poster Child"
  • How to document pilot programs
    • Photos
    • Stories/anecdotes
    • Examples of use
    • Profiles of kids and their laptops
    • Screenshot app-- develop + have kids take a screenshot of their laptop in its favorite use/config
  • XO map
  • Pecan Rolls 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 hour,
      • 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.
Retrieved from "http://wiki.laptop.org/mediawiki/index.php?title=Organizing_organizing&oldid=40086"