Received: by 10.66.88.200 with SMTP id bi8mr1181387pab.27.1348918359891;
Sat, 29 Sep 2012 04:32:39 -0700 (PDT)
X-BeenThere: london-hack-space@googlegroups.com
Received: by 10.68.242.38 with SMTP id wn6ls17537491pbc.8.gmail; Sat, 29 Sep
2012 04:32:36 -0700 (PDT)
Received: by 10.66.84.41 with SMTP id v9mr3170639pay.43.1348918356516;
Sat, 29 Sep 2012 04:32:36 -0700 (PDT)
Received: by 10.66.84.41 with SMTP id v9mr3170638pay.43.1348918356505;
Sat, 29 Sep 2012 04:32:36 -0700 (PDT)
Return-Path: <sam.lindenrat...@gmail.com>
Received: from mail-pa0-f54.google.com (mail-pa0-f54.google.com [209.85.220.54])
by gmr-mx.google.com with ESMTPS id js4si348900pbb.2.2012.09.29.04.32.36
(version=TLSv1/SSLv3 cipher=OTHER);
Sat, 29 Sep 2012 04:32:36 -0700 (PDT)
Received-SPF: pass (google.com: domain of sam.lindenrat...@gmail.com designates 209.85.220.54 as permitted sender) client-ip=209.85.220.54;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of sam.lindenrat...@gmail.com designates 209.85.220.54 as permitted sender) smtp.mail=sam.lindenrat...@gmail.com; dkim=pass header...@gmail.com
Received: by padbi1 with SMTP id bi1so3367723pad.13
for <london-hack-space@googlegroups.com>; Sat, 29 Sep 2012 04:32:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:content-type;
bh=6TzTjfIWatHn7AIveflaTeSHz7o7kcsROhR9infcapw=;
b=1AnaomosBJksT+k5lnzNvapSBIBCnvJ2nP9RDYkCpb9fNPDImeCU5KzQuv+jMo/Rbb
5t62arFjVDcRUmuYRchQpkuwunIyqEK9lttVb2YaiQB/g3LgOJ0cd7clwzqCwZs53AEJ
4uMpH6s9QQZLM5D0zQ43/HtTw5wvxmujlMFjbIOvkn8nbX3OeWw7YbPel/h1/Rf4w8AP
Eg9neLBZo5wEBEJhARf70qQ4oKhUPx1ghWBc9XR0td/jGEjXpSTujZCdGneJpVn3CBqq
PLqjjsKuo38ZN0OBnC5vVrJUt5UVJayiqVHqDecqraSwHT5vdAnh/Pi8z7HSuOP3u4Km
eRfw==
Received: by 10.66.73.9 with SMTP id h9mr23794699pav.76.1348918356307; Sat, 29
Sep 2012 04:32:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.23.37 with HTTP; Sat, 29 Sep 2012 04:32:15 -0700 (PDT)
In-Reply-To: <1658B4D1-36B5-4E07-8F5A-08D73AFAF...@gmail.com>
References: <592E49D7-AE03-45F4-8989-2B17623ED...@gmail.com> <1658B4D1-36B5-4E07-8F5A-08D73AFAF...@gmail.com>
From: SamLR <sam.lindenrat...@gmail.com>
Date: Sat, 29 Sep 2012 12:32:15 +0100
Message-ID: <CAGqn4cZbY7kJZDSA5BRXbwhm7-ZCtH0=YjoV0fmKU7vaUw9...@mail.gmail.com>
Subject: Re: [london-hack-space] Re: State of the LHS community: subgroups as
a social mechanism to resource management problems?
To: london-hack-space@googlegroups.com
Content-Type: multipart/alternative; boundary=f46d042f9e9e75700b04cad5871f
--f46d042f9e9e75700b04cad5871f
Content-Type: text/plain; charset=ISO-8859-1
Hey Martin,
Some excellent suggestions there. I think a (bi-weekly/monthly?) members
only meeting would be very good.
The subgroups idea is also nice, assuming we can get enough of the members
involved with infrastructure subgroups to keep the place ticking over
nicely without the same 5 or 6 people being _all_ the groups, I'd almost be
tempted to say that if you e.g. lead a group and commit to making sure the
workshop is tidy we'll waive membership fee (donations still welcome from
those that want to give them).
I know that having 'paid' members is an idea that has been shot down
several times but we have enough members that to run the workshop I'd be
inclined to say we need someone who's job it is to make sure that we have
the required consumables, that stuff is safe, that the wood pile is tidy
etc.
A lot of the rage re tidiness is that a lot gets done on a boom/bust cycle
(i.e. once every few weeks someone rage cleans) rather than
steady maintenance which is what is really needed.
S
On 28 September 2012 17:32, Martin Dittus <deks...@gmail.com> wrote:
>
> Just adding a few links to Hackerspace design patterns that relate to the
> three suggestions.
>
>
> On 28 Sep 2012, at 16:26, Martin Dittus wrote:
>
> > 1. Subgroups
>
> http://hackerspaces.org/wiki/The_Infrastructure_Pattern
> http://hackerspaces.org/wiki/The_Strong_Personalities_Pattern
> http://hackerspaces.org/wiki/The_Responsibilty_Pattern
>
> (I've not found a design pattern to manage very large communities, but
> experience shows that social groups above a few dozen members tend to yield
> challenges that are hard to address, and community segmentation can help.
> EMF teams and villages worked incredibly well.)
>
>
> > 2. Meetings
>
> http://hackerspaces.org/wiki/The_Plenum_Pattern
> http://hackerspaces.org/wiki/The_Democracy_Pattern
> http://hackerspaces.org/wiki/The_Debate_Culture_Pattern
> http://hackerspaces.org/wiki/The_OpenChaos_Pattern
>
> (The "plenum" is one of the most widely adopted design patterns that we
> don't currently use. I'm told other groups have had great success with it.)
>
>
> > 3. Mentors
>
> http://hackerspaces.org/wiki/The_Command_Pattern
> http://hackerspaces.org/wiki/The_U23_Pattern
> http://hackerspaces.org/wiki/The_sudo_leadership_Pattern
> http://hackerspaces.org/wiki/The_Private_Talk_Pattern
>
> (I think we want to avoid introducing formal lines of authority, but the
> trustees could use some community support.)
>
> m.
--f46d042f9e9e75700b04cad5871f
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Hey Martin,=A0<div><br></div><div>Some excellent suggestions there. I think=
a (bi-weekly/monthly?) members only meeting would be very good.</div><div>=
<br></div><div>The subgroups idea is also nice, assuming we can get enough =
of the members involved with infrastructure subgroups to keep the place tic=
king over nicely without the same 5 or 6 people being _all_ the groups, I&#=
39;d almost be tempted to say that if you e.g. lead a group and commit to m=
aking sure the workshop is tidy we'll waive membership fee (donations s=
till welcome from those that want to give them).=A0</div>
<div><br></div><div>I know that having 'paid' members is an idea th=
at has been shot down several times but we have enough members that to run =
the workshop I'd be inclined to say we need someone who's job it is=
to make sure that we have the required consumables, that stuff is safe, th=
at the wood pile is tidy etc.</div>
<div><br></div><div>A lot of the rage re tidiness is that a lot gets done o=
n a boom/bust cycle (i.e. once every few weeks someone rage cleans) rather =
than steady=A0maintenance=A0which is what is really needed.=A0</div><div><b=
r>
</div><div>S<br><br><div class=3D"gmail_quote">On 28 September 2012 17:32, =
Martin Dittus <span dir=3D"ltr"><<a href=3D"mailto:deks...@gmail.com" ta=
rget=3D"_blank">deks...@gmail.com</a>></span> wrote:<br><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex">
<br>
Just adding a few links to Hackerspace design patterns that relate to the t=
hree suggestions.<br>
<br>
<br>
On 28 Sep 2012, at 16:26, Martin Dittus wrote:<br>
<br>
> 1. Subgroups<br>
<br>
<a href=3D"http://hackerspaces.org/wiki/The_Infrastructure_Pattern" target=
=3D"_blank">http://hackerspaces.org/wiki/The_Infrastructure_Pattern</a><br>
<a href=3D"http://hackerspaces.org/wiki/The_Strong_Personalities_Pattern" t=
arget=3D"_blank">http://hackerspaces.org/wiki/The_Strong_Personalities_Patt=
ern</a><br>
<a href=3D"http://hackerspaces.org/wiki/The_Responsibilty_Pattern" target=
=3D"_blank">http://hackerspaces.org/wiki/The_Responsibilty_Pattern</a><br>
<br>
(I've not found a design pattern to manage very large communities, but =
experience shows that social groups above a few dozen members tend to yield=
challenges that are hard to address, and community segmentation can help. =
EMF teams and villages worked incredibly well.)<br>
<br>
<br>
> 2. Meetings<br>
<br>
<a href=3D"http://hackerspaces.org/wiki/The_Plenum_Pattern" target=3D"_blan=
k">http://hackerspaces.org/wiki/The_Plenum_Pattern</a><br>
<a href=3D"http://hackerspaces.org/wiki/The_Democracy_Pattern" target=3D"_b=
lank">http://hackerspaces.org/wiki/The_Democracy_Pattern</a><br>
<a href=3D"http://hackerspaces.org/wiki/The_Debate_Culture_Pattern" target=
=3D"_blank">http://hackerspaces.org/wiki/The_Debate_Culture_Pattern</a><br>
<a href=3D"http://hackerspaces.org/wiki/The_OpenChaos_Pattern" target=3D"_b=
lank">http://hackerspaces.org/wiki/The_OpenChaos_Pattern</a><br>
<br>
(The "plenum" is one of the most widely adopted design patterns t=
hat we don't currently use. I'm told other groups have had great su=
ccess with it.)<br>
<br>
<br>
> 3. Mentors<br>
<br>
<a href=3D"http://hackerspaces.org/wiki/The_Command_Pattern" target=3D"_bla=
nk">http://hackerspaces.org/wiki/The_Command_Pattern</a><br>
<a href=3D"http://hackerspaces.org/wiki/The_U23_Pattern" target=3D"_blank">=
http://hackerspaces.org/wiki/The_U23_Pattern</a><br>
<a href=3D"http://hackerspaces.org/wiki/The_sudo_leadership_Pattern" target=
=3D"_blank">http://hackerspaces.org/wiki/The_sudo_leadership_Pattern</a><br=
>
<a href=3D"http://hackerspaces.org/wiki/The_Private_Talk_Pattern" target=3D=
"_blank">http://hackerspaces.org/wiki/The_Private_Talk_Pattern</a><br>
<br>
(I think we want to avoid introducing formal lines of authority, but the tr=
ustees could use some community support.)<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
m.</font></span></blockquote></div><br></div>
--f46d042f9e9e75700b04cad5871f--
Message from discussion State of the LHS community: subgroups as a social mechanism to resource management problems?
| Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy |
| ©2013 Google |