Talk:Hackerspace Design Patterns 2.0: Difference between revisions

From Noisebridge
Jump to navigation Jump to search
(Added suggestion for automatic payments.)
No edit summary
Line 93: Line 93:
- David
- David
Totalism Hackbase/Lanzarote, Canary Islands, Spain
Totalism Hackbase/Lanzarote, Canary Islands, Spain
People have strong opinions.  When talk of a discussion comes up, people email (or irc, etc), and say they aren't coming to discuss, but they are dead against it.  Discussion is stifled.  (Especially disruptive for groups making decisions with consensus, but disruptive for majority-vote, too.)  Solution: stop online discussion, move comments and discussion to in-person (or, to one-on-one, for someone who is part of the community is out of town at the moment).

Revision as of 09:27, 22 July 2015

Mission Statement(s), e.g., "Excellence" -- Enforcing and Re-inforcing Hacking "Purity"

Imposter Syndrome Anti-Pattern -- *everyone* has it

Shower Pattern now has an Anti-Pattern,
as does the Kitchen Pattern.

Territorial Anti-Pattern: people carving out a spot in the space (others too uncomfortable to use "their" space). People who belong tend to drift away.

Reboot Pattern: turn off and on. Invite people to help re-create the space -- creates excitement as everyone feels part of creating the space (like when it's new).

Greeters Pattern: welcome everyone, give tour which includes what space is and is not about. Supports Cultural Immune System Pattern.

Conflict Resolution Pattern

-- having a system helps!

Gender Equality at spaces

Burnout by community members (or board/officers)

Organizational structures: anarchy, board-run

Decision-making: consensus, majority vote

Cultural Immune System Pattern:
Problem: You want people in your hackerspace who are good for your community, and want to keep them happy and safe -- and you don't want to attract people who will hurt your community or drive away people who are good for your community.
Solution: Social control, "Cultural immune system"

Simple diagram of Hackerspace Time-loop Pattern:
New People & Ideas ====> Productivity & Growth ====> Entrenchment/Stagnation
/\ ....................................................................................................... ||
|| ....................................................................................................... ||
|| ....................................................................................................... ||
|| ....................................................................................................... \/
Entrenchment/Stagnation <=== Productivity & Growth <=== New People & Ideas


http://geekfeminism.wikia.com/wiki/Feminist_hackerspace_design_patterns

Periodic Show & Tell get-togethers (but don't want to scare people off who aren't "experts" -- see "Imposter Syndrom" Anti-Pattern)

Greet new people, give tour, share about the space's culture from the start.

Remind people when they miss a membership dues payment. Alternatively, require all members pay via an automatic payment system (like paypal).

Automate as much of the busy-work as possible (help avoid burn-out).

Cleanliness -- things can get messy quickly at hackerspaces.

Project storage management isn't easy.

Getting rid of things that aren't used -- otherwise things pile up and get in the way.

Accepting donations is cool -- having policies on when to say "no" to a donation is important.

What draws people to hackerspaces? Community (first), Tools & Equip (second). Getting new stuff should attract more people for the Community.

Maintaining tools & equipment -- how to do it?

Rules & Procedures -- how to disseminate them so everyone knows them? Keep the rules simple to understand. Put up signs that are easy to read at a glance to remind people where needed.

Attract people with Classes and Workshops and Talks and Demos.

Safety for people and tools & equipment: have classes. Some spaces have certification.

Empower people to spread the joy and attract people to your space.

Get rid of old stuffs that are no longer being used, and re-make spaces within your hackerspace that are no longer being used -- this makes way for what's growing in your hackerspace.

The name can attract or repel people. E.g., "Lab" tends to attract males.

How to communicate? Email lists can be unwieldy (and attract trolls). IRC can be a time-sink (and attract trolls). User forum. Wiki. Slack (and non-corporate versions). Usually, there's not a single method that works for all community members.

Security: cameras? Non-anonymous door access system?

Separate tools for space maintenance, or for special purposes?


Notes from Red Mountain Makers, by Shirley Hicks:
http://www.velochicdesign.com/category/makerspaces/

How to Start a Hackerspace on the Adafruit blog, by Eric Michaud:
https://blog.adafruit.com/2012/11/12/how-to-start-a-hackerspace/

How to Create a Hackerspace, by Mitch Altman:
http://makezine.com/magazine/how-to-create-a-hackerspace/

I've updated this "1.0" pattern some time ago to reflect developments that hackbases brought. https://wiki.hackerspaces.org/The_Roommate_Anti-Pattern https://hackerspaces.org/wiki/Hackbases - David Totalism Hackbase/Lanzarote, Canary Islands, Spain


People have strong opinions. When talk of a discussion comes up, people email (or irc, etc), and say they aren't coming to discuss, but they are dead against it. Discussion is stifled. (Especially disruptive for groups making decisions with consensus, but disruptive for majority-vote, too.) Solution: stop online discussion, move comments and discussion to in-person (or, to one-on-one, for someone who is part of the community is out of town at the moment).