Received: by 10.180.104.38 with SMTP id gb6mr3972001wib.4.1352821338765;
        Tue, 13 Nov 2012 07:42:18 -0800 (PST)
X-BeenThere: london-hack-space@googlegroups.com
Received: by 10.180.77.228 with SMTP id v4ls8687559wiw.0.canary; Tue, 13 Nov
 2012 07:42:02 -0800 (PST)
Received: by 10.180.74.79 with SMTP id r15mr2379258wiv.4.1352821322370;
        Tue, 13 Nov 2012 07:42:02 -0800 (PST)
Received: by 10.180.74.79 with SMTP id r15mr2379257wiv.4.1352821322359;
        Tue, 13 Nov 2012 07:42:02 -0800 (PST)
Return-Path: <deks...@gmail.com>
Received: from mail-wi0-f173.google.com (mail-wi0-f173.google.com [209.85.212.173])
        by gmr-mx.google.com with ESMTPS id cn9si1070512wib.0.2012.11.13.07.42.02
        (version=TLSv1/SSLv3 cipher=OTHER);
        Tue, 13 Nov 2012 07:42:02 -0800 (PST)
Received-SPF: pass (google.com: domain of deks...@gmail.com designates 209.85.212.173 as permitted sender) client-ip=209.85.212.173;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of deks...@gmail.com designates 209.85.212.173 as permitted sender) smtp.mail=deks...@gmail.com; dkim=pass header...@gmail.com
Received: by mail-wi0-f173.google.com with SMTP id hm2so2860371wib.14
        for <london-hack-space@googlegroups.com>; Tue, 13 Nov 2012 07:42:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=subject:mime-version:content-type:from:in-reply-to:date
         :content-transfer-encoding:message-id:references:to:x-mailer;
        bh=wvFrFdO5tbsLtAmvNWZ4cyxj+C9Qs+9KlZn/FY10qCM=;
        b=MMdrha+niu46gy6/HvmlE20VtZ5xwnucbSJd4Qw7UjUv+HZwNzM0GFnAAwTq41121a
         3HduXUVrEll5CM8/Z0xl0Uv3/0wM4qn5gqMHABF4gersCQxGCFQF4tqsccXE0S0QvVgc
         UzLgopf6V5EeQVvkwvZYVxPwuT1ShL9Q0u3ZpKF3Rl59Ive8iF1OBIf23JJ9QUhzqM63
         HllrTXQc27ZEvGMlHuTCz6n1wGGQD8J+jZXpWFioXwU0DUxYUygMuha0T8d0NI14tH4q
         9mypZOmLnG/CeK1CEPmxNZsmIQ3BS79MXpIZsjYuYLaOYGeAfw9eBCKUEAe51lDQ/WEr
         u1Zw==
Received: by 10.180.102.166 with SMTP id fp6mr21060627wib.9.1352821322139;
        Tue, 13 Nov 2012 07:42:02 -0800 (PST)
Return-Path: <deks...@gmail.com>
Received: from [192.168.2.43] (host86-156-54-255.range86-156.btcentralplus.com. [86.156.54.255])
        by mx.google.com with ESMTPS id ec3sm7174653wib.10.2012.11.13.07.41.58
        (version=TLSv1/SSLv3 cipher=OTHER);
        Tue, 13 Nov 2012 07:42:01 -0800 (PST)
Subject: Re: [london-hack-space] How to make structural changes to our organisation?
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Martin Dittus <deks...@gmail.com>
In-Reply-To: <CAC9rG2j4mJ-Yo10gRxdz4Q0bXzNGjVHjvEwJB5Lhf=TBX8m...@mail.gmail.com>
Date: Tue, 13 Nov 2012 15:41:57 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <0E717A89-6C87-40B7-89F1-03E8CD392...@gmail.com>
References: <C371D82A-B673-4A15-AF61-CBB76F46B...@gmail.com> <bef9dd6f-6cd9-4b37-838b-06607760a...@d3g2000vbj.googlegroups.com> <FEABB943-51D6-4FE2-922B-187B8907F...@gmail.com> <CAC9rG2j4mJ-Yo10gRxdz4Q0bXzNGjVHjvEwJB5Lhf=TBX8m...@mail.gmail.com>
To: london-hack-space@googlegroups.com
X-Mailer: Apple Mail (2.1283)

Yes, as a general approach (which we are already following); although I =
think we can now also describe more specific instances for this.

Random examples of frequent LHS activities:
- someone organises a pledge drive
- someone organises an event
- someone wants to store a work-in-progress

For each of these we could describe a design pattern that broadly =
describes how to go about making these happen. (In several cases we =
already have documentation, albeit spread across the wiki.)

Other activities are currently not as well-established, and members =
could benefit from some guidance:
- someone wants to start a new subgroup
- someone wants to organise a cleanup session
- someone wants to mediate in a conflict between members

In almost all cases members currently have to come up with their own =
ways of doing these things, which may act as an impediment. If instead =
there's a widely accepted (and documented!) practice that is frequently =
refined people may be encouraged to do these things more often.

m.


On 13 Nov 2012, at 14:57, Russ Garrett wrote:

> On 13 November 2012 14:53, Martin Dittus <deks...@gmail.com> wrote:
>> Another thought I had --  instead of "institutionalising" new =
organisational structures (putting specific people in particular =
positions) we could describe them as situational patterns. This is in =
the spirit of a fluid and member-driven organisation, and completely =
bypasses any need for "ratification."
>=20
> Sounds like you're describing this:
> http://hackerspaces.org/wiki/The_sudo_leadership_Pattern
>=20
> --
> Russ Garrett
> r...@garrett.co.uk