attempt to document existing Noisebridge community guidelines #27

Open
wants to merge 1 commit into
from

Conversation

Projects
None yet
2 participants

No description provided.

+Community Guidelines
+====================
+
+Noisebridge supports fair usage. We agree as participants of Noisebridge to be excellent.
@flamsmark

flamsmark Mar 25, 2014

Contributor

I'm not clear what “fair usage” means in this context? What were you trying to communicate?

+
+Noisebridge shares a building with other tenants. The following guidelines outline best practices for sharing space with our neighbors.
+
+* Do not service the elevator. Doing so conflicts with an agreement that we have with our landlord. Elevator issues should be reported to building management via the secretary@noisebridge.net alias.
@flamsmark

flamsmark Mar 25, 2014

Contributor

Suggestion:

We have promised the landlord that we will not attempt to service or perform maintenance on the elevator. Instead, elevator issues should be reported secretary@noisebridge.net, and will be taken up with building management.

+
+* Do not service the elevator. Doing so conflicts with an agreement that we have with our landlord. Elevator issues should be reported to building management via the secretary@noisebridge.net alias.
+
+* The roof is not apart of Noisebridge.
@flamsmark

flamsmark Mar 25, 2014

Contributor

Typo.

+
+* The fire escape is to be used only in case of an emergency.
+
+* Going anywhere noted above, except in narrow circumstances that you almost certainly aren't covered by, jeopardizes our continued tenancy.
@flamsmark

flamsmark Mar 25, 2014

Contributor

Suggestion: remove the bullet point on this line, and change to:

There are only very specific circumstances under which we may use any of these places. None of these circumstances are likely to come up in regular use. Entering these spaces under any other circumstances jeopardizes our continued tenancy.

+Personal Use
+------------
+
+We agree that Noisebridge is an infrastructure provider for technical-creative projects. We teach, we learn, we share. The following guidelines outline best practices for using and maintaining our shared hackerspace.
@flamsmark

flamsmark Mar 25, 2014

Contributor

Suggested alternate line:

Noisebridge is an infrastructure provider for technical-creative projects. In order to continue serving that function, we must maintain this infrastructure.

+
+We agree that Noisebridge is an infrastructure provider for technical-creative projects. We teach, we learn, we share. The following guidelines outline best practices for using and maintaining our shared hackerspace.
+
+* Noisebridge is your hackerspace, not your home. Overuse/abuse is an anti-pattern within the community.
@flamsmark

flamsmark Mar 25, 2014

Contributor

I've really enjoyed s/home/hostel. Here's an alternate line:

Noisebridge is a hackerspace not a hostel. Using Noisebridge like a place to live impedes our mission, and makes it less useful as an infrastructure provider for others.

+
+* Noisebridge is your hackerspace, not your home. Overuse/abuse is an anti-pattern within the community.
+
+* Noisebridge has designated space for project storage. Failure to store and label your project in a designated space may result in unexpected hacks. If you are unaware of what spaces are designated for project storage, then please ask someone or consult the wiki.
@flamsmark

flamsmark Mar 25, 2014

Contributor

Suggestion:

Noisebridge has designated places to store projects. Storing projects in common areas is anti-social. If your project is stored in a common area, it may be re-purposed or dicarded. If you do not know where to store your project, ask: in person, by mailing-list, or perusing the wiki.

+
+* Noisebridge has designated space for project storage. Failure to store and label your project in a designated space may result in unexpected hacks. If you are unaware of what spaces are designated for project storage, then please ask someone or consult the wiki.
+
+* Pull your own weight. We don't have housekeeping service, so clean up after yourself and put things away when you're done. In fact, you're going to get a lot of good karma by tidying up twice the amount of space you use on a regular basis. Washing dishes, answering the door/phone, taking out the garbage, giving tours are great. Each one, teach one.
@flamsmark

flamsmark Mar 25, 2014

Contributor

This seems to have a lot of wishy-washy sort of language in it. Suggestion:

We are all responsible for keeping Noisebridge clean and tidy. You are responsible for cleaning up after yourself. Leaving your mess for others is antisocial.

+
+* Pull your own weight. We don't have housekeeping service, so clean up after yourself and put things away when you're done. In fact, you're going to get a lot of good karma by tidying up twice the amount of space you use on a regular basis. Washing dishes, answering the door/phone, taking out the garbage, giving tours are great. Each one, teach one.
+
+* Noisebridge operates as a Do-ocracy; if you want something done, do it. Most of the time many of us just don't want to be troubled with spending a week figuring out if everyone is ok with a small or mundane thing. The biggest challenge in a do-acracy is ascertaining (and taking) responsibility. If someone undoes a do-acratic change, then more discussion is encouraged before any further changes are made.
@flamsmark

flamsmark Mar 25, 2014

Contributor

I'm not sure about this line. I'd definitely like to talk about do-ocracy and and the one-revert principle, but I'm not sure that this is the right place for it. I think the easiest solution would be to drop it from this document, and open an issue. We could add it in a different document or a subsequent commit.

In particular, I think that do-ocracy and one-revert are principles would really benefit from @kevinjos' approach of a very short, pithy delivery in the bureaucracy, and a longer discussion & explanation on the wiki.

@@ -0,0 +1,37 @@
+[This document is a hack at best. As such, it shall expire three months after initial consensus. If Noisebridge deems said policy a success after three months, Noisebridge may extend said policy or amendments thereof.]
@flamsmark

flamsmark Mar 25, 2014

Contributor

I'm fine with this sentiment, but I think it could be expressed better. How about putting a specific expiry date in the header? Then if we make a change, we can likewise extend the expiry date. I'm concerned that a relative time might have ambiguous meaning.

Contributor

flamsmark commented Mar 25, 2014

Thanks @kevinjos, this has some tight wording. I'd prefer for bullet-points to be on sequential lines to conform with the markdown/HTML semantics, but that's just formatting.

There are some issues that I covered in my proposal which I think are missing from yours:

  • Asking people to leave
  • Specific discussion of sleeping at Noisebridge
  • Leaving food out (outside of a general notion of mess)
  • Smoking near the street-level entrance

Did you drop those things because you want to cover them in subsequent revisions, because you don't think we really agree on them, or just though the back-and-forth of drafting?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment