rename to "the hackerspace blueprint"

Sasja-patch-1 untagged-e2dff71ae47770e89670
Merlijn Sebrechts 4 years ago
parent 8dc4a86429
commit 8408b12df2
  1. 8
      .gitignore
  2. 16
      .travis.yml
  3. 2
      5-membership.md
  4. 2
      7-the-legacy.md
  5. 20
      CONTRIBUTING.md
  6. 6
      README.md
  7. 0
      flow.svg
  8. 0
      hackerspace-blueprint-booklet-cover.pdf
  9. 3
      pandoc-metadata.yaml

8
.gitignore vendored

@ -1,6 +1,6 @@
hack-the-hackerspace.epub
hack-the-hackerspace.pdf
hack-the-hackerspace-booklet-body.pdf
hack-the-hackerspace*.html
hackerspace-blueprint.epub
hackerspace-blueprint.pdf
hackerspace-blueprint-booklet-body.pdf
hackerspace-blueprint*.html
test*.pdf
test*.tex

@ -6,21 +6,21 @@ addons:
install: tlmgr install mdframed mweights needspace sourcecodepro sourcesanspro collection-fontsextra pdfjam
script: |
# Generate epub
pandoc --verbose pandoc-metadata.yaml README.md [0-9]*.md -o hack-the-hackerspace.epub --metadata date="`date +%D`" --toc-depth=2 --epub-embed-font='epub-fonts/*.ttf' --css=epub.css
pandoc --verbose pandoc-metadata.yaml README.md [0-9]*.md -o hackerspace-blueprint.epub --metadata date="`date +%D`" --toc-depth=2 --epub-embed-font='epub-fonts/*.ttf' --css=epub.css
# Generate PDF
pandoc --verbose pandoc-metadata.yaml README.md [0-9]*.md -o hack-the-hackerspace.pdf --metadata date="`date +%D`" --template eisvogel.tex --include-before-body=include-cover.tex --include-after-body=include-back.tex
pandoc --verbose pandoc-metadata.yaml README.md [0-9]*.md -o hackerspace-blueprint.pdf --metadata date="`date +%D`" --template eisvogel.tex --include-before-body=include-cover.tex --include-after-body=include-back.tex
# Generate booklet
numpages=$(pdfinfo hack-the-hackerspace.pdf | awk '/^Pages/ { print $2}')
pdfbook hack-the-hackerspace.pdf 2-$(($numpages-2)) -o hack-the-hackerspace-booklet-body.pdf
numpages=$(pdfinfo hackerspace-blueprint.pdf | awk '/^Pages/ { print $2}')
pdfbook hackerspace-blueprint.pdf 2-$(($numpages-2)) -o hackerspace-blueprint-booklet-body.pdf
deploy:
provider: releases
api_key:
secure: cIRIKuDWejK79Kojh2URkQBmQcKDJtH/MmrzgCySQ7ArjbZ6/cPkS014QbNmUft4GiRGZzIiulfkkvLtdT4UVGVXEw7gTK/V5b6bEci6fst4rDPL/hCDeXcLutOxcOwb7vei38V5XhE+1D2UcFQFNJFkeo60WKWR9ybIQ7pAemo=
file:
- hack-the-hackerspace.epub
- hack-the-hackerspace.pdf
- hack-the-hackerspace-booklet-cover.pdf
- hack-the-hackerspace-booklet-body.pdf
- hackerspace-blueprint.epub
- hackerspace-blueprint.pdf
- hackerspace-blueprint-booklet-cover.pdf
- hackerspace-blueprint-booklet-body.pdf
skip_cleanup: true
on:
repo: "0x20/HTH"

@ -24,7 +24,7 @@ When a conflict/problem can not be resolved between individuals/via do-ocracy or
The members should do the following things as a group.
* Creating and patching Hack the Hackerspace.
* Creating and patching the hackerspace blueprint.
* Solve problems in the hackerspace when do-ocracy cannot fix them.
* Electing the board during a General Assembly.

@ -2,7 +2,7 @@
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 Hack the Hackerspace 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/HTH).
* [**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".

@ -1,6 +1,6 @@
# Contributing to Hack the Hackerspace
# Contributing to the hackerspace blueprint
## Building Hack the Hackerspace
## Building the book
First install the build tools.
@ -11,13 +11,11 @@ sudo apt install pandoc texlive-plain-generic texlive-latex-extra texlive-fonts-
Generate the print version using `pandoc`.
```bash
pandoc --verbose pandoc-metadata.yaml README.md [0-9]*.md -o hack-the-hackerspace.pdf --template eisvogel.tex --toc --listings --metadata date="`date +%D`" --include-before-body=include-cover.tex --include-after-body=include-back.tex
```
Generate the booklet version from the print version. The cover and back should be printed separately.
```bash
pandoc --verbose pandoc-metadata.yaml README.md [0-9]*.md -o hack-the-hackerspace.pdf --template eisvogel.tex --toc --listings --metadata date="`date +%D`" --include-before-body=include-cover.tex
numpages=$(pdfinfo hack-the-hackerspace.pdf | awk '/^Pages/ { print $2}')
pdfbook hack-the-hackerspace.pdf 2-$(($numpages-2)) -o hack-the-hackerspace-booklet-body.pdf
# Generate epub
pandoc --verbose pandoc-metadata.yaml README.md [0-9]*.md -o hackerspace-blueprint.epub --metadata date="`date +%D`" --toc-depth=2 --epub-embed-font='epub-fonts/*.ttf' --css=epub.css
# Generate PDF
pandoc --verbose pandoc-metadata.yaml README.md [0-9]*.md -o hackerspace-blueprint.pdf --metadata date="`date +%D`" --template eisvogel.tex --include-before-body=include-cover.tex --include-after-body=include-back.tex
# Generate booklet
numpages=$(pdfinfo hackerspace-blueprint.pdf | awk '/^Pages/ { print $2}')
pdfbook hackerspace-blueprint.pdf 2-$(($numpages-2)) -o hackerspace-blueprint-booklet-body.pdf
```

@ -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 "Hack the Hackerspace" (HTH), 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 `hack-the-hackerspace.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/HTH/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 Hack the Hackerspace 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/HTH), in order to make it easy to build on the hackerspace blueprint as a community.
# 1. Overview
@ -25,4 +25,4 @@ However, when you want to do something that affect a lot of people in the space,
Every organization has a number of unspoken guidelines of how you should behave, we have written down some of ours in Section 6 in order to make it easier for people to get a sense of what to do in certain situations. These **guidelines** are not meant to be strict rules, but they give an overview of what is good and bad behavior in the space.
Because every good idea that was once written down has been misinterpreted, we included information that led us to the system and the guidelines. We call it **the legacy**. It is a collection of information that we used to create Hack the Hackerspace, it gives more context to why the system is the way it is. The legacy should by used as a "cipher" to interpret the system and the guidelines correctly and to explain a bit of the rationale behind them.
Because every good idea that was once written down has been misinterpreted, we included information that led us to the system and the guidelines. We call it **the legacy**. It is a collection of information that we used to create the hackerspace blueprint, it gives more context to why the system is the way it is. The legacy should by used as a "cipher" to interpret the system and the guidelines correctly and to explain a bit of the rationale behind them.

Before

Width:  |  Height:  |  Size: 29 KiB

After

Width:  |  Height:  |  Size: 29 KiB

@ -4,7 +4,8 @@
#
#
#
title: "Hack The Hackerspace Manifesto: empowering people to be awesome"
title: "The Hackerspace Blueprint"
subtitle: "Empowering people to be awesome"
author: [Merlijn Sebrechts, Hackerspace Gent]
tags: [Do-ocracy, Hackerspace, Self-governance, Structureless Organizations]
language: en

Loading…
Cancel
Save