first pass at documenting metadata format etc
might as well admit it's a yaml file
fixed formatting issues and updated one or two sentences
converted package_spec.yaml to consistently use 80 character lines
explain metadata template
actually, dealing with dual licenses isnt worth my effort
wtf kind of lame ass excuse for a merge is this
updated description of a maintainer
be explicit about todo in the spec
i probably shouldn't be writing specifications this late at night
a long-overdue list of lab equipment useful for do-it-yourself biology
more diybio-related equipment and greatly improved file organization
various updates to package_spec.yaml (listed below)

updates:
- removed comment from url line
- rewrote my bad additions to intro
- added 'dependency' definition
- added to package name requirements
- formatting fixes
we also need a short description for each project
old code to download thumbnails from the thingiverse scrape
heath matlock contributed this a few years ago
this time in png format
first go at a new web presence
2010-01-21 - fix skdb package import call for units unit test
packages aren't necessarily going to be python packages on the first round