Session:How to (re)start a hackerspace
From 36C3 Wiki
| Description | We explain how to run a do-ocracy and the lessons we learned from 6 years of hacking our own community. |
|---|---|
| Website(s) | https://hackerspace.design |
| Type | Talk |
| Kids session | No |
| Keyword(s) | |
| Tags | do-ocracy |
| Processing assembly | Assembly:HSBE |
| Person organizing | Galgalesh |
| Language | en - English |
Other sessions...
| |
(Click here to refresh this page.)
| Subtitle | Do-ocracy done well |
|---|---|
| Starts at | 2019/12/30 14:00 |
| Ends at | 2019/12/30 14:40 |
| Duration | 40 minutes |
| Location | Assembly:HSBE |
We explain how to run a do-ocracy and the lessons we learned from 6 years of hacking our own community.
- How do you solve internal conflict?
- How do you stop people from exploiting loopholes in the rules of your community?
- How do you create a culture and shared values?
- How do you keep directors from burning out?
- How do give people creative freedom?
History
Hackerspace.Gent was on the brink of collapse because of internal conflict. Instead of giving up, we decided to hack the hackerspace itself; find a system where internal conflict actually gets solved. We did an number of workshops to figure out how to do this, we wrote everything down, and got to work. Six years later, the disorganized workshop notes turned into an actual booklet: the hackerspace blueprint. We hope you can use this to solve issues in your organization.
