Hi: I disagree with some of what you posted, but it may be only a matter of semantics. See below:
On Tuesday 14 April 2009, H. Kurth Bemis wrote: > To start a space you're going to need members that are active in the > hacker community. Define hacker community? How about just a community that has mutual interests? > Members that already have been hacking Arduino for a > few years, members that have been working with electronics and > chemistry, members that have "mAd 5k1Llz" in several different areas. > If you're missing that diversity, then I think the space will not > sustain itself very long. I think you are confusing a specific 'hacker' Event that is being discussed with the concept of a hackerspace, which is different. > > So before you get worked up about a space and moving and what not, spend > several months attending regular, weekly meetings. Give it a few > months, spread the word that you're trying to raise interest to start a > space. After that time, you should have a pretty good idea of who is > serious about the space and who isn't. To find who is serious about the > becoming a member and who isn't, simply charge dues. No matter if there > isn't a space at the present time, collect dues and keep records. If > the whole thing becomes a wash, then return the dues. Space is necessary to have a place for events, if not for squatting. Space is a major consideration. Defining the Events, the types, the participants, is another matter completely; as is discussion of the way the organization is structured.... > > It's important to stop thinking of the space as a venture that outsiders > will come to, because honestly, you will not want outsiders poking > around your workshop or lab. You are defining hackerspace as a geek/nerd thing exclusively; which may work in urban areas, but not in the sticks. Not outsiders, but members, just members who are not techies. There should (IMHO) be a place for that/them; artists, designers, special-interest groups, etc... UNLESS the consensus is that they are not wanted. > At Foulab, we welcome visitors, but we > make sure they are supervised while in the lab. I don't know about the > projects and tools that are planned for the space, but in our lab we > have several large power tools that will take your hand off without a > hickup. Someone that does not know what they are doing or working with > can seriously injure themselves. Also, I'll say it again - some members > projects may borderline on, or cross the "legal" line. Best to keep > those things on the downlow. The space just needs adequate supervision and security. A locked closet some alarm system ..... Do we have the skills to create that? I'd hope so. > > When it comes down to it, you are trying to build a community. The > space will come after the community has gained members and momentum. > I'm sorry to say, but "Build it and they will come" is a pipe dream. > Reality is that spaces cost money and are much more work then I think > most realize. It's not "Build it and they will come" It is, from where i'm perched, a number of things in parallel, starting w/a plan. Finding a site, enumerating the amenities and Events, defining the community can all be broached simultaneously. As can running Events concurrently while the plan is still in development. > > I really recommend visiting other spaces and seeing how they started, > how their managed and the like. There's much more going on behind the > scenes then a bunch of hackers in a workshop (or lab) hacking away on > projects. And I would really recommend avoiding the possibility of other hackerspaces defining the model by which we run. Hackerspace, BHive, Hub, call it what you will: the notion has been floating around for a long time in various flavors and most everyone here can grok the 'big picture' w/out having to adopt somebody else's vision of what worked for them. Not to say that perspective wouldn't be helpful, just not the 'be all' and 'end all' of what it is. > > It would be nice to see a community start in Vermont, but it's important > to make sure there's a communality and not a few folks who want a shared > space to code in. While that's fine, and I'm sure there are spaces that > are mostly for "soft" hacking (software, etc), the majority of spaces > are setup and used as workshops and labs. Actually, i dont know that there are such publically accessible places, which made this impetus appealling (in that scope). > > Just a few thoughts based on what I've seen cross the list...didn't mean > to offend or upset anyone, apologies in advance if I have or did. :] > > ~k >
signature.asc
Description: This is a digitally signed message part.
