BIT 120215

February 15 2012 Build Instructor Training

Place: Meeting Room

Facilitator: Amelia

Scribe: Lynnae

Attendance: Sean E, Phillip, Kurt, Stephen M, Brett, Lynnae, Nate, Jason O, Amelia, Michael, Howard, Blaine, Max, John, Gordon, Mary, Janet, Jeffrey, Tara

Introductions

Review of last instructor training notes, July 2011 http://wiki.freegeek.org/index.php/BIT_110728 Build category, see "Build Instructor Trainings"

Update for the last 6 months: Addition of Laptop QC, build testing of Optical Drives, recent spec upgrades.

Note on Laptop QCs: Builders can receive 1 build credit for 3 laptop QCs, please try to limit this to 2 build credits per builder. We can't store Laptop QCs like we can store in progress system builds/QC.

There is a wait list available for LCD monitors, if there are no LCDs available during disbursement, just let Amelia know if there is a builder who needs to be added to the list.

Sean showed us how to read the FGSS information to determine how many completed QCs/Builds a builder has completed, and how to enter a build credit without a system ID attached. Check in with a staff member if you're not sure how to do these things.

Education:

-Teaching Modules idea brainstorming

How to install Linux Other Linux flavors Manual Partitioning File Systems

  file hierarchy, or differences between file systems

How to read information about processors (across generations and model types) Introduction to user interface and customizing Intro to package manager Tours of Post-Build Reuse and Recyling elements of Free Geek Dual Booting Internet research methods How to build a gaming computer Intro to open vs closed source softwares

Jeffrey is interested in teaching a GUI class Michael: Dual Booting Kurt: Installing Linux

1. Amelia will commit to making a wiki page for Build Module curricula

-Visual Appendix Ideas:

RAM chart PATA vs SATA vs Floppy Jumpering How to read a multimeter How to read a Mobo/typical pin outs BIOS password clearing visual

QC and the store, Lynnae's notes:

Goal: To give build instructors context for systems sold from the store, and what is helpful for instructors to keep in mind.

  Basic overview (info from database, how the outward facing store stock

looks, and what we do to prep it) Lappies: January: sold 69, disbursed 35 February so far: 31 sold, 7 disbursed Systems: Jan: sold 53, disbursed 107 Feb: sold 44, disbursed 65

Hurdles in the store: consistency with a really inconsistent inventory time to process things expectations from our customer base (apple store we ain't) inconsistent QC process

    Things to watch out for ("stop and fix")

Loose screws, dust, clogged fans, poorly labeled broken ports, crooked stickers, missing system ID tags/stickers, handwritten/misleading printme notes, mismatched or ill-sized face plates and slot covers ("holsteins"), beige anything, gook and grime, sticker residue, missing feet. Laptops: Screen quality (flickers, lines, dead pixels, dark screen spots, etc), sticky/inconsistent/broken keys or track pad, loose/missing screws, inconsistent AC adapter, fan/hard drive noise.

   If you need to take something back to laptops, see if the instructor

is available first. They may be running around. If needed, write a note, and leave it on the incoming table by the box to return QC'd systems.

   How to write a helpful printme note

If you're writing a book, it's time to stop and fix/consider rejecting the system. Keep in mind this needs to be interpreted by a wide base of people. References to things we do all the time are pretty unintelligible to most of the outside world. No hand written notes: keep in mind these systems are under warranty, tech support needs access to anything important about these systems, the database is the primary way we keep track of these things. Always note untested ports, cover with black electrical tape.

   Discussion questions/questions to keep in mind:

How can we keep builders engaged during QC process? How can we introduce more attention to detail and learning opportunities? What resources or comprehensive approaches are missing from the current QC process (do you need anything?).

Sign-offs & Disbursements Don't have time for sign-off walk through Disbursements: double-check build status when builder starts take-home box to make sure they are eligible, discuss post-build options. Source USB mice and speakers from receiving (you can grab things from the class room as long as a class is not in session), LCD monitors in the warehouse on the adoption shelf, double check that they are 15-17", keyboards, mice and power cords are also squirreled in the warehouse. For introducing volunteers to post build, on the back of the door in Tardis there is an area-by-area map of needed shifts. If you need an adapter for their monitor, the build room has some available, you can check the store too.

Esoterics: Weird issues and fixes

Questions, shout-outs, feedback

COMMITMENTS

1. Amelia will commit to making a wiki page for Build Module curricula
2. Amelia will revise printme instructions
3. Amelia will switch the assembly and qc checklists to include the system ID before instructor sign-off, have builder hold off from printing printme before sign-off