Organizing organizing
Jump to navigation
Jump to search
- 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
- 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.
- 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.
- 38, 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.
- Todo list should indicate the urgency of the item for the project.
- Todo list should indicate necessity of the item to the project.
- Todo list should have difficulty levels, like the art of computer programming. E.g., If you know Python then a problem is a: