<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
After a lot of discussions and bikeshedding we set this system up.<br>
<a class="moz-txt-link-freetext" href="http://wiki.hackerspace.lu/wiki/Funding">http://wiki.hackerspace.lu/wiki/Funding</a><br>
Has been ok since a year.<br>
One may argue that a small group can vote against a project, but in
fact it can't. A no-vote gets transformed into a collective vote for
all members.<br>
So it's basis-democracy with a frontend of classic hierachy to
speedup decisions.<br>
<br>
Georges<br>
<br>
<div class="moz-cite-prefix">On 02/26/2014 11:43 PM, Enabrin Tain
wrote:<br>
</div>
<blockquote
cite="mid:1393454622.42297.YahooMailNeo@web140403.mail.bf1.yahoo.com"
type="cite">
<div style="color:#000; background-color:#fff;
font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial,
Lucida Grande, sans-serif;font-size:10pt">
<div><br>
</div>
<div style="color: rgb(0, 0, 0); font-size: 13.3333px;
font-family: HelveticaNeue,Helvetica
Neue,Helvetica,Arial,Lucida Grande,sans-serif;
background-color: transparent; font-style: normal;"><span>Hi
Torrie,</span></div>
<div class="yui_3_13_0_ym1_9_1393436134559_81" style="color:
rgb(0, 0, 0); font-size: 13.3333px; font-family:
HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida
Grande,sans-serif; background-color: transparent; font-style:
normal;"><span><span>A budget is the first priority of a
Hackerspace, because your facility is your contribution to
the community. If you can't keep the bills paid, then the
other stuff gets way harder. </span>We have committees
for various topics of interest: Facilities Committee,
Finance Committee, Gardening, Crafts and Sewing; that sort
of thing. They are basically Communities of Interest, and
they are the people who do the diligence and grunt work for
the Hackerspace. We've done <a moz-do-not-send="true"
href="https://256.makerslocal.org/wiki/Member_Grants_2012">grants</a>
in the past where people put in bids for projects and the
membership voted on them. Maybe he is thinking that doing
something like that could be more constructive? One of the
grant proposals that passed was an Event Purse to help fund
events at the Space.<br>
</span></div>
<div style="color: rgb(0, 0, 0); font-size: 13.3333px;
font-family: HelveticaNeue,Helvetica
Neue,Helvetica,Arial,Lucida Grande,sans-serif;
background-color: transparent; font-style: normal;"><span></span><span>It's
entirely possible that he's trying to help but feels like he
doesn't have enough information to help effectively. If
that's the case, it could be an opportunity to build your
Finance COI.<br>
</span></div>
<div>Best wishes, <br>
</div>
<div> Phil Showers<br>
<br>
<a moz-do-not-send="true" rel="nofollow" target="_blank"
href="https://256.makerslocal.org/wiki/User:Enabrintain"><span
style="color:rgb(0, 0, 255);"><span
style="text-decoration:underline;">My Projects</span></span></a><br>
</div>
<br>
<div style="font-family: HelveticaNeue, Helvetica Neue,
Helvetica, Arial, Lucida Grande, sans-serif; font-size: 10pt;">
<div style="font-family: HelveticaNeue, Helvetica Neue,
Helvetica, Arial, Lucida Grande, sans-serif; font-size:
12pt;">
<div class="y_msg_container"><br>
----------------------------------------------------------------------<br>
<br>
<br>
Message: 5<br>
Date: Wed, 26 Feb 2014 14:28:10 -0500<br>
From: Edward L Platt <<a moz-do-not-send="true"
ymailto="mailto:ed@elplatt.com"
href="mailto:ed@elplatt.com">ed@elplatt.com</a>><br>
To: Hackerspaces General Discussion List<br>
<<a moz-do-not-send="true"
ymailto="mailto:discuss@lists.hackerspaces.org"
href="mailto:discuss@lists.hackerspaces.org">discuss@lists.hackerspaces.org</a>><br>
Subject: Re: [hackerspaces] Dealing with micromanagement
of hackers<br>
Message-ID:<br>
<CAKb0FmF-eUdJBH=XAw+<a moz-do-not-send="true"
ymailto="mailto:XWux5yxALtMvQkPcSnR8JzAS9RACE6w@mail.gmail.com"
href="mailto:XWux5yxALtMvQkPcSnR8JzAS9RACE6w@mail.gmail.com">XWux5yxALtMvQkPcSnR8JzAS9RACE6w@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
It sounds like the member in question is doing the
*opposite* of<br>
micromanaging. If you want to take members' opinions into
account, some<br>
level of bureaucracy is inevitable and the goal should be
more effective,<br>
rather than less (or more), bureaucracy. Or, if you have
strong central<br>
leadership that gets to make decisions, that works to. I
can't tell which<br>
model you're striving for.<br>
<br>
Also, PSA: if you don't like meetings, committees are your
friend! You get<br>
to say "hey everyone who cares about X, go hash it out in
a focused session<br>
and bring back a concise report for everyone." Then if
someone wants to<br>
derail a general meeting with it, you can say "If you
really care about<br>
this issue, go join the committee." Way more efficient
than having<br>
everyone sit through discussion about everything.<br>
<br>
-Ed<br>
<br>
<br>
On Wed, Feb 26, 2014 at 1:08 PM, Bert Hartmann <<a
moz-do-not-send="true"
ymailto="mailto:berthartm@gmail.com"
href="mailto:berthartm@gmail.com">berthartm@gmail.com</a>>
wrote:<br>
<br>
> Hey Torrie,<br>
><br>
> I don't know anything about your space, so this is
all pure speculation on<br>
> my part, but if you don't have enough consensus to
pass a budget, perhaps<br>
> you do need to open up the discussion to more people
until they're<br>
> comfortable with the result? If you do have
consensus, then it shouldn't be<br>
> an issue, and just approve the budget and move
forward.<br>
><br>
> I know in New Jersey the law requires our non-profit
to have an annual<br>
> meeting with all the members about this time of year,
where we<br>
> traditionally pass a budget for the year, among other
things. Perhaps a<br>
> similar type of meeting for your group is healthy, so
that no matter what<br>
> process develops the budget (1 man and a spreadsheet
or 20 people in 20<br>
> meetings) there's a hard and fast deadline everyone's
working towards so it<br>
> doesn't get out of control and you end up with a
workable result to present<br>
> the rest of the group (who will presumably keep on
hacking despite it).<br>
><br>
> Incidentally, to answer your last question: I've seen
the role of the<br>
> board as handling all the bureaucratic stuff (rent,
government filings,<br>
> cleaning the bathroom, budget negotiations) so that
the hacking may go on<br>
> unimpeded for everyone else. Some of it's
unavoidable, the trick is just to<br>
> minimize the impact to the organization at large and
the members in<br>
> specific.<br>
><br>
> my 2 cents,<br>
> Bert<br>
><br>
><br>
> On Wed, Feb 26, 2014 at 11:08 AM, Torrie Fischer <<a
moz-do-not-send="true"
ymailto="mailto:tdfischer@hackerbots.net"
href="mailto:tdfischer@hackerbots.net">tdfischer@hackerbots.net</a><br>
> > wrote:<br>
><br>
>> Hi, discuss@!<br>
>><br>
>> Lately at my hackerspace, we've had a member who
is very interested in<br>
>> micromanaging the space. I'm currently both
treasurer and AWS sysadmin for<br>
>> synhak.org, where I proposed a budget to use some
grant money we received to<br>
>> secure 3 year funding of our infrastructure.<br>
>><br>
>> Time and time again, this member in question
wants to form a committee or<br>
>> some equally stifling bureaucratic structure to
analyze any change to the space<br>
>> under the guise of "investigating all the
options".<br>
>><br>
>> Micromanagement like this is totally against our
culture, but it seems<br>
>> that there are one or two others who go along
with it because it "makes sense".<br>
>><br>
>> Whats the best way to kill bureaucratic
micromanagement and protect the<br>
>> hacker ethos at a space?<br>
>> ____________________________________<br>
<br>
-- <br>
Edward L. Platt<br>
<a moz-do-not-send="true" href="http://elplatt.com/"
target="_blank">http://elplatt.com</a><br>
<a moz-do-not-send="true"
href="http://civic.mit.edu/users/elplatt"
target="_blank">http://civic.mit.edu/users/elplatt</a><br>
<a moz-do-not-send="true" href="http://i3detroit.com/"
target="_blank">http://i3detroit.com</a><br>
@elplatt <<a moz-do-not-send="true"
href="http://twitter.com/elplatt" target="_blank">http://twitter.com/elplatt</a>><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a moz-do-not-send="true"
href="http://lists.hackerspaces.org/pipermail/discuss/attachments/20140226/32dcd799/attachment-0001.html"
target="_blank">http://lists.hackerspaces.org/pipermail/discuss/attachments/20140226/32dcd799/attachment-0001.html</a>><br>
<br>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Discuss@lists.hackerspaces.org">Discuss@lists.hackerspaces.org</a>
<a class="moz-txt-link-freetext" href="http://lists.hackerspaces.org/mailman/listinfo/discuss">http://lists.hackerspaces.org/mailman/listinfo/discuss</a>
</pre>
</blockquote>
<br>
</body>
</html>