<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
</head><body style="">
<div>
The timing was amazing. It's like the material for my Maker Community book project has unfolded in my inbox. Boy do I have a lot of usage permission forms to send out...
</div>
<div>
</div>
<div>
Randy
</div>
<div>
<br />> On July 2, 2014 at 9:28 PM Ryan Rix <ry@n.rix.si> wrote:
<br />>
<br />>
<br />> "J. F. Corner" <jake@5n4k3.com> writes:
<br />> > And now this thread has turned into drama. Meta indeed.
<br />>
<br />> Only if that's how you choose to read it. I am choosing not to and it's
<br />> a great discussion about the merits of hackerspace design patterns and
<br />> that is basically the point of this list.
<br />>
<br />> Carry on, friends.
<br />>
<br />> I'd interject with my own patterns but my wrist is killing me today.
<br />>
<br />> > On 7/2/2014 21:25, Naomi Most wrote:
<br />> >> The "meta point" being that no one should model a hackerspace on Noisebridge?
<br />> >>
<br />> >> That may be true. I have no stake in that particular game.
<br />> >>
<br />> >> There are dozens of ways to model a hackerspace, and I wouldn't say
<br />> >> Noisebridge has the best one. It's an interesting model, and one I
<br />> >> feel is worth pursuing because it is hard, and I perceive there to be
<br />> >> payoffs in figuring it out without compromising its ideals. You may
<br />> >> disagree.
<br />> >>
<br />> >> But the original point *I* was addressing was the assertion that if
<br />> >> you start with a community and then build an organization, that the
<br />> >> rest will basically follow.
<br />> >>
<br />> >> I used Noisebridge as a counterexample to THAT point.
<br />> >>
<br />> >> Noisebridge is a great example of how organizations based on culture
<br />> >> and minimal policy can easily shift, even pushing its original members
<br />> >> out, simply by being unaware of how the rapid influx of new people
<br />> >> (ANY new people, not the oft-demonized Occupy and so on) changes the
<br />> >> culture by sheer weight.
<br />> >>
<br />> >> That's not the only lesson learned from the last 5 years at 2169
<br />> >> Mission St, but it is one of the biggest ones.
<br />> >>
<br />> >> Again: if you guys can't see past "at least we aren't Noisebridge",
<br />> >> you're never going to be able to learn from our mistakes.
<br />> >>
<br />> >> --Naomi
<br />> >>
<br />> >>
<br />> >>
<br />> >>
<br />> >> On Wed, Jul 2, 2014 at 6:08 PM, Al Billings <albill@openbuddha.com> wrote:
<br />> >>> Naomi,
<br />> >>>
<br />> >>> sudoroom has the same problems as noisebridge because it explicitly modeled
<br />> >>> itself on noisebridge with consensus decision making, an open door policy to
<br />> >>> the street, and a political, social justice mission. They've gone as far as
<br />> >>> to say a space isn't a real hackerspace if it isn't political.
<br />> >>>
<br />> >>> Your counterexample proves the meta point...
<br />> >>
<br />> >>
<br />> >
<br />> >
<br />> > _______________________________________________
<br />> > Discuss mailing list
<br />> > Discuss@lists.hackerspaces.org
<br />> > http://lists.hackerspaces.org/mailman/listinfo/discuss
<br />> _______________________________________________
<br />> Discuss mailing list
<br />> Discuss@lists.hackerspaces.org
<br />> http://lists.hackerspaces.org/mailman/listinfo/discuss
</div>
</body></html>