renamed for clarity and added more legacy

README.md

@@ -4,36 +4,29 @@ A hackerspace is a physical place, run by people interested in various aspects o
 
 We are a breeding ground for awesome ideas. We provide a nest where those ideas can become reality. We operate by collaboration and openness. We allow people to fail, and to try again.
 
-# We failed, but we try again
+## We failed, but we try again
 
 We created our very own Ghent hackerspace. We had two rules: be excellent to each other and decide everything by consensus. We thought normal human interaction and common sense would solve all problems. Sadly, this was not true. When our hackerspace almost died, we decided to "Hack the Hackerspace". We found that the problems could all be traced to the following root causes:
 
- * We cannot rely on common sense because **people have different realities.**
- * **People have different, conflicting goals.** Because of that, consensus will never be reached on certain things. Problems will arise and they will not be solved. In most cases, no solution is worse than a bad solution.
+* We cannot rely on common sense because **people have different realities.**
+* **People have different, conflicting goals.** Because of that, consensus will never be reached on certain things. Problems will arise and they will not be solved. In most cases, no solution is worse than a bad solution.
 
 We knew that, in order to fix this, we needed a system that gets the best out of everyone and enables us to be awesome! After long late-night discussions, we came up with HTH. *This git repository contains the organizational structure of our hackerspace. This is intended to be place-agnostic information so it can be used by other hackerspaces around the world.*
 
 This is divided into 3 parts. Because [naming things is very hard](http://xkcd.com/910/) we decided to use the names from the ["Silo" series of Hugh Howey](http://en.wikipedia.org/wiki/Silo_%28series%29). The series follows the life of several people living in underground silo's in a post-apocalyptic society.
 
-#### [1. The Order](https://github.com/0x20/HTH/tree/master/order)
+### [1. The System](./system)
+
 This is a description of the system that will run our hackerspace. You will find the different decision processes and the different entities of the organization.
 
 *In the series, the order is a book that describes how the silos should be managed. The order is clearly "bad" because all control is an infringement to the freedom of the people. Still, if you progress further in the series, you see that the order is still a good way to manage the people.*
 
-In the series, the order is used to control the people, and to limit their ability to progress. They want to keep the people dumb, so they're easy to manage. However, in our hackerspace, we want to do the exact opposite. Our order should empower people to get the best out of themselves. Our order should stimulate collaboration, and should enable people to think creatively and to solve problems creatively. We know that this system will be flawed from the start. We know that control of people is evil. But a flawed system is better than no system, and we will continuously patch this system to make it better. That is why this is on GitHub. So we can learn from our past mistakes and other people can stand on our shoulders to see further than anyone else.
+The system should empower people to get the best out of themselves. It should stimulate collaboration, and enable people to think creatively and to solve problems creatively. We know that this system will be flawed from the start. We know that control of people is evil. But a flawed system is better than no system, and we will continuously patch this system to make it better. That is why this is on GitHub. So we can learn from our past mistakes and other people can stand on our shoulders to see further than anyone else.
 
-#### [2. The Pact](https://github.com/0x20/HTH/tree/master/pact)
-
-This is the Code of Conduct. This is intended to be a very broad enforced guideline of how members should behave.
-
-*In the series, the pact is "The law".*
-
-Unlike in the series, our pact will be made by the group, and enforced by the group. The group can change the pact as they see fit.
-
-#### [3. The Legacy](https://github.com/0x20/HTH/tree/master/legacy)
-Because every good idea that was once written down has been misinterpreted, we included all the information that led us to the Order and the Pact in this repository as The Legacy. This should by used as a "cipher" to interpret these correctly and to explain a bit of the rationale behind them.
-
-*In the series, the legacy is a collection of all the information that remains in the old world. It serves as a warning for the people questioning the order. The legacy is only available to a selected number of people, just like the order. The legacy does not include all of history, only certain parts chosen by the people who built the silo.*
+### [2. The Guidelines](./guidelines)
 
+This is the Code of Conduct. This is intended to be a very broad guideline of how members should behave.
 
+### [3. The Legacy](./legacy)
 
+Because every good idea that was once written down has been misinterpreted, we included information that led us to the system and the guidelines in this repository as The Legacy. This should by used as a "cipher" to interpret the system and the guidelines correctly and to explain a bit of the rationale behind them.

guidelines/README.md

@@ -1,9 +1,7 @@
-# Pact Proposal
-
-The pact == code of conduct.
+# 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](../order/decision.md#members-group).
+code of conduct for the space. Each of the points will be agreed upon using [group decision model](../system/decision.md#members-group).
 
 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, different 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.
 
@@ -28,7 +26,7 @@ There is a clear distinction between Personal vs Space projects.
 
 ### Space
 
-* Decisions goes through the [Flow](../order/flow.md)
+* Decisions goes through the [Flow](../system/flow.md)
 * The property of the project is considered space property and 2.2 applies to it.
 * The Group decides what happens to the end-result of the project
 
@@ -54,7 +52,7 @@ All personal property that is not in a members box has to be labeled (including
 * 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
 
-**Space property that requires you to follow a workshop before use**
+##### Space property that requires you to follow a workshop before use
 
 * ~~3D printer~~ (Broken: if you can fix it, you're the new expert!)
 * Table-saw

legacy/README.md

@@ -0,0 +1,7 @@
+# The Legacy
+
+Because every good idea that was once written down has been misinterpreted, we included information that led us to the system and the guidelines in this repository as The Legacy. This should by used as a "cipher" to interpret the system and the guidelines correctly and to explain a bit of the rationale behind them.
+
+* [**The fall of the hacker groups.**](The_Fall_of_Hacker_Groups)
+
+* [**The tyranny of structurelessness**](http://www.jofreeman.com/joreen/tyranny.htm) is an essay by American feminist Jo Freeman inspired by her experiences in a 1960s women's liberation group that concerns power relations within radical feminist collectives. The essay looks back on the experiments of the feminist movement in creating organizations that do not have any structure or leadership. Jo Freeman states that leadership and structure did actually exist in these organizations but its existence was denied. This made it hard to hold the leadership accountable for their actions and made it hard for newcomers to figure out how the organization worked. As a solution, Freeman suggests formalizing the existing hierarchies in the group and subjecting them to democratic control.

order/README.md

@@ -1,15 +0,0 @@
-# [Roles](roles.md)
-
-Defines the roles of the different entities that are present in the space.
-
-# [Decision Making Model](decision.md)
-
-A description of the decision making models used in the different entities of the space.
-
-# [Work Flow](flow.md)
-
-The flow how decisions are made in the space.
-
-# [Do-ocracy](do-ocracy.md)
-
-The definition and boundaries of the Do-ocracy

order/do-ocracy.md

@@ -1,19 +0,0 @@
-# Do-ocracy
-
-## In short
- * If you want something done: **Just do it!**
- * Have you done something? **Great!, now tell others about it.** Tell them what you did, and why you did it. The mailing-list is a great place to do so. Telling other people about your actions lets them know who to thank and will give you more support.
- * If somebody complains: Either **revert it**, or work out a solution with the person who is complaining.
-
-## Vision behind it
-
-A do-ocracy is an organizational structure in which individuals choose to pick up roles and execute tasks by themselves, rather than getting them appointed by others.
-Responsibilities are attach to people who do the work, rather than to the elected/selected officials.
-Doing a task is in itself justification for you being the person who does that job.
-
-Source: http://www.communitywiki.org/en/DoOcracy
-
-# Boundaries
-
-Some things are to sensitive to be handled by do-ocracy alone, like throwing things away. The Pact defines what the boundaries are of the Do-ocracy. Any member can request that a decision is discussed in the group.
-

order/roles.md

@@ -1,32 +0,0 @@
-# The Board
-
-The role of the board is explained in detail in [the board document](board.md).
-
-# Group Of Members
-
-*The members make and maintain the hacker environment.*
-
-When a conflict/problem can not be resolved between individuals/via do-ocracy or when it impacts the group, a decision is required by the group. Any member can request that a decision is made by the Group Of Members instead of by do-ocracy/individual members.
-
-They are responsible for
-
- - Creating and patching Pact and the Order (in general assembly)
- - Solve problems when do-ocracy cannot fix them
- - Elect board, validate membership decisions made by the board.
- - Organize workshop, 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
- - To follow and enforce the [Pact](../pact/README.md).
-
-# Non-members
-
-Non-members are also an important part of the space. They can contribute to the hacker environment and they can be potential members. However, non-members have less privileges than members.
-
- - Non-members are only allowed in the space when they are in company of a member. That member is responsible for the actions of the non-member.
- - Non-members have to follow the Pact. A non-member is not allowed to challenge a decision made by the group. Does the non-member disagree with a decision made by the group, then he/she should become a member and bring the topic forward on a meeting.

system/README.md

@@ -0,0 +1,19 @@
+# The System
+
+An explanation of the structure of the hackerspace.
+
+## [Roles](roles.md)
+
+Defines the roles of the different entities that are present in the space.
+
+## [Decision Making Model](decision.md)
+
+A description of the decision making models used in the different entities of the space.
+
+## [Work Flow](flow.md)
+
+The flow how decisions are made in the space.
+
+## [Do-ocracy](do-ocracy.md)
+
+The definition and boundaries of the Do-ocracy.

system/decision.md

@@ -20,11 +20,11 @@ Below outlines the decision making model to be used by this group.
 | Week 2  |     Discuss in group, listen, learn and build compromise      |  80% consensus |
 | Week 3  |     Discuss in group, listen, learn and build compromise      |  Point system    |
 
-##### week 0:
+### week 0
 
 The point is put on the agenda of the weekly meeting and is announced on the mailing-list. This needs to be at least 3 days in advance.
 
-##### week 1:
+### week 1
 
 The point is discussed in group and requires a 100% consensus to reach a group decision. The motivation for striving for consensus is because consensus comes with characteristics that benefits the hackerspace:
 
@@ -35,11 +35,11 @@ The point is discussed in group and requires a 100% consensus to reach a group d
 
 The required 100% consensus also means that a very small minority can block a decision. That is a desired feature but it comes with a responsibility. When a small minority or even an individual feels very strongly that a proposed decision is not correct they have the option to block a decision. This does not stop a decision but gives the opposers 1 week of time. During that week the minority has the task to convince fellow members of their viewpoint.
 
-##### week 2:
+### week 2
 
 The point is discussed again but now a rough consensus of %80 is applied to reach a decision (https://en.wikipedia.org/wiki/Rough_consensus). If the small minority of last week was not able to convince enough fellow members the decision will be passed with rough consensus of %80. When their viewpoint make enough sense to fellow members, critical mass must be found to reach a new compromise. All members joining the discussion must strive to reach the rough consensus, to build the compromise. Not doing so is not being excellent.
 
-##### week 3:
+### week 3
 
 When all has failed, or the problem is too controversial, but a decision is still required the below point system will be used to reach a decision.
 

system/do-ocracy.md

@@ -0,0 +1,19 @@
+# Do-ocracy
+
+## In short
+
+* If you want something done: **Just do it!**
+* Have you done something? **Great!, now tell others about it.** Tell them what you did, and why you did it. The mailing-list is a great place to do so. Telling other people about your actions lets them know who to thank and will give you more support.
+* If somebody complains: Either **revert it**, or work out a solution with the person who is complaining.
+
+## Vision behind it
+
+A do-ocracy is an organizational structure in which individuals choose to pick up roles and execute tasks by themselves, rather than getting them appointed by others.
+Responsibilities are attach to people who do the work, rather than to the elected/selected officials.
+Doing a task is in itself justification for you being the person who does that job.
+
+Source: http://www.communitywiki.org/en/DoOcracy
+
+## Boundaries
+
+Some things are to sensitive to be handled by do-ocracy alone, like throwing things away. The guidelines defines what the boundaries are of the Do-ocracy. Any member can request that a decision is discussed in the group.

system/flow.md

@@ -1,5 +1,5 @@
+# The flow
+
 ![Diagram](https://cdn.rawgit.com/qwaxys/HTH/master/order/HTH-flow.svg)
 
 To edit the diagrams please use [draw.io](https://www.draw.io/?url=https%3A%2F%2Fraw.githubusercontent.com%2Fqwaxys%2FHTH%2Fmaster%2Forder%2FHTH-flow.svg). After editing export as SVG and select "Include a copy of my diagram".
-
-

system/roles.md

@@ -0,0 +1,34 @@
+# The Roles
+
+## The Board
+
+The role of the board is explained in detail in [the board document](board.md).
+
+## Group Of Members
+
+*The members make and maintain the hacker environment.*
+
+When a conflict/problem can not be resolved between individuals/via do-ocracy or when it impacts the group, a decision is required by the group. Any member can request that a decision is made by the Group Of Members instead of by do-ocracy/individual members.
+
+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.
+- Organize workshop, 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
+- To follow and enforce the [Guidelines](../guidelines/README.md).
+
+## Non-members
+
+Non-members are also an important part of the space. They can contribute to the hacker environment and they can be potential members. However, non-members have less privileges than members.
+
+- Non-members are only allowed in the space when they are in company of a member. That member is responsible for the actions of the non-member.
+- Non-members have to follow the guidelines. A non-member is not allowed to challenge a decision made by the group. Does the non-member disagree with a decision made by the group, then he/she should become a member and bring the topic forward on a meeting.