<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
-----BEGIN PGP SIGNED MESSAGE----- <br>
Hash: SHA1 <br>
<br>
(with limited information of what transpired)<br>
<br>
I don't know how your space was setup legally (NFP, charity or
otherwise) but this seems horribly illegal, not to mention it sounds
like they're taking actions that the membership should be able to
dispute and dissolve the board over.<br>
<br>
In Canada there is legal recourse if our directors were to say,
dissolve the corporation, empty the accounts and leave with the
equipment. If you were setup as a co-op or 501c3 I have to think
something similar applies in the states.<br>
<br>
Ben<br>
<br>
On 7/2/2014 9:32 AM, Torrie Fischer wrote:<br>
<span style="white-space: pre;">> On Wednesday, July 02, 2014
13:44:01 David Potocnik wrote:<br>
>> There's another perspective to this.<br>
>> I guess Torrie & the hackers of Ackron are going to
be okay - they<br>
>> started a new space right? They moved their stuff and got
another<br>
>> lease and all is well?<br>
><br>
> Nope. Board took everything. They also took the $15k in the
banking account <br>
> and moved it to some other bank without informing the
membership or anything, <br>
> and is disregarding the portions of the bylaws that
explicitly state such <br>
> things need to have transparency.<br>
><br>
>><br>
>> "Advice I give most folks starting a hackerspace, start a
community<br>
>> first. Find the people you want to start the space
with. Worry about<br>
>> that. because at the end of the day, even if you don't
have a space,<br>
>> that community is worth way way more."<br>
>><br>
>> ...Or just simplify building spaces (sharing protocols
& know-how),<br>
>> build a lot of them and cross-pollinate (travel, hang
out). Fork,<br>
>> collaborate, merge. Set up varieties, name them and setup<br>
>> instances of them. Find and argue about good practices
and patterns<br>
>> with whoever comes to this platform.<br>
>> As the thing progresses on we'll keep having a clearer
and clearer<br>
>> cartography of different hacker belief systems, and a
better idea of<br>
>> how they can and cannot coexist.<br>
>><br>
>> There is the more stable isotopos: Coworking spaces,
Makerspaces, Fablabs.<br>
>> I believe Hackerspaces and Hackbases (live-in
hackerspaces) should be<br>
>> unstable, and definitely not without politics.<br>
>> They should be, and sometimes are, avantgarde
experimental political<br>
>> machines.<br>
><br>
> Well said. One should be permitted to hack a hackerspace,
though in a non-<br>
> destructive fashion.<br>
><br>
>><br>
>> David<br>
>> from CHT#1 hackbase /\/
<a class="moz-txt-link-freetext" href="http://hackerspaces.org/wiki/Cyberhippietotalism">http://hackerspaces.org/wiki/Cyberhippietotalism</a><br>
>><br>
>> On 2 July 2014 04:07, Ryan Rix <a class="moz-txt-link-rfc2396E" href="mailto:ry@n.rix.si"><ry@n.rix.si></a> wrote:<br>
>>> matt <a class="moz-txt-link-rfc2396E" href="mailto:matt@nycresistor.com"><matt@nycresistor.com></a> writes:<br>
>>>> I think this boils down to the dichotomy of
hackerspace vs co-working<br>
>>>> space.<br>
>>>><br>
>>>> If you build up infrastructure and expect a
community to show up in<br>
>>>> it, don't be surprised if more than one community
shows up, or the<br>
>>>> community that shows up is not one you want to be
a part of.<br>
>>>><br>
>>>> Noisebridge suffers the tragedy of the commons in
a pretty severe<br>
>>>> way... having had mole people living in their
basement and bi-polar<br>
>>>> homeless people show up and and claim they are
'sleep hacking'.<br>
>>>><br>
>>>> That's not what I am talking about. What I am
talking about is the<br>
>>>> last line in that piece :<br>
>>>><br>
>>>> "A lot of this can be traced to our collective
inability to remember<br>
>>>> our core pillars of consensus, excellence, and
do-ocracy. There is no<br>
>>>> one person or event that can be blamed. As a
community, we failed to<br>
>>>> hold close the values we had. We were hacked by
policy hackers."<br>
>>>><br>
>>>> Now I don't know anything about synhak... so I am
just going to speak<br>
>>>> to the perspective brought forth by the person
who wrote this piece.<br>
>>>> This is a person who enjoyed the community that
arrived at synhak in<br>
>>>> the early days. As the space grew and changed and
time went on, so did<br>
>>>> the culture and so did the community.<br>
>>>><br>
>>>> I think Torrie is talking specific solutions but
not seeing the forest<br>
>>>> through the trees. When torrie talks about common
values along side<br>
>>>> mission statement, and limiting growth of new
membership. What she is<br>
>>>> really talking about is fostering a community
rather than<br>
>>>> infrastructure. She's focusing more on being with
the people she wants<br>
>>>> to be with, than focusing on building a space.<br>
>>>><br>
>>>> And I think that has worked out very well for NYC
Resistor. We like<br>
>>>> each other. We've liked each other with fairly
decent success for 5-6<br>
>>>> years. And while folks have grown apart and there
has been some<br>
>>>> inevitable culture shift. The community has
remained strong.<br>
>>>><br>
>>>> So, the answer is simple. Synhak like noisebridge
built a space. And<br>
>>>> communities fought for it, and some took it and
some lost it. Much<br>
>>>> like noisebridge. NYC Resistor built a community
in a coffee shop...<br>
>>>> everything else came later.<br>
>>>><br>
>>>> Advice I give most folks starting a hackerspace,
start a community<br>
>>>> first. Find the people you want to start the
space with. Worry about<br>
>>>> that. because at the end of the day, even if you
don't have a space,<br>
>>>> that community is worth way way more.<br>
>>><br>
>>> Well written, Matt.<br>
>>><br>
>>> r<br>
>>> _______________________________________________<br>
>>> Discuss mailing list<br>
>>> <a class="moz-txt-link-abbreviated" href="mailto:Discuss@lists.hackerspaces.org">Discuss@lists.hackerspaces.org</a><br>
>>>
<a class="moz-txt-link-freetext" href="http://lists.hackerspaces.org/mailman/listinfo/discuss">http://lists.hackerspaces.org/mailman/listinfo/discuss</a><br>
>><br>
>> _______________________________________________<br>
>> Discuss mailing list<br>
>> <a class="moz-txt-link-abbreviated" href="mailto:Discuss@lists.hackerspaces.org">Discuss@lists.hackerspaces.org</a><br>
>> <a class="moz-txt-link-freetext" href="http://lists.hackerspaces.org/mailman/listinfo/discuss">http://lists.hackerspaces.org/mailman/listinfo/discuss</a><br>
>><br>
>><br>
>> _______________________________________________<br>
>> Discuss mailing list<br>
>> <a class="moz-txt-link-abbreviated" href="mailto:Discuss@lists.hackerspaces.org">Discuss@lists.hackerspaces.org</a><br>
>> <a class="moz-txt-link-freetext" href="http://lists.hackerspaces.org/mailman/listinfo/discuss">http://lists.hackerspaces.org/mailman/listinfo/discuss</a></span><br>
<br>
-----BEGIN PGP SIGNATURE-----
<br>
Version: GnuPG v2.0.22 (MingW32)
<br>
<br>
iQEcBAEBAgAGBQJTtAzcAAoJEMlZqYK/WZStFVsH/1iufqsKS3cjZLs34Uslc8+W
<br>
4jnxoCOKO7Ymsoo7qNy6krLiIjKOKU9xnaxbPUDiEHXBZbONUPCKMRyaVgQnJ0E4
<br>
kieHV77opFcyf0kVr+BuaZO6W3jgEels1KX8IRGXFKyMJ0Vk/lhXkUpzmHpXKps1
<br>
SMfrKo2b/EziFCked7WwGEPYwDMrmZ2/XlconDNE+50+58B5OMlc9v/MldcaODTi
<br>
/5k+nWnQxZZIVclGF1w9OTulNUz3ujFnGOtjydBOMr0aL5lAPjmY0IYz6sncrjUK
<br>
EBUZBqlLHDcP+wNKkVQujZ+jWAbb56DGHF0zpJ3SeFk76F07dK+Ht3omr/b5FY0=
<br>
=ds6c
<br>
-----END PGP SIGNATURE-----
<br>
<br>
</body>
</html>