summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorkanzure <kanzure@gmail.com>2009-09-03 08:14:50 -0500
committerkanzure <kanzure@gmail.com>2009-09-03 08:14:50 -0500
commit2901258a9bcf47c0808d5aeae4c711cfb07df966 (patch)
treec561917f4f0fdea117598b77b8cb1fe56708edd8
parentd290ca39c0b31a73e9e02b5b87c794c1b9d432a5 (diff)
downloadskdb-2901258a9bcf47c0808d5aeae4c711cfb07df966.tar.gz
skdb-2901258a9bcf47c0808d5aeae4c711cfb07df966.zip
dumped some text into the readme
-rw-r--r--readme14
1 files changed, 14 insertions, 0 deletions
diff --git a/readme b/readme
index 6df9b15..a9eb2a9 100644
--- a/readme
+++ b/readme
@@ -53,3 +53,17 @@ pymates/
unittests/
run these after hacking to make sure you didn't break anything
+
+
+====
+
+Here are some brief explanations of skdb that we have used in the past.
+
+skdb is a method for downloading hardware over the internet. Technically, it's a free and open source hardware package manager. We're making it because we don't want to reinvent the wheel every time we begin a new project. There are many common tools and parts involved in making thermocyclers, microprocessors, cnc machines, coils, pcb projects, robot armies, etc. Essentially it is like "apt-get" and "emerge" for debian and gentoo, and all the other linux software package managers. You could even say it is like "apt-get but for real stuff". In skdb, hardware is organized into packages, a standard and consistent way for programs to know where data is going to be found. For every part in a package, there are a number of interfaces that define possible ways to connect with other parts (part mating). And for every package there are listed dependencies which tell skdb what else has to be downloaded and built in order to successfully carry out a project-- all of which is dealt with automatically, unless you're a die-hard Gingery fan, which is perfectly fine. With OpenCASCADE integration, an open source CAD geometry kernel, parts can be visualized and with skdb combined in real-time to show new assemblies and constructions. The next steps are automatic instruction generation for assembling these parts and projects, with human-readable instructions as well as robot instructions (i.e., g code). In the pipeline is also a python/django-based wiki frontend to skdb with a git back-end called "djangit", which could be used as a free alternative to instructables, thingiverse, etc. These tools are imperative to do-it-yourself and free manufacturing, so please feel free to check out skdb over the web:
+
+git repository: http://adl.serveftp.org/skdb.git/
+repository contents: http://adl.serveftp.org/skdb/
+presentation: http://adl.serveftp.org/lab/presentations/updates-from-austin.pdf
+email: openmanufacturing@googlegroups.com
+IRC: #hplusroadmap on irc.freenode.net
+