Hackerspace Design Patterns 2.0 - Revision history

AkroniumEddie: added link abt TMI/Rules-itis

2015-09-06T19:11:06Z

added link abt TMI/Rules-itis

AkroniumEddie: grouped Rules and money $tuff together

2015-09-06T18:57:46Z

grouped Rules and money $tuff together

Show changes

AkroniumEddie: turned into past tense and enhanced formatting

2015-09-06T18:39:04Z

turned into past tense and enhanced formatting

Show changes

68.61.232.220: Add patterns from i3 Detroit

2015-09-05T13:25:39Z

Add patterns from i3 Detroit

@@ Line 178: / Line 178: @@
-Ed Platt's new Patterns:<br>
+'''Replacement Pattern'''
-https://elplatt.com/new-hackerspace-design-patterns
+([https://elplatt.com/new-hackerspace-design-patterns source])<br>
 '''Reboot Pattern''':<br>

Maltman23: /* Wanted: your Hackerspace Design Patterns */

2015-08-09T21:06:13Z

Wanted: your Hackerspace Design Patterns

← Older revision		Revision as of 14:06, 9 August 2015
Line 12:		Line 12:
	[https://events.ccc.de/camp/2015/wiki/Main_Page CCCamp2015]<br>		[https://events.ccc.de/camp/2015/wiki/Main_Page CCCamp2015]<br>
	'''When''': [https://events.ccc.de/camp/2015/wiki/Village:Norton%27s_Obscure_Phoggy_Embassy#calendar Day 3], Saturday 15-August from 11:15am to 1:30pm.<br>		'''When''': [https://events.ccc.de/camp/2015/wiki/Village:Norton%27s_Obscure_Phoggy_Embassy#calendar Day 3], Saturday 15-August from 11:15am to 1:30pm.<br>
	'''Where''': [https://events.ccc.de/camp/2015/wiki/Village:Norton%27s_Obscure_Phoggy_Embassy Norton's Obscure Phoggy Embassy (NOPE) Village] (aka: the Noisebridge / Sudo Room Village<br>		'''Where''': [https://events.ccc.de/camp/2015/wiki/Village:Norton%27s_Obscure_Phoggy_Embassy Norton's Obscure Phoggy Embassy (NOPE) Village] (aka: the Noisebridge / Sudo Room Village)<br>
	[https://events.ccc.de/camp/2015/wiki/Session:Hackerspace_Design_Patterns_2.0_Workshop https://events.ccc.de/camp/2015/wiki/Session:Hackerspace_Design_Patterns_2.0_Workshop]		[https://events.ccc.de/camp/2015/wiki/Session:Hackerspace_Design_Patterns_2.0_Workshop https://events.ccc.de/camp/2015/wiki/Session:Hackerspace_Design_Patterns_2.0_Workshop]

Maltman23: /* Wanted: your Hackerspace Design Patterns */

2015-08-09T21:03:30Z

Wanted: your Hackerspace Design Patterns

← Older revision		Revision as of 14:03, 9 August 2015
Line 2:		Line 2:

	I submitted a proposal for a talk at [http://events.ccc.de/camp/2015/wiki CCCamp 2015]: an updated presentation of the '''Hackerspace Design Patterns'''. It was accepted!		I submitted a proposal for a talk at [http://events.ccc.de/camp/2015/wiki CCCamp 2015]: an updated presentation of the '''Hackerspace Design Patterns'''. It was accepted!

			'''[https://events.ccc.de/camp/2015/Fahrplan/events/6842.html Hackerspace Design Patterns 2.0 Talk]''' at [https://events.ccc.de/camp/2015/wiki/Main_Page CCCamp2015]<br>
			'''When''': [https://events.ccc.de/camp/2015/Fahrplan/schedule/2.html Day 3], Saturday 15-August from 10:30am to 11:00am.<br>
			'''Where''': Project 2501 Tent (aka: Tent A)<br>
			[https://events.ccc.de/camp/2015/Fahrplan/events/6842.html https://events.ccc.de/camp/2015/Fahrplan/events/6842.html]

			Immediately following the [https://events.ccc.de/camp/2015/Fahrplan/events/6842.html Talk], I'll be leading a [https://events.ccc.de/camp/2015/wiki/Session:Hackerspace_Design_Patterns_2.0_Workshop Workshop / Discussion]. All are welcome! If you're just curious, or if you are interested talking about what has worked well (and what has not worked so well) at your space. Let's discuss and distill out new Patterns to add to the Hackerspace Design Patterns for all hackerspaces (forming, new, and old) to benefit from, far into the future.<br>
			'''[https://events.ccc.de/camp/2015/wiki/Session:Hackerspace_Design_Patterns_2.0_Workshop Hackerspace Design Patterns 2.0 Workshop]''' at
			[https://events.ccc.de/camp/2015/wiki/Main_Page CCCamp2015]<br>
			'''When''': [https://events.ccc.de/camp/2015/wiki/Village:Norton%27s_Obscure_Phoggy_Embassy#calendar Day 3], Saturday 15-August from 11:15am to 1:30pm.<br>
			'''Where''': [https://events.ccc.de/camp/2015/wiki/Village:Norton%27s_Obscure_Phoggy_Embassy Norton's Obscure Phoggy Embassy (NOPE) Village] (aka: the Noisebridge / Sudo Room Village<br>
			[https://events.ccc.de/camp/2015/wiki/Session:Hackerspace_Design_Patterns_2.0_Workshop https://events.ccc.de/camp/2015/wiki/Session:Hackerspace_Design_Patterns_2.0_Workshop]

	== tl;dr: ==		== tl;dr: ==

Maltman23 at 20:47, 9 August 2015

2015-08-09T20:47:02Z

← Older revision		Revision as of 13:47, 9 August 2015
Line 168:		Line 168:
	Ed Platt's new Patterns:<br>		Ed Platt's new Patterns:<br>
	https://elplatt.com/new-hackerspace-design-patterns		https://elplatt.com/new-hackerspace-design-patterns




			'''Reboot Pattern''':<br>
			'''Problem''':<br>
			When the space is brand new, everyone putting their energy into the space is creating something new, and are excited about it, and bond over it. After a few years, people come and go, and that feeling and energy of new-ness is gone -- and people who are newer to the space have the sense that the space has existed long before them, and will continue on its own. Also, the culture of the space changes over time. Some bad behaviors might start creeping in. And some people who have been putting lots and lots of their time and energy into the space tend to get burned out.<br>
			'''Solution''':<br>
			When you're OS isn't working so well, turn it off and on again! This often helps! So, have a Reboot for your space! Close the space for a month, and only let in people who are helping fix up the space. It's very bonding. It renews the feeling of new-ness, the feeling that each person has that they are creating the space that they are wanting to be a part of. And don't let in people who don't belong. After opening again, keep attracting people who belong (i.e., people who both benefit and contribute to the space -- and "contribute" can be in many forms: financial, cleaning, fixing, giving classes/workshops, learning cool things, sharing their positivity, making people at the space feel good, whatever people at the space feel is positive); and keep people out who are bad for the space. This collective behavior keeps the "cultural immune system" of the space healthy and strong. Have a mini-Reboot annually to regenerate this year after year.<br>
			'''An alternative to a Reboot''': is to have a Big Project that gets a majority (or, ideally, all) of the people at the space psyched to be helping bring to reality.

Holly: /* New Hackerspace Design Patterns */ added doublespace for tidiness

2015-07-19T22:02:57Z

New Hackerspace Design Patterns: added doublespace for tidiness

← Older revision		Revision as of 15:02, 19 July 2015
Line 37:		Line 37:

	'''Spreadsheet Pledges Funding Pattern:''' There is a large piece of equipment that several people want, but that your space cannot afford. Create a spreadsheet and have members enter pledges. When the total pledged amount exceeds the cost of the item, call in the pledges and purchase the item. It is important that pledgers understand that they will not be paid back -- they are paying to bring useful equipment into the space. Only pledge what this is worth to you.		'''Spreadsheet Pledges Funding Pattern:''' There is a large piece of equipment that several people want, but that your space cannot afford. Create a spreadsheet and have members enter pledges. When the total pledged amount exceeds the cost of the item, call in the pledges and purchase the item. It is important that pledgers understand that they will not be paid back -- they are paying to bring useful equipment into the space. Only pledge what this is worth to you.


	'''NonexistentKitchenPattern:''' Don’t have a kitchen at your space. Nothing turns a group of diverse individuals into competing cliques like using your hackerspace as shared living quarters. Have a fridge that is cleaned once a week, whether it needs it or not, whether you think food should be thrown away or not (it should).		'''NonexistentKitchenPattern:''' Don’t have a kitchen at your space. Nothing turns a group of diverse individuals into competing cliques like using your hackerspace as shared living quarters. Have a fridge that is cleaned once a week, whether it needs it or not, whether you think food should be thrown away or not (it should).

Holly: /* New Hackerspace Design Patterns */ added Spreadsheet Pledges Funding Pattern

2015-07-19T22:02:25Z

New Hackerspace Design Patterns: added Spreadsheet Pledges Funding Pattern

← Older revision		Revision as of 15:02, 19 July 2015
Line 35:		Line 35:
	Please feel free to add your new Patterns here:		Please feel free to add your new Patterns here:


			'''Spreadsheet Pledges Funding Pattern:''' There is a large piece of equipment that several people want, but that your space cannot afford. Create a spreadsheet and have members enter pledges. When the total pledged amount exceeds the cost of the item, call in the pledges and purchase the item. It is important that pledgers understand that they will not be paid back -- they are paying to bring useful equipment into the space. Only pledge what this is worth to you.

	'''NonexistentKitchenPattern:''' Don’t have a kitchen at your space. Nothing turns a group of diverse individuals into competing cliques like using your hackerspace as shared living quarters. Have a fridge that is cleaned once a week, whether it needs it or not, whether you think food should be thrown away or not (it should).		'''NonexistentKitchenPattern:''' Don’t have a kitchen at your space. Nothing turns a group of diverse individuals into competing cliques like using your hackerspace as shared living quarters. Have a fridge that is cleaned once a week, whether it needs it or not, whether you think food should be thrown away or not (it should).

Maltman23: /* New Hackerspace Design Patterns */

2015-07-14T01:21:51Z

New Hackerspace Design Patterns

← Older revision		Revision as of 18:21, 13 July 2015
Line 150:		Line 150:


	'''The Cabin Fever ~~pattern~~.'''<br>		'''The Cabin Fever Pattern.'''<br>
	'''Problem:''' A contentious disagreement breaks out between a large number of members. The topic varies, but the contention occurs on a semi-regular basis. For example, at the end of January/beginning of February (northern hemisphere). Or every 4 months.		'''Problem:''' A contentious disagreement breaks out between a large number of members. The topic varies, but the contention occurs on a semi-regular basis. For example, at the end of January/beginning of February (northern hemisphere). Or every 4 months.
	<br>		<br>
Line 161:		Line 161:
	to focus their energy on, instead of directing it at each other, and set the cycle length to complement the existing cycle of contention.		to focus their energy on, instead of directing it at each other, and set the cycle length to complement the existing cycle of contention.
	<br>		<br>


			Ed Platt's new Patterns:<br>
			https://elplatt.com/new-hackerspace-design-patterns

← Older revision		Revision as of 12:11, 6 September 2015
Line 46:		Line 46:

	Please feel free to add your new Patterns here:		Please feel free to add your new Patterns here:


	'''Physics Pattern'''		'''Physics Pattern'''
	([https://elplatt.com/new-hackerspace-design-patterns source])<br>		([https://elplatt.com/new-hackerspace-design-patterns source])<br>
	Problem: The group makes a lot of rules, but they are often ignored.		Problem: The group makes a lot of rules, but they are often ignored.<br>
	<br>
	'''Solution:''' Instead of creating rules, make it physically impossible to do the wrong thing, e.g. instead of saying "turn the lights out when you're done," put the lights on an automatic timer.		'''Solution:''' Instead of creating rules, make it physically impossible to do the wrong thing, e.g. instead of saying "turn the lights out when you're done," put the lights on an automatic timer.

Line 56:		Line 56:
	'''API Pattern'''		'''API Pattern'''
	([https://elplatt.com/new-hackerspace-design-patterns source])<br>		([https://elplatt.com/new-hackerspace-design-patterns source])<br>
	'''Problem:''' Hackers don't like unnecessary rules, and rules are often unenforceable.		'''Problem:''' Hackers don't like unnecessary rules, and rules are often unenforceable. Check out link about [http://theconversation.com/too-much-information-how-a-data-deluge-leaves-us-struggling-to-make-up-our-minds-44674 repercussions of Rule-making overload].<br>
	<br>
	'''Solution:''' Instead of rules, create procedures for solving problems. For example, create a "parking ticket" that members can place on abandoned projects in their way, and a standard way to notify the group about the ticket. Allow anyone to dispose of an abandoned project a certain amount of time after a parking ticket has been issued.		'''Solution:''' Instead of rules, create procedures for solving problems. For example, create a "parking ticket" that members can place on abandoned projects in their way, and a standard way to notify the group about the ticket. Allow anyone to dispose of an abandoned project a certain amount of time after a parking ticket has been issued.

Line 68:		Line 67:

	'''The Cabin Fever Pattern.'''<br>		'''The Cabin Fever Pattern.'''<br>
	'''Problem:''' A contentious disagreement breaks out between a large number of members. The topic varies, but the contention occurs on a semi-regular basis. For example, at the end of January/beginning of February (northern hemisphere). Or every 4 months.		'''Problem:''' A contentious disagreement breaks out between a large number of members. The topic varies, but the contention occurs on a semi-regular basis. For example, at the end of January/beginning of February (northern hemisphere). Or every 4 months.<br>
	<br>
	'''Solution:''' The topic may be valid, but it's important to examine the root of the -vigorousness- of the disagreement. Are external/seasonal influences affecting the members? Sometimes people start fights to blow off steam. If the time of year or weather is affecting the members, make sure that important decisions aren't being adversely influenced by seasonal concerns. If regular steam-blowing is needed, establish a regular series of group projects/common goals to give people something to focus their energy on, instead of directing it at each other, and set the cycle length to complement the existing cycle of contention.<br>		'''Solution:''' The topic may be valid, but it's important to examine the root of the -vigorousness- of the disagreement. Are external/seasonal influences affecting the members? Sometimes people start fights to blow off steam. If the time of year or weather is affecting the members, make sure that important decisions aren't being adversely influenced by seasonal concerns. If regular steam-blowing is needed, establish a regular series of group projects/common goals to give people something to focus their energy on, instead of directing it at each other, and set the cycle length to complement the existing cycle of contention.<br>

Line 82:		Line 80:
	'''Problem:''' Your hackerspace could use with some income $upplementing. A group that some of your members are a part of needs a space to work or hold meetings in.<br>		'''Problem:''' Your hackerspace could use with some income $upplementing. A group that some of your members are a part of needs a space to work or hold meetings in.<br>
	'''Solution:''' Pimp the space and offer at a (reasonable) price the usage of the space in off-times by groups. Be willing to be flexible for each group and work out a signed agreement -- contract or Notary Public letter to one another. A usage schedule may need to be established for popular tools. <br>		'''Solution:''' Pimp the space and offer at a (reasonable) price the usage of the space in off-times by groups. Be willing to be flexible for each group and work out a signed agreement -- contract or Notary Public letter to one another. A usage schedule may need to be established for popular tools. <br>

	'''Converse Anti-Pattern:''' Now there's stuff sitting in the middle of your shop that isn't really the responsibility of any of your members.<br>		'''Converse Anti-Pattern:''' Now there's stuff sitting in the middle of your shop that isn't really the responsibility of any of your members.<br>
	'''Solution:''' Have a solid mechanism in place for dealing with junk. [https://wiki.pumpingstationone.org/Tidy_Space_Policy PS:One's Tidyspace policy] is good at removing junk in a fair way.		'''Solution:''' Have a solid mechanism in place for dealing with junk. [https://wiki.pumpingstationone.org/Tidy_Space_Policy PS:One's Tidyspace policy] is good at removing junk in a fair way.
Line 90:		Line 89:
	'''Solution:''' Run a fundrai$ing campaign, NPR style. Tote-bags and coupon books 'n all.		'''Solution:''' Run a fundrai$ing campaign, NPR style. Tote-bags and coupon books 'n all.

	'''Converse Anti-Pattern:''' You run ~~them~~ and can't make up on your printed totes, or you're running them every month.		'''Converse Anti-Pattern:''' You run the campaign$ and can't make up on your printed totes, or you're running them every month.


Line 165:		Line 164:
	'''Pot-Lock Pattern'''		'''Pot-Lock Pattern'''
	([https://elplatt.com/new-hackerspace-design-patterns source])<br>		([https://elplatt.com/new-hackerspace-design-patterns source])<br>
	'''Problem:''' Maintenance and cleaning is boring and no one wants to do it.		'''Problem:''' Maintenance and cleaning is boring and no one wants to do it.<br>
	'''Solution:''' Hold a combination pot luck and lock-in. Everyone works on maintenance and cleaning and takes a break to share home-cooked meals with each other. No one leaves until time is up.		'''Solution:''' Hold a combination pot luck and lock-in. Everyone works on maintenance and cleaning and takes a break to share home-cooked meals with each other. No one leaves until time is up.

Line 196:		Line 195:
	'''Problem''':<br>		'''Problem''':<br>
	When the space is brand new, everyone putting their energy into the space is creating something new, and are excited about it, and bond over it. After a few years, people come and go, and that feeling and energy of new-ness is gone -- and people who are newer to the space have the sense that the space has existed long before them, and will continue on its own. Also, the culture of the space changes over time. Some bad behaviors might start creeping in. And some people who have been putting lots and lots of their time and energy into the space tend to get burned out.<br>		When the space is brand new, everyone putting their energy into the space is creating something new, and are excited about it, and bond over it. After a few years, people come and go, and that feeling and energy of new-ness is gone -- and people who are newer to the space have the sense that the space has existed long before them, and will continue on its own. Also, the culture of the space changes over time. Some bad behaviors might start creeping in. And some people who have been putting lots and lots of their time and energy into the space tend to get burned out.<br>
	'''Solution'''~~:<br>~~		'''Solution:''' When you're OS isn't working so well, turn it off and on again! This often helps! So, have a Reboot for your space! Close the space for a month, and only let in people who are helping fix up the space. It's very bonding. It renews the feeling of new-ness, the feeling that each person has that they are creating the space that they are wanting to be a part of. And don't let in people who don't belong. After opening again, keep attracting people who belong (i.e., people who both benefit and contribute to the space -- and "contribute" can be in many forms: financial, cleaning, fixing, giving classes/workshops, learning cool things, sharing their positivity, making people at the space feel good, whatever people at the space feel is positive); and keep people out who are bad for the space. This collective behavior keeps the "cultural immune system" of the space healthy and strong. Have a mini-Reboot annually to regenerate this year after year.<br>
	When you're OS isn't working so well, turn it off and on again! This often helps! So, have a Reboot for your space! Close the space for a month, and only let in people who are helping fix up the space. It's very bonding. It renews the feeling of new-ness, the feeling that each person has that they are creating the space that they are wanting to be a part of. And don't let in people who don't belong. After opening again, keep attracting people who belong (i.e., people who both benefit and contribute to the space -- and "contribute" can be in many forms: financial, cleaning, fixing, giving classes/workshops, learning cool things, sharing their positivity, making people at the space feel good, whatever people at the space feel is positive); and keep people out who are bad for the space. This collective behavior keeps the "cultural immune system" of the space healthy and strong. Have a mini-Reboot annually to regenerate this year after year.<br>
	'''An alternative to a Reboot''': is to have a Big Project that gets a majority (or, ideally, all) of the people at the space psyched to be helping bring to reality.<br>		'''An alternative to a Reboot''': is to have a Big Project that gets a majority (or, ideally, all) of the people at the space psyched to be helping bring to reality.<br>