Hackpads are smart collaborative documents. .
Procedures and Subroutines
1248 days ago
Unfiled. Edited by Alex Hanson 1248 days ago
  • Too many people in build and too many complicated projects in progress leads to low quality instruction.
  • Just like anything else, there are issues of scale at FreeGeek. What works well for 30 volunteers may work poorly for 40, and not work at all for 60. 
  • We've got more people coming into the shop as a result of that CBS piece, so I want to improve our process before we are swamped.
  • Need to find a way to improve our organization so anyone with technical skill isn't pulled ten directions at once.
  • Decide on a maximum capacity for a Build day?
  • Teardown Area: 6 maximum
  • Build Area: 16
  • Testing Area: 6
  • QA Area: 3 (Janet and some helpers)
  • 31 people in build.
1289 days ago
Unfiled. Edited by Alex Hanson 1289 days ago
Put Volunteers to work:
  • Hand out computers from the build shelf to volunteers that come in. Tell them what the issues are with the item they are working on, and what they are to figure out.
  • Identify individuals with experience / skills and delegate solving problems to them.
  • Identify individuals with problems and work to solve these problems.
  • Pair up people w/limited skills.
  • Get sligntly more experienced people to watch the inexperienced.
Maintain Order:
  • Coordinate with the people in charge of Teardown, Test, QA etc. See what they need.
  • See if there are any conflicts building, and try to defuse them. Get HR / Staff  involved if things get serious or there has been a breach of the Code of Conduct.
  • If you get angry, take a break. If things get too upsetting, tell someone else on staff and then take the day off.
1375 days ago
Unfiled. Edited by James Slater 1375 days ago
  • General
Cleanup time for an OpenBuild Day begins 1hour from closing.
  • 60 minutes before closing, we announce:
  • Be aware that you must stop work in 30 minutes.
  • If you're in the middle of something that can't be finished before then, please find a good stopping point.
  • 30 minutes before closing, we announce:
  • We are closing in 30 minutes.  Stop ALL work on your computer, and make sure the area around you is at least as clean as how you found it.  The next time we're open for build hours is __________.
  • 10 minutes before closing, TURN THE LIGHTS ON and OFF a few times as an indication that we are closing.
  • At closing time, TURN THE LIGHTS OFF for  several minutes, as a clear indication that WE ARE CLOSED.

Stop sharing the collection with ?

This pad is open to "", so will still be able to access it.
Procedures and Subroutines Feed

Contact Support

Please check out our How-to Guide and FAQ first to see if your question is already answered! :)

If you have a feature request, please add it to this pad. Thanks!

Log in