Editing Structure and organization (section)

== Notes from Design Pattern on organization ==
Here is a translation of the orginazational section of the [http://hackerspaces.org/Hacker-Space-Design-Patterns.pdf hackerspace design pattern], posted here so that we can edit/comment on them for our space. [http://hackerspaces.org/wiki/Documentation hackerspaces.org] has a number of good resources to look over, including bylaws and regulations of other hacker spaces around the country. 

=== The Plenum Pattern ===
==== Problem ====
You want to resolve internal conﬂicts, exercise democratic decision 
making, and discuss recent issues and future plans. 
==== Implementation ====
Have a regular meeting with all members, if possible. Have an 
agenda and set goals. Make people commit themselves to tasks. 
Write down minutes of the meeting and post them on a mailing 
list and/or Wiki. Go for the only date that works: once a week. 
Weird dates like “ﬁrst full-moon after the third Friday” will never 
work. Likewise, every other week or anything similar won’t work 
either. 

=== The Tuesday Pattern ===
==== Problem ====
Every weekday sucks. You will not ﬁnd any day when every hacker 
can attend a meeting. Someone always has an appointment. 
==== Implementation ====
Meet on Tuesday. Since all days are equally bad, just pick 
Tuesday. End of discussion.

=== The OpenChaos Pattern ===
==== Problem ==== 
You want to draw in new people and provide an interface to the 
outside world. 
==== Implementation ====
Have a monthly, public, and open lecture, talk or workshop. 
Announce it at your local time (no UTC, CEST, EST or something 
else). Invite interesting visitors to your regular meetings and don’t 
tell the weirdos. 

=== The U23 Pattern ===
==== Problem ====
Your older members graduate from college or get married. Your 
space needs fresh blood. 
==== Implementation ====
Recruit young people through a challenge you set up for them, in 
the form of a course that spans several weeks. Overwhelm them 
with problems from hardware and software hacking and let them 
solve them in teams. Prepare for the challenge and tutor them, 
but give them room to experiment. Retire after the team building 
and let the smartest of the young ones run the space.

=== The Sine Curve Pattern ===
==== Problem ====
You did everything right. You had some big events and a nice time 
in your shiny hacker space. But after some time the enthusiasm 
goes away and your projects are stagnating. 
==== Implementation ====
Peak enthusiasm at a hacker space has the form of a sine curve 
with a cycle duration of four years. Keep the hacker space 
running, even if the feel-good factor is temporarily on holiday. 
Chances are good that your space will be awesome again in two 
years. Don’t give up! Maybe an exciting new member will knock 
on your door tomorrow.