adinfinitum
/
hackerspace-blueprint
mirror of https://codeberg.org/tqt/hackerspace-blueprint.git
2
0
Fork 0
Code Issues Releases Wiki Activity

Merge pull request #29 from galgalesh/master 

Touch-up of guidelines
pull/33/head untagged-b0f0f92b2d394606f5ac
Merlijn Sebrechts 2019-04-14 21:27:52 +02:00 committed by GitHub
parent bb0a85155d dc0440d65f
commit 8e303daf91
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 48 additions and 43 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

91
6-guidelines.md
View File

@ -1,100 +1,105 @@
# 6. Guidelines
**Note:** For now the goal of this page is to collect ideas that YOU think should be part of the guidelines for the space.
The hackerspace is a shared resource created *by* the community, *for* the community. It only exists because people think it's valuable enough to nourish it. Without the community, the hackerspace would simply not exist, so it is very important that we as a community collaborate and keep it fun for everyone.
Basically we've come the observation that "*use common sense*" and "*be excellent*" don't always suffice as a *code of conduct*. This is because different people have different realities, values and morals. We think this diversity is a good thing. However in a communal context where these realities clash with each other it creates friction and conflict.
We want you to be a part of it, but you need to do three things.
So the need for guidelines arose, this is an attempt to define these rules.
* Use common sense,
* be excellent to others,
* and don't be an asshole.
These guidelines are a practical emanation the two basic rules:
People have different realities, values and morals, resulting in different ideas for how to do these three things. Different realities have clashed in the past, which created friction and conflict. This was very dangerous the hackerspace dies when the community falls apart.
* Use common sense
* Be excellent to each other
This document helps solve the issue of different realities by giving you a set of guidelines to help you get an idea of what it means to be a valuable part of this community. These guidelines describe what the hackerspace thinks it means to use common sense, be excellent to others, and not be an asshole.
Members are encouraged to apply the two basic rules to the best of their abilities. *Be excellent to each other* implies treating others the way you want to be treated, which is considered by almost all moral systems as [the golden rule](http://en.wikipedia.org/wiki/Golden_Rule).
First and foremost, [the golden rule](http://en.wikipedia.org/wiki/Golden_Rule): treat others the way you want to be treated.
## 6.1 Projects
## Loopholes
There is a clear distinction between Personal vs Space projects.
The goal of the do-ocracy and these guidelines is to create an awesome community. The do-ocracy gives you a lot of freedom, but you need to use it wisely. People who try to exploit loopholes in this system to do things that damage the community cannot handle the freedom of a do-ocracy and will be pushed out very quickly. Do not read these guidelines like a lawyer, but read it like a cookbook. It doesn't matter if you add a bit more sugar, as long as your goal is to make the cake better.
### Personal
## Projects
* You have full control over what happens to the project.
* The property of the project is considered personal property and 6.2.1 applies to it.
There is a clear distinction between "personal" and "space" projects. Keep this in mind so you know what to expect and what people can expect of you.
### Personal projects
* You have full control over how to do the project.
* The project stuff/material is considered your personal property.
* You decide what happens to the end-result of the project.
### Space
### Space projects
* Decisions go through the [Flow](flow.md).
* The property of the project is considered space property and 6.2.2 applies to it.
* The Group decides what happens to the end result of the project.
* The do-ocracy decides how to do the project.
* The project stuff/material is considered space property.
* The do-ocracy decides what happens to the end result of the project.
## 6.2 Property and tools
## Property and tools
### 6.2.1 Personal Property
### Personal property
Only members are allowed to have personal property in the space. You get one box where you can leave your stuff. If you need more space for your projects, bring it up in a group meeting.
* Only members are allowed to have personal property in the space. You get one box (the membership box) where you can leave your stuff. If you need more space for your projects, bring it up in a group meeting.
* If you break personal property of another member, you have to fully reimburse the member's losses.
* All personal property that is not in a members box has to be labeled (including tools and machines).
If you break personal property of another member, you have to fully reimburse the member's losses.
### Space property
All personal property that is not in a members box has to be labeled (including tools and machines).
### 6.2.2 Space Property
#### 6.2.2.1 Using space property
#### Using space property
* When you are using tools/infrastructure from the space, you are effectively borrowing that item from the community.
* Return borrowed items promptly in the same or better condition than when borrowed.
* If you borrow it, return it. If you damage or lose it: follow 6.2.2.2.
* Return borrowed items as soon as possible in the same or better condition than when borrowed.
* So when using something, clean it afterwards and put it back in it's place.
* If you are not trained to use tool X, don't use tool X but ask an expert to teach you first.
* If you are not trained to use tool X, don't use tool X but ask an expert to teach you first.
* If you use one of the public workstations, please shut it off when you are done.
* if you use the printer, please deposit some cash to pay for consumables
#### 6.2.2.2 Damaging or losing space property
#### Damaging or losing space property
If you damage or lose space property, you have to notice the Group Of Members immediately via the mailing-list. In the mail, you say what happened and if/how you will fix it. If the Group Of Members do not agree to this, they will have to put it forward on the next meeting.
If you damage or lose space property, you have to notice the community immediately in the Changelog or the Main channel on mattermost. Explain what happened and if/how you will fix it.
#### 6.2.2.3 Taking space property out of the space
#### Taking space property out of the space
Only members are allowed to take space property out of the space. If you take space property out of the space, you have to notify the Group Of Members immediately via the mailing-list. In the mail, you have to include when you'll return it. If any other member disagrees, you put it back.
Only members are allowed to take space property out of the space. If you take space property out of the space, you have to notify the community immediately, for example in the "changelog" or "main" channels on Mattermost. If a somebody disagrees with you taking it out of the space, make that person happy or put it back.
## 6.3 Space maintenance
## Space maintenance
### 6.3.1 Cleaning
### Cleaning
* Keep the dishes clean: when using the dishes, clean your dishes and any dishes that are standing there. When you see other people using the dishes, and they forget cleaning them, give them a gentle reminder.
* Keep the desks clean, feel free to use the desk space for your stuff, you can leave your stuff on the desk when you just 'pop out for some food', but leave a note stating when you'll be back. _Do Not_ leave it there until the next morning.
* Remove empty packaging, from food or beverages.
* Every once in a while there will be a cleaning day in the space, as a good upstanding member of the community you should attend one of these at least once quarterly. Many hands make light work.
### 6.3.2 Exit space
### Exit space
* If you are the last person to leave the space, it's your responsibility to clean up. If you see people leaving, please alert them if they have left their trash in the space.
* Switch off all power consuming things
* Close the roof
* Read and follow the checklist at the door.
### 6.3.3 Throwing things away
### Throwing things away
* Some things that seem a useless waste of space to you, might be very valuable to other people. When you throw things away, it has to be decided upon by the group, via the decision model of the group.
* Some things that seem a useless waste of space to you might be very valuable to other people. When you throw things away, you have to let the community know and give them enough time to object.
## 6.4 Social behavior
## Social behavior
* When in doubt if you're doing the right thing, you probably aren't.
* Just try not to be *that* guy.
* Share your love and passion, but respect people's boundaries.
* Don't hack people without their explicit consent.
### 6.4.1 Noise
If you have any issues with other people's behavior, please notify the board. The board will help if you want, but even if you don't; still notify them so they know of the problem.
### Noise
People are trying to concentrate in here so:
* Mind your voice, volume. If you are talking to someone on the other side of the space, everyone in between can hear you; move closer.
* We know you like X music, but use headphones or keep the volume low.
* Don't be afraid to ask if you are not intruding/disturbing.
* If need to make a lot of noise, ask if you are not intruding/disturbing.
* Some moments are 'louder' than others, so it's not always easy to follow. Sometimes library/office-rules apply, sometimes workshop-rules and sometimes bar-rules. When in doubt, check with the other members.
### 6.4.2 Network/security
### Network/security
* Just leave other people's stuff alone, don't post "*funny*" social network status updates on unattended logged in computers.
* Don't sniff the network / no ssl-strip / rogue dhcp / random script-kiddo stuff. It been done before, it's lame.
* Don't sniff the network, no ssl-strip / rogue dhcp / random script-kiddo stuff. It been done before. It's lame.
* Don't congest the network with (legal) torrenting, just behave nicely, so we don't have to write an AUP.