At Node we worked from the stance of: "don't make (me|us) make a (rule|policy)". I think we got it from Nick Farr, but the idea is pretty common. We're not specifically anarchists, but we trend towards anti-hierarchy, so if we all agree something shouldn't be done (it's common sense) then we don't do it. If there's an issue with the landlord ("no explosions", for example) then we don't do it. If there's an issue with personal safety or the destruction of someone else's property, then we don't do it. (you get the picture).<div>
<br></div><div><blockquote class="gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204, 204, 204);border-left-style:solid;padding-left:1ex">
rule enforcers</blockquote><div><br></div><div>This sounds like a recipe for hurt feelings. Inside/outside, us/them mentalities break down relationships, are probably bad for a functioning collective. Unless you're not looking for a collective and want a strong hierarchy. In that case, make lots of rules and signs and stuff. </div>
<div><br></div><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
public membership agreements</blockquote><div><br></div><div>Ours is here: <a href="http://wiki.baltimorenode.org/index.php?title=Membership_Agreement">http://wiki.baltimorenode.org/index.php?title=Membership_Agreement</a> . Most of it is cribbed from somewhere else. Most of it is also only in there because it's "official".</div>
<div><br></div><div>- - - - -</div><div><br></div><div>Probably the hardest thing to get over as a member of a hackerspace central committee is that other people will want to do and will do things you don't want them to do. This is also one of the hardest things to get over as a parent, btw. At the point you realize that, the best thing to do is get over yourself and let them do it. Two rules of thumb: pick your battles wisely and pick fewer battles.</div>
<div><br></div><div>If there's a problem with the law (national or local), then the solution is organic (as in life, not chemistry: solution arises as a natural outcome of the cause), they will be caught and punished. If there's a problem with other people ("damn, I hate it that George burns his hair with a soldering iron for fun and he's a weirdo") then the solution is also organic, George will be cut out of the group and will eventually stop coming. Hackerspaces are intensely social organizations, social pressure is their most powerful (or *only* powerful) weapon against internal enemies-of-the-state. </div>
<div><br></div><div>More to the point, even if you make a perfect list of rules and add things to it and put up lots of signs, the only weight it carries is whatever social pressure the hackerspace can exert. Similarly, anything that is not on your list of rules but is enforced via social pressure will be as good as law (e.g., "the first rule of hackerspace is that you *don't* talk about Windows in a complementary fashion").</div>
<div><br></div><div>The continuum of "more rules!" vs. "it is what it is" has a big fuzzy grey area in the middle and that's okay. Your space has to find a balance between "respect your fellow members" and "if you want it done right, do it yourself".</div>
<div><br></div><div><br></div><div>- Adam</div><div><br></div><div><br></div><div><div class="gmail_quote">On Mon, Oct 4, 2010 at 12:38 PM, Matt lehner <span dir="ltr"><<a href="mailto:mlehner@gmail.com" target="_blank">mlehner@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">In conjunction with developing the by-laws for Buffalo Lab, I am<br>
concerned about having a Membership Agreement and associated AUPs.<br>