Added statutes and more cleanup
parent
c5126922de
commit
e11062cd82
|
@ -1,6 +1,6 @@
|
|||
# 3. Meetings
|
||||
|
||||
## The desicion making model
|
||||
## The decision making model
|
||||
|
||||
Below outlines the decision making model to be used during meetings.
|
||||
|
||||
|
@ -87,3 +87,26 @@ As you can see in this example, a less-extreme proposal that, on first sight, ha
|
|||
| TOTAL | **32** | 18 |
|
||||
|
||||
However, extreme ideas will not be able to "win". With extreme ideas, the outcome of this model will be the same as with a +50% majority.
|
||||
|
||||
## General Assembly and Statutes
|
||||
|
||||
A general assembly is different from a normal meeting in that it is governed by the rules in the official statutes of the legal entity "Hackerspace Gent (0x20)". As a Belgian non-profit organization, Hackerspace Gent is required to host a General Assembly each year. During a general assembly, the board is elected.
|
||||
|
||||
The statutes dictate the following.
|
||||
|
||||
* The General Assembly needs to be announced at least 10 days beforehand.
|
||||
* 50% of members need to be present during a General Assembly.
|
||||
* 2/3 of members need to be present in order to change the statutes and/or the board.
|
||||
* Decisions during the General assembly need a 2/3 majority of the present members.
|
||||
* The board needs to have at least 3 members.
|
||||
|
||||
You can find the latest version of the statutes in the Government gazette (staatsblad) (Dutch-language).
|
||||
|
||||
1. Go to http://www.ejustice.just.fgov.be/tsv/tsvn.htm
|
||||
2. Fill in `0x20` in the "Benaming" field and press the "Opzoeking" button. Now you should see a number next to the "opzoeking" button, this is how many search results there are. *0x20 is the short name for "Hackerspace Gent", previously "Whitespace".*
|
||||
3. Press the "lijst" button to see all the search results.
|
||||
|
||||
More important information from the statutes.
|
||||
|
||||
* The hackerspace needs to have at least 4 members.
|
||||
* New members need to be approved by the board.
|
||||
|
|
|
@ -10,17 +10,17 @@ They are responsible for
|
|||
|
||||
- Creating and patching the guidelines and the system.
|
||||
- Solve problems when do-ocracy cannot fix them.
|
||||
- Elect board, validate membership decisions made by the board.
|
||||
- Electing the board during a General Assembly.
|
||||
- Organize workshops, events, lectures.
|
||||
|
||||
## Individual members
|
||||
|
||||
*The individuals have to be excellent.*
|
||||
|
||||
- Follow [Do-ocracy](do-ocracy.md)
|
||||
- Actively try to fix problems
|
||||
- Maintain personal safety and that of others
|
||||
- Follow and enforce the [Guidelines](guidelines.md).
|
||||
- Follow Do-ocracy.
|
||||
- Actively try to fix problems.
|
||||
- Maintain personal safety and that of others.
|
||||
- Follow and enforce the Guidelines.
|
||||
|
||||
## Non-members
|
||||
|
||||
|
|
|
@ -1,7 +1,6 @@
|
|||
# 5. Guidelines
|
||||
# 6. Guidelines
|
||||
|
||||
**Note:** For now the goal of this page is to collect ideas that YOU think should be part of the
|
||||
code of conduct for the space. Each of the points will be agreed upon using [group decision model](decision.md#members-group).
|
||||
**Note:** For now the goal of this page is to collect ideas that YOU think should be part of the guidelines for the space.
|
||||
|
||||
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.
|
||||
|
||||
|
@ -14,25 +13,25 @@ These guidelines are a practical emanation the two basic rules:
|
|||
|
||||
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).
|
||||
|
||||
## 1 Projects
|
||||
## 6.1 Projects
|
||||
|
||||
There is a clear distinction between Personal vs Space projects.
|
||||
|
||||
### Personal
|
||||
|
||||
* You have full control over what happens to the project.
|
||||
* The property of the project is considered personal property and 2.1 applies to it.
|
||||
* The property of the project is considered personal property and 6.2.1 applies to it.
|
||||
* You decide what happens to the end-result of the project.
|
||||
|
||||
### Space
|
||||
|
||||
* Decisions go through the [Flow](flow.md).
|
||||
* The property of the project is considered space property and 2.2 applies to it.
|
||||
* 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.
|
||||
|
||||
## 2 Property and tools
|
||||
## 6.2 Property and tools
|
||||
|
||||
### 2.1 Personal Property
|
||||
### 6.2.1 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.
|
||||
|
||||
|
@ -40,13 +39,13 @@ If you break personal property of another member, you have to fully reimburse th
|
|||
|
||||
All personal property that is not in a members box has to be labeled (including tools and machines).
|
||||
|
||||
### 2.2 Space Property
|
||||
### 6.2.2 Space Property
|
||||
|
||||
#### 2.2.1 Using space property
|
||||
#### 6.2.2.1 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 2.2.2.
|
||||
* If you borrow it, return it. If you damage or lose it: follow 6.2.2.2.
|
||||
* So when using something, clean it afterwards and put it back in it's place.
|
||||
* If you are not trained to use tool $FOO, don't use tool $FOO but ask an expert to teach you first.
|
||||
* If you use one of the public workstations, please shut it off when you are done.
|
||||
|
@ -57,40 +56,40 @@ All personal property that is not in a members box has to be labeled (including
|
|||
* ~~3D printer~~ (Broken: if you can fix it, you're the new expert!)
|
||||
* Table saw
|
||||
|
||||
#### 2.2.2 Damaging or losing space property
|
||||
#### 6.2.2.2 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.
|
||||
|
||||
#### 2.2.3 Taking space property out of the space
|
||||
#### 6.2.2.3 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.
|
||||
|
||||
## 3 Space maintenance
|
||||
## 6.3 Space maintenance
|
||||
|
||||
### 3.1 Cleaning
|
||||
### 6.3.1 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 deskspace 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.
|
||||
|
||||
### 3.2 Exit space
|
||||
### 6.3.2 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.
|
||||
|
||||
### 3.3 Throwing things away
|
||||
### 6.3.3 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.
|
||||
|
||||
## 4 Social behavior
|
||||
## 6.4 Social behavior
|
||||
|
||||
* When in doubt if you're doing the right thing, you probably aren't.
|
||||
* Just try not to be *that* guy.
|
||||
|
||||
### 4.1 Noise
|
||||
### 6.4.1 Noise
|
||||
|
||||
People are trying to concentrate in here so:
|
||||
|
||||
|
@ -99,7 +98,7 @@ People are trying to concentrate in here so:
|
|||
* Don't be afraid to 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.
|
||||
|
||||
### 4.2 Network/security
|
||||
### 6.4.2 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.
|
||||
|
|
Loading…
Reference in New Issue