[hackerspaces] Hackerspace drama, oh my!

[michael howard]

> it's a great discussion about the merits of hackerspace design patterns

Following the list and discussion for this.  Discussing good and bad
ideas sounds good.

People have written from many places, like Manaus, in the Amazon,
asking "how do we start and run a hackerspace". Got to answer
something. So... hearing about anyone's two cents worth of experience
is not a bad idea.

So, carry on, please, with all the good, the bad, and the ugly.

'cause dere 'gotta be sum gold in'ere sumwhere



2014-07-02 23:44 GMT-03:00 Randall G. Arnold <randall.arnold at texrat.net>:
> 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...
>
> Randy
>
>> On July 2, 2014 at 9:28 PM Ryan Rix <ry at n.rix.si> wrote:
>>
>>
>> "J. F. Corner" <jake at 5n4k3.com> writes:
>> > And now this thread has turned into drama. Meta indeed.
>>
>> Only if that's how you choose to read it. I am choosing not to and it's
>> a great discussion about the merits of hackerspace design patterns and
>> that is basically the point of this list.
>>
>> Carry on, friends.
>>
>> I'd interject with my own patterns but my wrist is killing me today.
>>
>> > On 7/2/2014 21:25, Naomi Most wrote:
>> >> The "meta point" being that no one should model a hackerspace on
>> >> Noisebridge?
>> >>
>> >> That may be true. I have no stake in that particular game.
>> >>
>> >> There are dozens of ways to model a hackerspace, and I wouldn't say
>> >> Noisebridge has the best one. It's an interesting model, and one I
>> >> feel is worth pursuing because it is hard, and I perceive there to be
>> >> payoffs in figuring it out without compromising its ideals. You may
>> >> disagree.
>> >>
>> >> But the original point *I* was addressing was the assertion that if
>> >> you start with a community and then build an organization, that the
>> >> rest will basically follow.
>> >>
>> >> I used Noisebridge as a counterexample to THAT point.
>> >>
>> >> Noisebridge is a great example of how organizations based on culture
>> >> and minimal policy can easily shift, even pushing its original members
>> >> out, simply by being unaware of how the rapid influx of new people
>> >> (ANY new people, not the oft-demonized Occupy and so on) changes the
>> >> culture by sheer weight.
>> >>
>> >> That's not the only lesson learned from the last 5 years at 2169
>> >> Mission St, but it is one of the biggest ones.
>> >>
>> >> Again: if you guys can't see past "at least we aren't Noisebridge",
>> >> you're never going to be able to learn from our mistakes.
>> >>
>> >> --Naomi
>> >>
>> >>
>> >>
>> >>
>> >> On Wed, Jul 2, 2014 at 6:08 PM, Al Billings <albill at openbuddha.com>
>> >> wrote:
>> >>> Naomi,
>> >>>
>> >>> sudoroom has the same problems as noisebridge because it explicitly
>> >>> modeled
>> >>> itself on noisebridge with consensus decision making, an open door
>> >>> policy to
>> >>> the street, and a political, social justice mission. They've gone as
>> >>> far as
>> >>> to say a space isn't a real hackerspace if it isn't political.
>> >>>
>> >>> Your counterexample proves the meta point...
>> >>
>> >>
>> >
>> >
>> > _______________________________________________
>> > Discuss mailing list
>> > Discuss at lists.hackerspaces.org
>> > http://lists.hackerspaces.org/mailman/listinfo/discuss
>> _______________________________________________
>> Discuss mailing list
>> Discuss at lists.hackerspaces.org
>> http://lists.hackerspaces.org/mailman/listinfo/discuss
>
> _______________________________________________
> Discuss mailing list
> Discuss at lists.hackerspaces.org
> http://lists.hackerspaces.org/mailman/listinfo/discuss
>