Sasja-patch-1
Merlijn Sebrechts 4 years ago
parent 8408b12df2
commit 8d4be246fe
  1. 4
      .travis.yml
  2. 4
      7-the-legacy.md
  3. 4
      README.md

@ -1,4 +1,4 @@
language: R
language: r
addons:
apt:
packages:
@ -23,6 +23,6 @@ deploy:
- hackerspace-blueprint-booklet-body.pdf
skip_cleanup: true
on:
repo: "0x20/HTH"
repo: "0x20/hackerspace-blueprint"
if:
tag IS blank

@ -2,9 +2,9 @@
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.
Some of these documents, discussions and comments on them are archived in the `legacy` folder of [the hackerspace blueprint repository](https://github.com/0x20/HTH).
Some of these documents, discussions and comments on them are archived in the `legacy` folder of [the hackerspace blueprint repository](https://github.com/0x20/hackerspace-blueprint).
* [**The fall of the hacker groups**](The_Fall_of_Hacker_Groups) makes the claim that it is becoming rare for creativity to arise from groups or teams. Even though the technological advances should make it easier to create and maintain hacker groups, they are becoming increasingly rare. The author poses the theory that this is because the same technological revolution bombards us with a constant flow of information and fear, and because we dread the thought of being alike, of sharing multiple views and opinions. As such, we are turning progressively judgmental of who we should be partnering with, on the basis that "they do not understand".
* [**The fall of the hacker groups**](http://phrack.org/issues/69/6.html) makes the claim that it is becoming rare for creativity to arise from groups or teams. Even though the technological advances should make it easier to create and maintain hacker groups, they are becoming increasingly rare. The author poses the theory that this is because the same technological revolution bombards us with a constant flow of information and fear, and because we dread the thought of being alike, of sharing multiple views and opinions. As such, we are turning progressively judgmental of who we should be partnering with, on the basis that "they do not understand".
* [**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.

@ -11,11 +11,11 @@ We created our very own Ghent hackerspace. We had two rules: be excellent to eac
* 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 "the hackerspace blueprint", a document that describes how to run a hackerspace in a way that brings out the best in people. **To get the latest PDF version of this document, go [here](https://github.com/0x20/HTH/releases/latest) and download the file `hackerspace-blueprint.pdf`.**
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 "the hackerspace blueprint", a document that describes how to run a hackerspace in a way that brings out the best in people. **To get the latest PDF version of this document, go [here](https://github.com/0x20/hackerspace-blueprint/releases/latest) and download the file `hackerspace-blueprint.pdf`.**
We have been refining this system for a few years now, tweaking the system when we encounter issues and explaining important parts in more details. This document specifically describes how Hackerspace Gent runs, but it is generic enough so that it can be easily adapted to other hackerspaces and similar organizations. Feel free to use and remix this for your own benefit, learn from our mistakes and let us know what you think of it!
The goal of this system is to empower people to get the best out of themselves. It stimulates collaboration and enables people to think and 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 continuously update this system to make it better. That is why [this is on GitHub](https://github.com/0x20/HTH), in order to make it easy to build on the hackerspace blueprint as a community.
The goal of this system is to empower people to get the best out of themselves. It stimulates collaboration and enables people to think and 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 continuously update this system to make it better. That is why [this is on GitHub](https://github.com/0x20/hackerspace-blueprint), in order to make it easy to build on the hackerspace blueprint as a community.
# 1. Overview

Loading…
Cancel
Save