In terms of Montpelier... Chad has a good idea that we should probably explore... and I'll let him elaborate on it. But the point of it would be it may be incredibly easy for us to get a hackerspace organized in Montpelier assuming we can get a handful (say 6) folks to want to be involved.
I would be very interested in what your friend (Jim) in Montpelier found out about doing a project like this (setting up a hackerspace), what research he did, and whether or not he is still interested? ... When Tom and I left it was clear to me that the 'portable hackerspace' concept had some good traction with the eight who met ... and that it seemed like we were all open to doing such a meet at Tony's house in the next month. But then we left before everyone else so that may have been vetoed afterwards. We'll need to organize... who wants to be an organizer first and a participant second? Should we be clear about which VAGUE threads are hackerspace related by defining thread names be prefixed with "HS:" so that it is easy for folks not as interested in hackerspace meetings to filter them out? If we become meta organizers of a cross-interest mega-group, which groups should we be aware of to involve? And where will our meta-portal for group communication be located? I have a server, but I bet lots of other folks do too - folks that already have a CMS of some sort installed? Here is Tony's list: Vague - Mailing List Vtsda - Mailing List .Net - Mailing LIst SQL Server - Mailing List Ruby - ??? PHP - ??? Café Scientifique - ??? Crash collective - ??? Lamb Alley - ??? Contact through Chad A.? Woodworkers workshop - ??? HAM radio club - ??? Contact through Tom C.? Green Mountain Prospectors - ??? Local 2600 group - ??? Meeting time listed in back of 2600... Any more? The people that met on Tuesday were the following: Josh S. Joe E. Chad A. Tony C. Rion D. Tom C. Kevin T. Nick F. Josh was taking notes proper. Perhaps he can chime in with some more thoughts? Also, everyone that thinks this is a cool idea... pat Kevin T. on the back when you meet him next time for bringing it up. -Nick --- Nicholas Floersch (pr. Floor-sh) Stone Environmental, Inc. > -----Original Message----- > From: Vermont Area Group of Unix Enthusiasts > [mailto:[email protected]] On Behalf Of Jim Carroll > Sent: Thursday, April 09, 2009 9:32 AM > To: [email protected] > Subject: Re: VT Hackers Meetup > > On Thu, Apr 9, 2009 at 6:29 AM, Marc Farnum Rendino <[email protected]> > wrote: > > I'm from Hinesburg too, so I'd like to see something there as well. > :) > > Me three! > > > Suggestion: Let's think of this as a meta-incubator with the express > > purpose of creating several local groups. The local groups may indeed > > come and go as interest/projects change, and that too may be part of > > the way this is built; the more dynamic the better, especially if > > there's a stable core. > > I don't actually think the economics of a dedicated hacker-space would > work... a friend of mine seriously looked at putting together > something like this in Montpelier, and he would have to have at least > 6 regular 'tenants' at their desks and paying a small fee (couple > hundred a month) before it would start to be worth the rent. Once you > have a core like this though... all sorts of casual meetings could > happen. > > Would I would love to see is a monthly get-together / pot luck at > someone's house for a few hours on a weekend... > > Maybe automate their vegetable garden weeding with some > arduino-powered robots. Or put some temperature, flood water, and > wine-level sensors in a wine cellar! ;) > > A little more expensive than the arduino but wireless is Synapse: > http://dkc1.digikey.com/us/en/ph/Synapse/EK2100.html The creators > program it with 100% python, and gave a fantastic talk at PyCon: > http://us.pycon.org/2009/conference/schedule/event/73/ > > In my mind, what we need is some good planning so when we get together > on a weekend, we have all the plans and parts and people together to > do some cool stuff. > > -Jim This communication, including any attachments, is solely for the confidential use of the person(s) named above. If you have received this communication in error, please notify the sender immediately and delete/destroy the original. Any reader other than the intended recipient is hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited.
