Difference between revisions of "Build"

Latest revision as of 16:54, 18 July 2014

This page has been migrated to a document on Free Geek's Google Drive.

Information remaining behind may no longer be relevant.

MIGRATOR:

When you have tagged this page as migrated,
please add a link to the new document on Google Drive.

(Link to new page immediately below.)

Building computers for people is a great way to learn. 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; see Testing Out.

Build workshops

The build workshops are the heart of the build program. They run twice a day on most days that we're open, and though there are teachers (and often assistants) for each one, they are largely peer-taught. In most of the workshops, the builders will range from beginners to experienced builders.

QC

The first thing builders do in a build workshop is to quality control computers built by other builders. They use several Free Geek specific scripts and follow a checklist.

Educational goals: Learning to use scripts and other utilities, basic troubleshooting, seeing the pitfalls others fall into.
Material goals: Make sure the FreekBox, Grantbox, and Store desktops are ready to go out the door.

Assembly

This is where participants actually build (put together) computers and update the software.

Educational goals: More in-depth hardware knowledge, use of configuration tools.
Material goals: Um, we need computers! Reuse is our mission.

Laptop QC

Desktop builders can help out their mobile brethren by running laptops through quality control and diagnostics. There is a lot of overlap with desktop QCs as well as some quirks specific to laptops.

Educational goals: Learning to use scripts and other utilities, basic troubleshooting, and an introduction to laptop hardware.
Material goals: Make sure laptops are ready to be disbursed and sold!

Pages related to build

Post-Build
Build tips - Lessons learned the hard way
Build Instructor Guide - A guide for volunteer Build Instructors
Build Instructor Database Guide - How to sign off on QCs & Assemblies using the FGDB

Troubleshooting Guides

Build Troubleshooting Guide
- POST
- BIOS
- Hard Drive
- Optical Drives
- Audio
- Video
- Miscellaneous

@@ Line 1: / Line 1: @@
-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]].
+{{migrated}}
+[https://docs.google.com/document/d/184yCb_yuib6e9vjFrVfwJGiN1NVL5MXovq86mqrlFLA/edit?usp=sharing Link]
+__NOTOC__ __NOEDITSECTION__
+Building computers for people is a great way to learn. 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]].
+{|cellspacing="1px" style="background-color:#f8fcff"
+| width="70%" style="border: 1px solid #6688AA; background-color:#FFFFFF; padding:1em;" valign="top"|
 ==[[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."
+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; see [[Testing Out]].
+==Build workshops==
+The build workshops are the heart of the build program. They run twice a day on most days that we're open, and though there are teachers (and often assistants) for each one, they are largely peer-taught. In most of the workshops, the builders will range from beginners to experienced builders.
-===[[Card sorting]]===
+;[[QC checklist|QC]]
-* ''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.
+The first thing builders do in a build workshop is to quality control computers built by other builders. They use several Free Geek specific scripts and follow a checklist.
-* ''Material goals:'' Sorted cards can be processed (either in testing or recycling) much more quickly.
+* ''Educational goals:'' Learning to use scripts and other utilities, basic troubleshooting, seeing the pitfalls others fall into.
-* ''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.
+* ''Material goals:'' Make sure the FreekBox, [[Grantbox]], and Store desktops are ready to go out the door.
-* ''Test out:'' This step can be tested out of through a card identification quiz.
-===[[Motherboard sorting]]===
+;[[Assembly checklist|Assembly]]
-* ''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.
+This is where participants actually build (put together) computers and update the software.
-* ''Material goals:'' This is primarily educational.
+* ''Educational goals:'' More in-depth hardware knowledge, use of configuration tools.
-* ''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.
+* ''Material goals:'' Um, we need computers! Reuse is our mission.
-* ''Test out:'' This step can be tested out of through a motherboard-knowledge quiz.
-===System evaluation ([[eval 1]])===
+;[[Laptop_QC_Checklist|Laptop QC]]
-* ''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.
+Desktop builders can help out their mobile brethren by running laptops through quality control and diagnostics.  There is a lot of overlap with desktop QCs as well as some quirks specific to laptops.
-* ''Material goals:'' This task entails doing a preliminary cull of definite "recycle" systems and salvaging ("mining") parts to be tested.
+* ''Educational goals:'' Learning to use scripts and other utilities, basic troubleshooting, and an introduction to laptop hardware.
-* ''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.
+* ''Material goals:'' Make sure laptops are ready to be disbursed and sold!
-* ''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.
-===[[basic linux command line for builders]]===
+|width="30%" align="left" style="border: 1px solid #6688AA; background-color:#efefef;padding:1em;" valign="top" |
-==Build workshops==
-===QC===
+== Pages related to build ==
-===Assembly and software===
+*[[Post-Build]]
-==="Graduating" from build===
+*[[Build tips]] - Lessons learned the hard way
-===Build assistants and instructors===
+*[[Build Instructor Guide]] - A guide for volunteer Build Instructors
-===Advanced testing===
+*[[Build Instructor Database Guide]] - How to sign off on QCs & Assemblies using the FGDB
-=="Advanced Linux" classes==
-==Laptop program==
-==Related links==
+== Troubleshooting Guides ==
-*[[Aaron's PCI Modem comments]]
+*[[Build Troubleshooting Guide]]
-*[http://freegeek.org/staffsched Staff schedule]: who's on reuse 2? who's the build instructor?
+**[[Troubleshooting in Build: POST|POST]]
+**[[Troubleshooting in Build: BIOS|BIOS]]
+**[[Troubleshooting in Build: Hard Drive|Hard Drive]]
+**[[Troubleshooting in Build: Optical Drives|Optical Drives]]
+**[[Troubleshooting in Build: Audio|Audio]]
+**[[Troubleshooting in Build: Video|Video]]
+**[[Troubleshooting in Build: Miscellaneous|Miscellaneous]]
+|}
 [[Category:Structure]]
 [[Category:Programs]]
+[[Category:Build]]