View source for Running a Kit Build

== Step-by-Step ==
# Pick a kit that people are interested in.
#* Check out [[Kit Building]] for some ideas.
#* If you're uncertain, poll some of your friends or post to the blabber list.
#* # If you haven't built this kit before, now would be a good time to order one and try it out.
# Price out the kit, including shipping and payment processing (usually around $1-1.50) costs. It's best if everyone can walk out with a working gadget for less than $30 total. Note what tools are needed. HacDC may already have what's needed.
#* Spare parts?
#* Batteries?
# Pick a date and time.
#* Weekend afternoons are nice because people aren't under pressure to rush from work or get home.
#* Try to pick a date 4-6 weeks in the future.
# Create a page for your event, including registration.
#* [http://www.eventbrite.com/ Eventbrite] is a classic option.
#* [http://hacdc.org The main HacDC site] is equipped with [http://civicrm.org/ CiviCRM].
#* If you want to avoid fronting money that you may or may not get back, have registration close with enough lead time for you to order the materials.
#* Ask people to bring needed tools if they have them. Even if HacDC has some, it may not have enough to go around.
# Add the event to the [http://www.google.com/calendar/embed?src=c2I4bWgxZDMzMnBidm5iMmc0aW9iMnA3MjhAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ event calendar]
# E-mail the blabber list
# Post to the [http://hacdc.org HacDC site/blog]
# Print directions for everyone. Some ways to save paper:
#* Ask people to share
#* Use the projector in the space as a supplement. Don't rely on people "staying together", though.
#* Print on both sides of the paper
#* Shorten existing directions in some way, or write your own

== Additional Pitfalls ==
* Don't trust things to work. Test it all in advance. That includes:
** Parts lists
** Firmware
** Directions