How we keep Noisebridge safe - Revision history

Lxpk at 22:25, 22 December 2021

2021-12-22T22:25:25Z

← Older revision		Revision as of 15:25, 22 December 2021
Line 1:		Line 1:
			{{gettingalong}}

	= How we keep a healthy, safe Noisebridge community =		= How we keep a healthy, safe Noisebridge community =

Nthmost: /* Red Flags */ Added "Yellow Flags" and removed shit like "only uses the terminals and couches". Let's take the Neo-McCarthyism down a notch, eh?

2018-10-17T21:59:56Z

Red Flags: Added "Yellow Flags" and removed shit like "only uses the terminals and couches". Let's take the Neo-McCarthyism down a notch, eh?

← Older revision		Revision as of 14:59, 17 October 2018
Line 90:		Line 90:
	* Mediation by demand - We only do it if it's likely to succeed and everyone involved wants to do it.		* Mediation by demand - We only do it if it's likely to succeed and everyone involved wants to do it.

	== Red Flags ==		== Red and Yellow Flags ==

	Red flags are small signs that someone might be doing or going to try and do something that hurts the Noisebridge community. Seeing one warning sign is a reason for concern, but not a problem in and of itself. We talk about red flags when we see them to figure out if there's a larger pattern of behavior that no one person is seeing. Ie, someone found someone asleep on the couch, but didn't think too much of it. They mention it, and find out that three other people have woken the same person up, and a fourth person saw them stashing clothes in the wood shop. Now there's a much different story, which makes it pretty clear that this person doesn't belong at Noisebridge.		Red and Yellow flags are small signs that someone might be doing or going to try and do something that hurts the Noisebridge community. Seeing one warning sign is a reason for concern, but not a problem in and of itself. We talk about red flags when we see them to figure out if there's a larger pattern of behavior that no one person is seeing. Ie, someone found someone asleep on the couch, but didn't think too much of it. They mention it, and find out that three other people have woken the same person up, and a fourth person saw them stashing clothes in the wood shop. Now there's a much different story, which makes it pretty clear that this person doesn't belong at Noisebridge.

	Red flags include, but are not limited to:		'''BEWARE OVERFITTING'''

			Some people may just be having a bad day or just not really know how Noisebridge works yet. '''Lists of behaviors should not be used as excuses not to be excellent to someone'''. Even someone who seems to mean to do Noisebridge harm should still be treated a whole person.

			'''''Red flags''''' include, but are not limited to:
	* Name dropping to invoke privilege. Particularly if that person is [[User:Maltman23\|Mitch]], "the owner", or "the people in charge".		* Name dropping to invoke privilege. Particularly if that person is [[User:Maltman23\|Mitch]], "the owner", or "the people in charge".
	* Bolting past the person opening the door for them and heading for the back of the space		* Bolting past the person opening the door for them and heading for the back of the space
	* ~~Immediately heading~~ to ~~a hidey-hole - a dark~~, ~~unpopulated corner~~ of the ~~space~~		* Lying... (not lying like "my mom's calling me" when they need an excuse to tap out, but lying like "I'm one of the NB board members" when they are not.)
	* Immediately rummaging through things after coming in. ~~Either in the hack shelves, or elsewhere in the space.~~
	* Demanding help/attention when first coming in to the space (ie, fix my laptop/phone)
	* Lying
	* Giving people a hard time when someone questions their behavior or asks them to leave.		* Giving people a hard time when someone questions their behavior or asks them to leave.
	* Only taking from the space - ~~this mean~~ direct theft of tools/hack shelf contents/laptops/materials/etc, or ~~simply taking energy out of the space, by ie, sleeping,~~ constantly ~~complaining, etc~~.		* Only taking from the space - e.g. direct theft of tools/hack shelf contents/laptops/materials/etc or constantly bothering people for no productive purpose.
	* Only giving to the space - this is also known as the Savior/Martyr pattern (see below).		* Only giving to the space - this is also known as the Savior/Martyr pattern (see below).
	* Only using the Noisebridge kitchen/internet/couches
	* Ringing the doorbell late at night
	* Storing personal items/clothing at Noisebridge, particularly in out-of-sight places		* Storing personal items/clothing at Noisebridge, particularly in out-of-sight places
			* Repeatedly sleeps in the space (treats Noisebridge as a squat)
			* Shows up obnoxiously drunk/high.
			* Invokes anarchism as a reason why they can do whatever they want and don't have to listen to anyone else.


			'''''Yellow flags''''': could mean the person is having a bad day or doesn't really understand Noisebridge yet, so take this list with a grain of salt and use kindness first! Never use this list as reasons to kick people out in and of themselves.

			* Immediately heads to a hidey-hole - a dark, unpopulated corner of the space
			* Immediately rummages through things right after coming in (hack shelves, other people's projects, etc)
			* Immediately asking about the 24 hour access policy.
			* Immediately tells you "I've been coming here for years."
			* Doesn't seem to respect "Do Not Hack" tags or boxes labeled as people's projects.
			* Demanding help/attention when first coming in to the space (ie, fix my laptop/phone)
			* Reacts poorly when people introduce themselves or want to chat.
			* Napping in the space.
			* Repeatedly ringing the doorbell late at night or early in the morning (when Noisebridge is not typically open).
			* Showing a sense of entitlement - an attitude that Noisebridge exists solely for their benefit
	* Not making sense - racing thoughts, paranoia, etc		* Not making sense - racing thoughts, paranoia, etc
	* ~~Immediately asking~~ about the ~~24 hour access policy~~		* Argues about how Noisebridge should be when brand new to the community
	* Showing a sense of entitlement - an attitude that Noisebridge exists solely for their benefit
	* Gets argumentative quickly vs discussing when things don't go their way		* Gets argumentative quickly vs discussing when things don't go their way
	* Argues about how Noisebridge should be when brand new to the community
	* Sleeps in the space
	* Shows up drunk/high
	* Immediately tells you "I've been coming here for years."
	* Invokes anarchism as a reason why they can do whatever they want and don't have to listen to anyone else.
	* Reacts poorly when people introduce themselves or want to chat.

	The Savior/Martyr pattern:		The Savior/Martyr pattern:

Nthmost: /* Red Flags */ rewording some Savior/Martyr pattern aspects for clarity

2018-10-17T21:43:33Z

Red Flags: rewording some Savior/Martyr pattern aspects for clarity

← Older revision		Revision as of 14:43, 17 October 2018
Line 120:		Line 120:
	The Savior/Martyr pattern:		The Savior/Martyr pattern:
	* Shows up at Noisebridge incredibly enthusiastic to "Make Noisebridge Better!"		* Shows up at Noisebridge incredibly enthusiastic to "Make Noisebridge Better!"
	* ~~Starts jumping into~~ working on the Noisebridge infrastructure ~~in lots of ways~~		* Almost immediately starts working on the Noisebridge infrastructure, often making unilateral decisions about major things (e.g. setting up new spaces).
	* Makes lots of suggestions for what Noisebridge is doing wrong and how to improve it without getting to know the community first		* Makes lots of suggestions for what Noisebridge is doing wrong and how to improve it without getting to know the community first
	* Doesn't explore or do any of their own projects		* Doesn't explore or do any of their own projects
Line 126:		Line 126:
	* Develops a sense of propriety at Noisebridge - they are SAVING Noisebridge by making a huge personal sacrifice		* Develops a sense of propriety at Noisebridge - they are SAVING Noisebridge by making a huge personal sacrifice
	* Gets frustrated when they aren't in complete control, or resents that people don't recognize them enough for their sacrifice		* Gets frustrated when they aren't in complete control, or resents that people don't recognize them enough for their sacrifice
	* Ends up rubbing people the wrong way
	* Doesn't change their behavior when people give them feedback		* Doesn't change their behavior when people give them feedback
	* Eventually gets unwelcomed or banned in a spectacular explosion		* Eventually gets unwelcomed or banned in a spectacular explosion
	Often people that exhibit this pattern start out as very good contributors to the space, and are often well liked within the community. ~~But it has always led~~ to ~~badness, often extreme, when~~ people ~~only contribute to~~, ~~and don~~'t ~~benefit from~~ the ~~community~~.
			Often people that exhibit this pattern start out as very good contributors to the space, and are often well liked within the community.

			Left unchecked, the Savior/Martyr individual inevitably creates factions within the space just by virtue of being seen to be attached to the outcomes of an impossibly large array of things that happen at Noisebridge. These factions inevitably get into unresolvable conflicts until the Savior/Martyr person is either asked to take a break (note this is not the same as "Asked to Leave") or they wind up banned. We hate banning people, but if someone isn't willing to listen to feedback and update their behavior, that someone usually ends up on the wrong side of the 86 list.

	Shit that might feel unfair:		Shit that might feel unfair:
	* Some ~~people~~'~~s opinion carries~~ more weight than others.		* Some individuals' opinions carry more weight than others.
	* Not all conversations, particularly about safe space issues, happen in public forums. Sometimes there will be conversations you're not ~~privvy~~ to.		* Not all conversations, particularly about safe space issues, happen in public forums. Sometimes there will be conversations you're not privy to.
	* Not everyone is guaranteed the same level of due process.		* Not everyone is guaranteed the same level of due process.
	* Not everyone who fucks up in the space will get the same level of attention.		* Not everyone who fucks up in the space will get the same level of attention.

188.166.88.101: /* How we keep a healthy, safe Noisebridge community */

2017-05-04T02:53:06Z

How we keep a healthy, safe Noisebridge community

← Older revision		Revision as of 19:53, 3 May 2017
Line 1:		Line 1:
	= How we keep a healthy, safe Noisebridge community =		= How we keep a healthy, safe Noisebridge community =

	:''NOTE: This is ~~an ongoing draft~~ a ~~few of us have been working on on and off for a while in an attempt to try and~~ communicate to newer (and older) people in our community how our no-process tools and patterns work around dealing with issues in the space, without actually defining a formal process. ~~Comments and suggestions welcome~~.''		:''NOTE: This is a living document that attempts communicate to newer (and older) people in our community how our no-process tools and patterns work around dealing with issues in the space, without actually defining a formal process. Those that have been around a while should feel free to update it, but please try to keep it as a description of what we actually do in practice, versus what we aspire to do, to avoid unnecessary codification.''

	Noisebridge has learned a lot in the past few years about how to keep our community healthy and safe. We've tried a lot of things that didn't work, and in the process, found a few that did. This is an attempt to catalog some of the things we've learned, both to help pass on our learnings to newer community members as well as to share with other communities that may benefit from our past.		Noisebridge has learned a lot in the past few years about how to keep our community healthy and safe. We've tried a lot of things that didn't work, and in the process, found a few that did. This is an attempt to catalog some of the things we've learned, both to help pass on our learnings to newer community members as well as to share with other communities that may benefit from our past.

47.91.143.196: /* How we keep a healthy, safe Noisebridge community */ Removed my name as the author, since lots of other people have contributed at this point.

2017-03-13T04:32:49Z

How we keep a healthy, safe Noisebridge community: Removed my name as the author, since lots of other people have contributed at this point.

← Older revision		Revision as of 21:32, 12 March 2017
Line 1:		Line 1:
	= How we keep a healthy, safe Noisebridge community =		= How we keep a healthy, safe Noisebridge community =

	:''NOTE: This is an ongoing draft of ~~something I ([[User:Scotty\|Scotty]])~~ have been working on on and off for a while in an attempt to try and communicate to newer (and older) people in our community how our no-process tools and patterns work around dealing with issues in the space, without actually defining a formal process. Comments and suggestions welcome.''		:''NOTE: This is an ongoing draft a few of us have been working on on and off for a while in an attempt to try and communicate to newer (and older) people in our community how our no-process tools and patterns work around dealing with issues in the space, without actually defining a formal process. Comments and suggestions welcome.''

	Noisebridge has learned a lot in the past few years about how to keep our community healthy and safe. We've tried a lot of things that didn't work, and in the process, found a few that did. This is an attempt to catalog some of the things we've learned, both to help pass on our learnings to newer community members as well as to share with other communities that may benefit from our past.		Noisebridge has learned a lot in the past few years about how to keep our community healthy and safe. We've tried a lot of things that didn't work, and in the process, found a few that did. This is an attempt to catalog some of the things we've learned, both to help pass on our learnings to newer community members as well as to share with other communities that may benefit from our past.

Maltman23: /* Red Flags */

2017-03-12T18:25:07Z

Red Flags

← Older revision		Revision as of 11:25, 12 March 2017
Line 95:		Line 95:

	Red flags include, but are not limited to:		Red flags include, but are not limited to:
	* Name dropping to invoke privilege. Particularly if that person is [[User:~~Mitch~~\|Mitch]], "the owner", or "the people in charge".		* Name dropping to invoke privilege. Particularly if that person is [[User:Maltman23\|Mitch]], "the owner", or "the people in charge".
	* Bolting past the person opening the door for them and heading for the back of the space		* Bolting past the person opening the door for them and heading for the back of the space
	* Immediately heading to a hidey-hole - a dark, unpopulated corner of the space		* Immediately heading to a hidey-hole - a dark, unpopulated corner of the space

Maltman23: /* Red Flags */

2017-03-12T18:24:36Z

Red Flags

← Older revision		Revision as of 11:24, 12 March 2017
Line 95:		Line 95:

	Red flags include, but are not limited to:		Red flags include, but are not limited to:
	* Name dropping to invoke privilege. Particularly if that person is Mitch, "the owner", or "the people in charge".		* Name dropping to invoke privilege. Particularly if that person is [[User:Mitch\|Mitch]], "the owner", or "the people in charge".
	* Bolting past the person opening the door for them and heading for the back of the space		* Bolting past the person opening the door for them and heading for the back of the space
	* Immediately heading to a hidey-hole - a dark, unpopulated corner of the space		* Immediately heading to a hidey-hole - a dark, unpopulated corner of the space

Maltman23: /* How we keep a healthy, safe Noisebridge community */

2017-03-12T18:23:22Z

How we keep a healthy, safe Noisebridge community

← Older revision		Revision as of 11:23, 12 March 2017
Line 1:		Line 1:
	= How we keep a healthy, safe Noisebridge community =		= How we keep a healthy, safe Noisebridge community =

	:''NOTE: This is a draft of something I ([[User:Scotty\|Scotty]]) have been working on on and off for a while in an attempt to try and communicate to newer (and older) people in our community how our no-process tools and patterns work around dealing with issues in the space, without actually defining a formal process. Comments and suggestions welcome.''		:''NOTE: This is an ongoing draft of something I ([[User:Scotty\|Scotty]]) have been working on on and off for a while in an attempt to try and communicate to newer (and older) people in our community how our no-process tools and patterns work around dealing with issues in the space, without actually defining a formal process. Comments and suggestions welcome.''

	Noisebridge has learned a lot in the past few years about how to keep our community healthy and safe. We've tried a lot of things that didn't work, and in the process, found a few that did. This is an attempt to catalog some of the things we've learned, both to help pass on our learnings to newer community members as well as to share with other communities that may benefit from our past.		Noisebridge has learned a lot in the past few years about how to keep our community healthy and safe. We've tried a lot of things that didn't work, and in the process, found a few that did. This is an attempt to catalog some of the things we've learned, both to help pass on our learnings to newer community members as well as to share with other communities that may benefit from our past.

Maltman23: /* How we keep a healthy, safe Noisebridge community */

2017-03-12T18:20:37Z

How we keep a healthy, safe Noisebridge community

← Older revision		Revision as of 11:20, 12 March 2017
Line 1:		Line 1:
	= How we keep a healthy, safe Noisebridge community =		= How we keep a healthy, safe Noisebridge community =

	:''NOTE: This is a ~~rough~~ draft of something I ([[User:Scotty\|Scotty]]) have been working on on and off for a while in an attempt to try and communicate to newer people in our community how our no-process tools and patterns work around dealing with issues in the space, without actually defining a formal process. Comments and suggestions welcome.''		:''NOTE: This is a draft of something I ([[User:Scotty\|Scotty]]) have been working on on and off for a while in an attempt to try and communicate to newer (and older) people in our community how our no-process tools and patterns work around dealing with issues in the space, without actually defining a formal process. Comments and suggestions welcome.''

	Noisebridge has learned a lot in the past few years about how to keep our community healthy and safe. We've tried a lot of things that didn't work, and in the process, found a few that did. This is an attempt to catalog some of the things we've learned, both to help pass on our learnings to newer community members as well as to share with other communities that may benefit from our past.		Noisebridge has learned a lot in the past few years about how to keep our community healthy and safe. We've tried a lot of things that didn't work, and in the process, found a few that did. This is an attempt to catalog some of the things we've learned, both to help pass on our learnings to newer community members as well as to share with other communities that may benefit from our past.

Maltman23: /* How we keep a healthy, safe Noisebridge community */

2017-03-12T18:19:52Z

How we keep a healthy, safe Noisebridge community

← Older revision		Revision as of 11:19, 12 March 2017
Line 1:		Line 1:
	= How we keep a healthy, safe Noisebridge community =		= How we keep a healthy, safe Noisebridge community =

	:''NOTE: This is a rough draft of something I ([[User:Scotty]]) have been working on on and off for a while in an attempt to try and communicate to newer people in our community how our no-process tools and patterns work around dealing with issues in the space, without actually defining a formal process. Comments and suggestions welcome.''		:''NOTE: This is a rough draft of something I ([[User:Scotty\|Scotty]]) have been working on on and off for a while in an attempt to try and communicate to newer people in our community how our no-process tools and patterns work around dealing with issues in the space, without actually defining a formal process. Comments and suggestions welcome.''

	Noisebridge has learned a lot in the past few years about how to keep our community healthy and safe. We've tried a lot of things that didn't work, and in the process, found a few that did. This is an attempt to catalog some of the things we've learned, both to help pass on our learnings to newer community members as well as to share with other communities that may benefit from our past.		Noisebridge has learned a lot in the past few years about how to keep our community healthy and safe. We've tried a lot of things that didn't work, and in the process, found a few that did. This is an attempt to catalog some of the things we've learned, both to help pass on our learnings to newer community members as well as to share with other communities that may benefit from our past.