Build

Building computers for people is a fun way to learn stuff. The build program is a structured way for volunteers to contribute to the cause and learn about hardware and basic troubleshooting and Linux skills. Builders can also earn a computer, but the time commitment is significant and the computer is the same as that earned in the adoption program.

Prebuild steps

We don't require any prior knowledge for people to join the build program. The steps that precede the build workshops are called, collectively, the "prebuild steps," and teach very basic material that will be needed for people to make their way in the build workshops. Several of these steps can be bypassed by people who know the material already; they can ask to be "tested out."

Card sorting

• Educational goals: Card sorting will familiarize the participant with terminology we will expect them to know, components in general, and the main characteristics of cards. We also want to encourage careful observation of the parts.
• Material goals: Sorted cards can be processed (either in testing or recycling) much more quickly.
• Teacher: Volunteers who have already done this task should be able to teach it. Also, the staff person who is acting as reuse coordinator will teach this.
• Test out: This step can be tested out of through a card identification quiz.

Motherboard sorting

• Educational goals: Much like card sorting, except particpants learn about the main characteristics of motherboards. They're also introduced to the flowcharts that we use in other parts of the build program.
• Material goals: This is primarily educational.
• Teacher: Volunteers who have already done this task should be able to teach it. Also, the staff person who is acting as reuse coordinator will teach this.
• Test out: This step can be tested out of through a motherboard-knowledge quiz.

System evaluation (eval 1)

• Educational goals: This task requires using documentation, using the flowcharts, learning the importance of labelling and tally sheets. It provides (for many) first contact with complete systems, tool and case structure. It's also an example of the peer-taught method of learning.
• Material goals: This task entails doing a preliminary cull of definite "recycle" systems and salvaging ("mining") parts to be tested.
• Teacher: Participants are encouraged to rely on the documentation and each other to figure out the processes. There is also a group of evaluation overlords who can instruct, check work, and test participants who are ready to move on. Also, the staff person who is acting as reuse coordinator will teach this.
• Test out: This step is required; builders can't skip it.

System evaluation (eval 2)

• Educational goals: The main skill used in eval 2 is troubleshooting. Participants get exposure to a turned-on system and learn about POST, processors and RAM, and the BIOS. Reading documentation is also stressed.
• Material goals: Eval 2 eliminates obsolete systems from the stream an ensures that systems we store are labeled and filed properly.
• Teacher: Participants are encouraged to rely on the documentation and each other to figure out the processes. There is also a group of evaluation overlords who can instruct, check work, and test participants who are ready to move on. Also, the staff person who is acting as reuse coordinator will teach this.
• Test out: This step is required; builders can't skip it.

Related links

• Aaron's PCI Modem comments
• Staff schedule: who's on reuse 2? who's the build instructor?