[00:00.000 --> 00:01.400]  A huge round of applause, please.
[00:01.780 --> 00:02.660]  They're awesome.
[00:05.360 --> 00:07.680]  They produce epic, epic awesome.
[00:08.280 --> 00:11.740]  And I probably shouldn't say too much about HacDC since it might be a conflict of interest.
[00:12.020 --> 00:22.880]  And in this country now, only a year after this talk was first given, we have 12 different cities in the United States that are all actively developing hackerspace projects.
[00:23.560 --> 00:27.520]  Hack... or... Hack Toronto dot... Wait, what was Toronto's hackerspace?
[00:28.140 --> 00:29.380]  Hack dot T.O.
[00:30.540 --> 00:31.600]  Hack lab dot T.O.
[00:32.180 --> 00:34.460]  We have Kansas City, Texarkana.
[00:34.640 --> 00:39.780]  A lot of hackerspaces are in progress as a direct result of the first version of this talk.
[00:40.000 --> 00:43.360]  So without any further ado, I present to you Jens Oleg with Hackerspace Design Patterns.
[00:43.380 --> 00:45.920]  Give him a huge, huge round of applause.
[00:50.860 --> 00:53.960]  Yeah, it's really an honor to be here for me.
[00:53.960 --> 00:58.120]  And I really feel like this is coming to a full circle.
[00:58.360 --> 01:10.640]  Like this whole thing started one year ago and now the updated version of the talk that we prepared like one year ago is here at The Last HOPE.
[01:13.160 --> 01:19.600]  So, what I'm going to talk about is hackerspace design patterns and the catalog that we compiled for that.
[01:19.780 --> 01:22.580]  I will explain why we call it design patterns.
[01:23.220 --> 01:27.840]  But first I will just introduce myself and introduce the people behind this presentation.
[01:28.060 --> 01:33.260]  And then, yeah, the largest part of the presentation is actually the catalog that I will present.
[01:36.260 --> 01:42.000]  So, there's just one person on stage right now, but there are many people behind this talk.
[01:43.220 --> 01:46.840]  Unfortunately, Lars Weiler, Pülon, of CCC Cologne couldn't make it.
[01:46.940 --> 01:56.380]  We were supposed to talk together, but at the last minute he received a very typical hacker electricity bill.
[01:56.380 --> 02:01.220]  So, his ticket to HOPE went away with that.
[02:02.160 --> 02:05.940]  Thorsten Haas, also of CCC Cologne, contributed many patterns.
[02:06.520 --> 02:10.660]  I also exchanged ideas with Tim Pridloff of CCC Berlin.
[02:10.960 --> 02:11.980]  Paul Boehm...
[02:11.980 --> 02:13.320]  How did we enter the country?
[02:13.660 --> 02:14.340]  Yeah.
[02:15.100 --> 02:18.180]  Paul Boehm of Mitterlab in Vienna unfortunately couldn't make it.
[02:18.180 --> 02:21.680]  But he also had some contributions to this talk.
[02:22.060 --> 02:24.420]  And many, many people from the CCC provided feedback.
[02:24.780 --> 02:26.880]  And, of course, the American hackers scene.
[02:27.000 --> 02:37.260]  We prepared this talk to present our experience of 10 or 15 years of building hackerspaces and putting it in one piece.
[02:38.040 --> 02:38.640]  Yeah.
[02:39.160 --> 02:41.600]  Just because of that visit of American hackers.
[02:41.920 --> 02:44.620]  So, you are also to thank Thor.
[02:45.760 --> 02:47.540]  My name is Jens Ohlig.
[02:47.920 --> 02:49.100]  I know it's a weird name.
[02:49.380 --> 02:49.960]  It's a...
[02:49.960 --> 02:50.160]  Yeah.
[02:51.180 --> 02:53.000]  A German version of Johannes.
[02:53.300 --> 02:55.160]  So, would be John in English.
[02:55.320 --> 02:57.480]  But, because it looks like a girl's name.
[02:57.640 --> 02:57.980]  Like Jen.
[02:58.760 --> 03:00.480]  People give me free stuff online.
[03:04.340 --> 03:08.820]  I'm one of the co-founders of the Chaos Computer Club in Cologne in Germany.
[03:09.200 --> 03:10.520]  I'm still active there.
[03:10.860 --> 03:14.540]  I've been an activist for the CCC in general.
[03:14.540 --> 03:17.440]  In Germany for more than 15 years now.
[03:18.520 --> 03:19.280]  And, I...
[03:19.280 --> 03:21.900]  At one point, I was a spokesperson for the CCC.
[03:22.220 --> 03:22.920]  Talked to the press.
[03:23.060 --> 03:24.700]  Talked to other organizations for them.
[03:24.860 --> 03:26.880]  I was a member on the board of the CCC.
[03:27.660 --> 03:29.380]  But, yeah.
[03:29.460 --> 03:31.460]  For personal reasons, I stopped doing that.
[03:31.720 --> 03:34.020]  But, I still follow the organization very closely.
[03:34.260 --> 03:41.620]  I'm involved with the annual Chaos Communication Congress that takes place every year between Christmas and New Year.
[03:44.100 --> 03:47.480]  The CCC in Cologne was founded in 1997.
[03:48.080 --> 03:49.860]  And we have around 42 members.
[03:51.380 --> 03:51.980]  We...
[03:51.980 --> 03:55.320]  We don't actually know, but we think that 42 is a good number.
[03:55.600 --> 03:56.840]  It's a good premium number.
[03:57.840 --> 03:59.040]  But, around...
[03:59.040 --> 03:59.120]  Yeah.
[03:59.360 --> 03:59.720]  50...
[03:59.720 --> 04:00.580]  Less than 50 people.
[04:01.620 --> 04:06.200]  And there are also people who technically are members, but don't show up anymore.
[04:06.700 --> 04:10.160]  And we are currently in our third point...
[04:10.160 --> 04:12.320]  Fifth version of our hackerspace.
[04:12.320 --> 04:19.260]  Our first version was in a bar that we got hold of.
[04:19.500 --> 04:23.720]  But, we later found out why we were able to get a lease for that bar.
[04:23.920 --> 04:30.920]  Because the person who ran that bar was away on a state-sponsored holiday.
[04:32.280 --> 04:40.100]  And, actually, we had lots of people turning up at our place asking where the new place to buy the Coke was.
[04:40.100 --> 04:40.980]  And...
[04:42.200 --> 04:42.740]  Yeah.
[04:42.960 --> 04:44.300]  We moved out of that place.
[04:45.380 --> 04:48.840]  And then found another place, which was just too small.
[04:49.040 --> 04:52.860]  And then, we had a new place, but we only used half of the space.
[04:53.160 --> 04:56.700]  And the other half was going to someone who actually lived there.
[04:56.820 --> 05:03.920]  And when that person moved out, our group was strong enough to just take over the whole space.
[05:04.080 --> 05:06.120]  So, that's where we are now.
[05:06.120 --> 05:10.460]  And all the pictures in this presentation were taken at the C4 hackerspace.
[05:10.640 --> 05:14.240]  At the CCC Cologne hackerspace, which we abbreviate C4.
[05:14.480 --> 05:16.020]  Like the plastic explosives.
[05:20.140 --> 05:22.340]  So, why did we compile this catalog?
[05:23.300 --> 05:23.760]  Yeah.
[05:24.120 --> 05:38.440]  Just as Nick Farr has mentioned before, in August 2007, a group of North American hackers, I should say, not all of them were from the U.S., visited spaces in Germany and in Austria, mainly.
[05:38.440 --> 05:48.220]  And they actually wanted to know how the places that we have work, how these self-organized hacker labs work.
[05:48.220 --> 05:59.280]  And, yeah, after the case communication camp, near Berlin, they just went around Europe, German-speaking Europe mainly, and visited a couple of these spaces.
[05:59.680 --> 06:03.220]  Every space did a little presentation on its history.
[06:03.220 --> 06:11.740]  And we were thinking about a good metaphor of sharing our experience with that thing.
[06:12.040 --> 06:14.820]  And we looked at design patterns.
[06:16.220 --> 06:29.340]  Design patterns, as most of you may know, are used in software engineering as a term for, yeah, typical situations where you could apply one approach to a solution.
[06:30.180 --> 06:33.680]  And, originally, they come from urban planning.
[06:34.160 --> 06:44.400]  So, a typical design pattern when planning out a city would be that you would somehow have to have a center for recreational things somewhere.
[06:45.220 --> 06:48.640]  And then you would put that pattern into use into your design.
[06:51.200 --> 07:10.940]  So, what is different in this design pattern metaphor from, let's say, a cookbook metaphor, we don't think that giving you a step-by-step manual would work, because the circumstances are very different, and you will run into very different problems depending on your environment.
[07:12.000 --> 07:25.780]  But, rather, we just want to provide a big box of LEGO bricks where you can get out tested patterns and then build your own solution.
[07:29.080 --> 07:29.890]  Yeah.
[07:31.420 --> 07:33.840]  And, of course, your mileage may vary.
[07:35.640 --> 07:41.080]  So, this is going to be the design patterns catalog.
[07:41.830 --> 07:45.650]  First group we called sustainability patterns.
[07:46.020 --> 07:51.420]  So, when starting a hackerspace, you have a chicken and egg problem.
[07:51.420 --> 07:55.860]  Should you concentrate on the infrastructure or the projects?
[07:56.770 --> 08:01.300]  And our solutions to that is that everything should be infrastructure-driven.
[08:01.720 --> 08:06.720]  You should have rooms and power and service, connectivity and other facilities first.
[08:07.220 --> 08:16.150]  And then, once you have the infrastructure in place, people will come up with amazing projects that you didn't imagine in the first place.
[08:16.150 --> 08:30.420]  This planning for the unexpected is also something that you will see a lot of times when running your self-organized hacker lab.
[08:32.430 --> 08:33.330]  So, yeah.
[08:33.480 --> 08:36.480]  This is a place where we have our network operations center in Cologne.
[08:39.060 --> 08:39.580]  Yeah.
[08:40.600 --> 08:43.980]  And many people... actually, there's a talk about that tomorrow.
[08:44.980 --> 08:48.180]  Excuses that people use for not opening a hackerspace.
[08:49.000 --> 08:56.620]  And one of the most often heard excuses is, is it really the time now to start your hackerspace?
[08:56.620 --> 08:57.520]  Shouldn't you wait?
[08:57.840 --> 08:59.820]  Have you really thought of all the problems?
[09:00.400 --> 09:06.280]  Some people spend a lot of time on designing very elaborate bylaws or...
[09:06.280 --> 09:07.360]  Yeah.
[09:07.500 --> 09:14.880]  Just going through every possible potential problem that they just might run into and then nothing gets done.
[09:16.080 --> 09:24.960]  So, we think that the time is right now and it's always easier to ask forgiveness than to get permission.
[09:24.960 --> 09:32.580]  That's what Grace Hopper, one of the pioneers of computer science, said, who was also a U.S. Navy Rear Admiral.
[09:33.220 --> 09:35.600]  It's very important to just start.
[09:35.800 --> 09:39.220]  Many of the problems you think of will vanish as soon as you get started.
[09:39.480 --> 09:40.820]  And when in doubt, just do it.
[09:42.480 --> 09:43.580]  And, yeah.
[09:43.760 --> 09:45.980]  How can you communicate in such a group?
[09:48.320 --> 09:51.500]  We get asked that question, but we don't really understand why.
[09:51.800 --> 09:54.220]  Because you're hackers and you should know what to do.
[09:54.440 --> 09:58.900]  You should stop slacking and set up a mailing list, a wiki, and an IRC channel.
[09:59.060 --> 10:00.020]  And you will need all three.
[10:01.580 --> 10:11.620]  Actually, you don't need these things that I just mentioned, but you have to think along the lines of what they provide as a platform.
[10:11.620 --> 10:20.080]  You will need a platform for discussion, maybe a mailing list, and you will need storage for collaborative documentation.
[10:20.460 --> 10:27.360]  A wiki is a good idea, and maybe using media wiki, like the software that powers Wikipedia.
[10:27.760 --> 10:31.700]  And you will have to have something for real-time communication.
[10:31.700 --> 10:39.440]  IRC is one option, but you could also have an XMPP Jabba server and do nifty stuff.
[10:40.040 --> 10:47.480]  There is an implementation of Jabba server that lets you share all the roasters with all the members.
[10:47.760 --> 10:51.980]  So everyone who is in that group will be on each other's buddy lists.
[10:53.070 --> 10:56.220]  You will really need all these three things.
[10:56.440 --> 10:59.760]  Exchanging cell phone numbers can also help.
[10:59.760 --> 11:06.460]  But, you know, you need to have one platform where you do actual discussions and come to a conclusion.
[11:07.080 --> 11:09.560]  And mail seems to be that medium for that.
[11:09.780 --> 11:14.860]  You will have to document your stuff, and from time to time you have to do real-time communication.
[11:15.440 --> 11:22.860]  Most of the failed attempts at creating hackerspaces neglected one aspect or the other that I've seen.
[11:24.860 --> 11:28.220]  And also being alone doesn't help you.
[11:28.340 --> 11:31.680]  You want to set up a hackerspace in your city alone and you fail.
[11:32.280 --> 11:36.320]  We think that you need to reach a critical mass.
[11:36.680 --> 11:41.060]  And for us that rule of thumb is two plus two persons.
[11:41.960 --> 11:51.020]  You need a partner to kick around the initial vision and exchange ideas about that vision that you have.
[11:51.740 --> 11:55.740]  And then you will need two more people in order to get real work done.
[11:56.940 --> 12:01.400]  Stuff like transporting physical items and stuff.
[12:02.380 --> 12:05.900]  And you shouldn't start before you have at least four people.
[12:06.440 --> 12:12.260]  And once you have that group of four people, it's easy to recruit more people because everyone has friends.
[12:12.260 --> 12:20.160]  And it seems like ten people as a start is a good number for sustainable hackerspace to have.
[12:21.600 --> 12:29.600]  Most attempts that we've seen where hackerspaces took off really took off after they have reached that point of ten people.
[12:30.060 --> 12:37.380]  And most failed attempts that we've seen was just one person in a city trying to do things on their own.
[12:40.220 --> 12:43.600]  And you would also have to need strong personalities.
[12:44.340 --> 12:45.400]  That's what we call that pattern.
[12:45.580 --> 12:46.380]  Nothing gets done.
[12:46.740 --> 12:47.640]  That's a problem.
[12:47.840 --> 12:51.140]  You all want the hackerspace, but it's so hard to get off your asses.
[12:52.620 --> 12:57.280]  You should look for strong personalities as members of your original group.
[12:57.780 --> 13:00.180]  People that have experience in building structures.
[13:01.200 --> 13:06.840]  And what I find most important is look for people who have authority and get respect.
[13:06.840 --> 13:10.440]  and not for people who use authority and get laughed at.
[13:10.800 --> 13:14.560]  Especially, yeah, in anti-authoritarian hacker circles.
[13:20.610 --> 13:21.370]  Okay.
[13:22.190 --> 13:24.170]  Another infrastructure...
[13:24.170 --> 13:31.230]  Oh, you might say I have not properly Americanized slides, but I hope you don't mind.
[13:33.050 --> 13:39.910]  The landlord and neighborhood pattern is another pattern for infrastructure that we see.
[13:41.170 --> 13:48.830]  Maybe you think you have found the perfect hackerspace, but the landlord is somewhat weird and the neighbors are picky.
[13:49.470 --> 13:53.990]  You should really reconsider if that space is the perfect space for you.
[13:54.250 --> 13:56.510]  Because we think you should choose wisely.
[13:56.810 --> 14:04.510]  And a benevolent but uninterested landlord and cool neighbors can be the decisive reason why the hackerspace takes off or not.
[14:05.370 --> 14:08.130]  Not so cool neighbors may call the cops at 2 a.m.
[14:08.470 --> 14:11.070]  Depending on your projects, this may be a serious problem.
[14:12.490 --> 14:19.150]  As hackers, we do not live the majority lifestyle and you should look for neighbors who are also weird and outside the majority.
[14:19.590 --> 14:24.610]  Let me tell you something about the neighbors we have at our hackerspace in Cologne, C4.
[14:24.610 --> 14:28.750]  We have our hackerspace next to a dominatrix studio.
[14:29.610 --> 14:36.590]  And this seems to work pretty well because they are interested in privacy.
[14:37.090 --> 14:38.570]  And so we are.
[14:39.890 --> 14:53.750]  It used to be a problem like having young, unwashed computer people running around that line of waiting businessmen in front of our neighbor's doors.
[14:53.970 --> 14:59.730]  But we finally found a way to get around that.
[14:59.730 --> 15:05.930]  And also, I've heard that this just goes very well together.
[15:06.170 --> 15:09.070]  I think in America you say like chocolate and peanut butter.
[15:11.050 --> 15:20.850]  Other hackerspaces I know of in Karlsruhe, in southern Germany, they share a space with a, I think, gay youth organization or something.
[15:20.850 --> 15:30.390]  So, just realize that you do not live inside the majority lifestyle and having cool neighbors that also, yeah, are outside the majority.
[15:31.250 --> 15:34.530]  Yeah, that's a big point, I think.
[15:38.900 --> 15:45.020]  One question that always comes up is, it's really, really expensive to pay for the space.
[15:45.020 --> 15:51.580]  So maybe that guy who's really cool could live in there and we could just use that space.
[15:51.980 --> 15:57.340]  And, or maybe we could be flat sharing and have a hackerspace in that flat as well.
[15:58.440 --> 16:02.320]  And, yeah, that always causes privacy problems.
[16:04.000 --> 16:07.660]  I don't think I've ever seen that to work out.
[16:08.100 --> 16:19.320]  And that's why our suggestion for the problem is that guests are really fine, but you just don't let anyone live there and you should kick the people out if necessary.
[16:20.160 --> 16:27.120]  We've had some really bad experience with people just making that, yeah, the place where they lived.
[16:27.480 --> 16:35.300]  And, in the end, yeah, privacy issues like someone wants to bring over their girlfriend or whatever.
[16:36.840 --> 16:38.120]  It's just inevitable.
[16:39.480 --> 16:45.460]  It should be, like, the perfect living room, the hackerspace, without anyone living there, you know.
[16:48.400 --> 16:49.680]  Yeah, separate.
[16:50.020 --> 16:54.660]  That's a word I made up because I couldn't possibly find an English word for that.
[16:54.660 --> 16:55.960]  So I took a French word.
[16:58.100 --> 17:08.480]  What you want to have is a well-structured hackerspace with rooms to chill, to discuss, or work in small groups.
[17:09.020 --> 17:21.680]  And when the main room is occupied, you want to have another place where you can go to, and split the groups, or this may be more of a European problem.
[17:21.840 --> 17:31.440]  You want to smoke a cigarette at the space without disturbing non-smokers, without disturbing non-smokers, or without disturbing non-smokers.
[17:34.320 --> 17:36.100]  Depends on what side you're on.
[17:38.880 --> 17:50.160]  So what we found was very practical, have a hackerspace with smaller separate rooms, and you can use curtains or doors to separate them from the main room.
[17:51.200 --> 18:01.260]  And, yeah, the smoking question seemed to come up in all the European hackerspaces I know of, and just having a smoker's room works for us.
[18:02.120 --> 18:14.740]  So this, on the bottom of the page you can see how it is organized with smaller rooms that we have, with a main room and smaller rooms where groups can work in.
[18:16.740 --> 18:21.800]  Kitchen, as a human being you need food, and as a hacker you need caffeine and food at all times.
[18:22.480 --> 18:27.260]  So, one solution for that problem would be to have a kitchen at your space.
[18:28.000 --> 18:31.960]  And we think nothing brings people together like cooking together.
[18:33.220 --> 18:35.240]  Have fridges for Club-Mate.
[18:35.740 --> 18:38.600]  Selling soft rings will help you raise money for the rent.
[18:38.960 --> 18:48.220]  Actually, most of the spaces I know of selling soft rings is really a huge part of their budget, and of how they finance their spaces.
[18:49.060 --> 18:54.420]  Sometimes maybe half of the money comes from selling drinks.
[18:55.160 --> 19:02.940]  And you should invest in the single most important piece of hardware, a dishwasher, because that will end so many discussions immediately.
[19:03.880 --> 19:13.300]  And you should have a freezer for pizzas and buy decent kitchen equipment, like really good knives and lots of pans and lots of pots.
[19:13.500 --> 19:16.320]  And you should show nerds how to cook real food.
[19:17.500 --> 19:19.360]  And that's the kitchen we have in Cologne.
[19:20.780 --> 19:25.500]  And just a few weeks ago, we had a visitor from NYC Resistor.
[19:25.700 --> 19:32.820]  Rose White was there, and she taught us how to make Louisiana-style gumbo, which was a nice experience.
[19:36.720 --> 19:42.980]  And, yeah, having a nice, cozy hackerspace is an important thing.
[19:43.200 --> 19:45.820]  All work and no play makes Jack a dull boy.
[19:46.100 --> 19:49.980]  There must be something else in addition to just workstations and electronics.
[19:49.980 --> 19:55.100]  So, I think you should equip your hackerspace accordingly.
[19:55.620 --> 20:04.520]  You should bring in couches, sofas, comfortable chairs, tables, ashtrays, ambient lights, stereo equipment, projector, and video game consoles.
[20:05.540 --> 20:08.260]  Bringing in plants didn't work for us that well.
[20:11.840 --> 20:26.340]  Actually, I've heard that at the hackerspace in New York City, NYC Resistor, there was a task force of two people who said, no, we don't think that's a natural law, like bringing in plants in hackerspaces won't work.
[20:26.340 --> 20:28.540]  So, they tried and they failed.
[20:31.360 --> 20:38.380]  And, yeah, that's one of the rooms that we have for just relaxing, discussing.
[20:40.160 --> 20:42.680]  That's a documentation of our poor plant, Igor.
[20:45.760 --> 20:47.140]  It's because of the logo.
[20:48.020 --> 20:51.220]  It may have something to do with the logo, yes, I don't know.
[20:55.860 --> 20:56.820]  Um, yeah.
[20:58.300 --> 21:01.480]  After long hacking sessions, you will start to smell funny.
[21:01.740 --> 21:06.160]  Also, gas to your space sometimes neglect personal hygiene.
[21:07.100 --> 21:10.280]  So, an obvious solution for that.
[21:11.080 --> 21:15.900]  And I think this is also, like, the gold standard for hackerspaces.
[21:16.140 --> 21:21.960]  We used to have a map of all the regional groups of the Chaos Computer Club in Germany and all the spaces they had.
[21:21.960 --> 21:28.420]  And they had a special pictogram if that space had a bathroom with a shower.
[21:28.780 --> 21:32.140]  And we think the discriminating hackerspace has a bathroom with a shower.
[21:32.420 --> 21:34.840]  Because that's, like, going the extra mile.
[21:35.580 --> 21:39.780]  Um, after long hacking nights, you will have the best ideas by taking a shower.
[21:39.780 --> 21:41.500]  This has happened more than one time.
[21:41.800 --> 21:43.220]  Someone working on a project.
[21:43.480 --> 21:46.280]  And then, um, at, like, 6 a.m. in the morning, um, they took a shower.
[21:48.760 --> 21:50.920]  And then, suddenly, the solution was there.
[21:51.260 --> 21:55.980]  Guests from other spaces may stay for several weeks or several days.
[21:56.280 --> 21:59.080]  Weeks probably not that wise, but several days.
[21:59.080 --> 22:00.720]  Uh, we call them au pair hackers.
[22:01.060 --> 22:15.460]  Um, we have little, little, um, um, little boxes at our hackerspace where every member has a little box where you can put in hardware or letters that were sent to that, or parcels that were sent to that hackerspace.
[22:15.460 --> 22:18.760]  And there's also one box for au pair hackers.
[22:19.140 --> 22:22.360]  And in that box, we keep, uh, extra keys for guests.
[22:22.780 --> 22:29.740]  And also, we keep, like, uh, yeah, random stuff like, uh, uh, tickets for, for museums in Cologne.
[22:29.980 --> 22:32.920]  So they can do touristy stuff while they're visiting ourselves.
[22:33.600 --> 22:43.900]  So, and, um, if you really, really, really want to go for an extra effort, you can buy a washing machine to get rid of the smelly towels, which we did.
[22:43.900 --> 22:46.940]  And then later we also bought a dryer.
[22:47.260 --> 22:49.940]  But maybe we're overdoing that thing a bit.
[22:52.580 --> 22:54.080]  So that's our bathroom.
[22:58.050 --> 23:06.510]  Yes, um, most questions that people have, uh, uh, around that, uh, thing of how to finance the hackerspace.
[23:06.790 --> 23:08.990]  You need to pay your rent and utilities.
[23:09.050 --> 23:14.930]  And this is, this is where really, uh, the regional differences come into.
[23:16.070 --> 23:20.030]  It's rather cheap for us in Germany to have a space like that.
[23:20.390 --> 23:28.850]  And I, I know it's almost impossible to have, uh, cheap rent in New York City or anywhere that you would want to live in New York City.
[23:29.550 --> 23:32.110]  Um, so, yeah.
[23:32.510 --> 23:38.950]  This is really where you cannot make a step-by-step manual, but you will have to find your own creative solutions.
[23:39.210 --> 23:42.890]  And people have come up with, uh, various solutions for that.
[23:43.190 --> 23:49.910]  But, um, it basically boils down to that, that you have to have fees that you collect regularly.
[23:49.910 --> 24:02.130]  I've heard that, um, yeah, if you don't have problems with the privacy issues, PayPal works very well because it will automatically collect the fees every month and you don't have to run after people.
[24:02.470 --> 24:04.590]  Have you paid your fee this month?
[24:04.790 --> 24:05.750]  And so on.
[24:05.890 --> 24:08.150]  And you shouldn't make no exceptions ever.
[24:08.850 --> 24:11.230]  Uh, you should choose an appropriate amount.
[24:11.230 --> 24:22.350]  Like, if you just say, hmm, $200 per month, then I would say it's not appropriate because, um, so many people simply wouldn't be able to afford that.
[24:22.930 --> 24:26.170]  Um, you should also think about having discounts for students.
[24:26.590 --> 24:31.090]  We also thought about having discounts for people who are unemployed.
[24:31.710 --> 24:35.830]  Um, so this is just something that you would have to discuss with your group.
[24:36.570 --> 24:45.130]  Um, what we made as a rule, and what I think works very well is have at least three months of rent on your account all the time.
[24:45.370 --> 24:45.850]  No exceptions.
[24:46.910 --> 24:51.350]  Because that would really make you sleep easier.
[24:52.150 --> 24:55.110]  Um, and you should elect a totalitarian treasure.
[24:57.390 --> 24:58.510]  Um, someone...
[24:58.510 --> 25:09.130]  Actually, I feel prey to our, uh, to the totalitarian treasure just a month ago because I, uh, I forgot to pay my fees.
[25:09.470 --> 25:13.370]  And then he sent me an email and I didn't reply.
[25:14.210 --> 25:18.410]  And, uh, then he outed me on our internal mailing list.
[25:19.530 --> 25:20.770]  Which was horrible.
[25:24.400 --> 25:29.220]  Um, sponsorship is one question I get asked a lot by Americans.
[25:29.220 --> 25:33.380]  Uh, we have made only negative experience with sponsorship.
[25:34.020 --> 25:36.000]  So we call it the sponsoring anti-pattern.
[25:36.420 --> 25:45.120]  Most people think it's a good idea to meet at a company that likes you, or maybe at a university where most of you study anyway.
[25:45.500 --> 25:51.920]  And, um, I think I should stress that, um, this is a really, really bad idea.
[25:53.100 --> 25:56.660]  You should never ever depend your space on external sponsors.
[25:57.380 --> 26:00.120]  Donations are great when they come from companies.
[26:00.420 --> 26:03.220]  But, uh, you should remember that companies can go bankrupt.
[26:03.980 --> 26:07.620]  And, um, when meeting at a university, you won't be a student forever.
[26:08.220 --> 26:10.880]  And also, it creates a kind of environment.
[26:11.100 --> 26:17.140]  Meeting at a university will exclude younger people like high school kids or people who don't like the university culture.
[26:17.960 --> 26:23.540]  And, um, yeah, having a sponsorship from a company means several other problems.
[26:23.700 --> 26:29.540]  No company, no matter how nice, we'll give away presents forever without asking for favors in return.
[26:30.140 --> 26:31.580]  That's just capitalism.
[26:34.660 --> 26:44.240]  Um, the next, uh, set of patterns that I want to introduce are all patterns that have to do with, uh, how to have regular meetings, organizational patterns.
[26:44.820 --> 26:58.820]  And, uh, if you want to have, um, if you want to resolve internal conflicts, exercise democratic decision-making, and discuss recent issues and future plan, there's just one way to go.
[26:59.640 --> 27:08.780]  Um, we call it plenum, which I was told is a very highbrow word in English, but, um, it just means a meeting where everyone attends.
[27:09.120 --> 27:12.060]  A regular meeting with all members, if possible.
[27:12.060 --> 27:14.680]  you should have an agenda and set goals.
[27:14.900 --> 27:21.660]  Maybe discuss that agenda before that on your mailing list and, uh, make people commit themselves to tasks.
[27:21.860 --> 27:42.360]  Like, um, yeah, we actually had a tradition of banning, uh, sentences that start with somebody should, or, uh, uh, there should be something, or sometimes we should think about, and, yeah, just banning that word, should, and especially if it comes together with somebody.
[27:42.760 --> 27:48.600]  Um, you should say stuff like, I will take care of this problem.
[27:49.120 --> 27:54.080]  Uh, you should write down the minutes of the meeting and post them on the mailing list or on the wiki.
[27:54.880 --> 27:59.920]  And, um, yeah, you should go for the only date that works, which is once a week.
[28:00.400 --> 28:09.820]  Um, I've seen so many hacker groups fail because they don't go for that only date that works, once a week, which everyone can remember.
[28:10.040 --> 28:11.600]  Ah, it's that day of the week.
[28:11.900 --> 28:13.860]  I will tell you later which day it is.
[28:14.040 --> 28:18.600]  Uh, it's that day of the week, um, so I have to go to the meeting tonight.
[28:18.660 --> 28:25.840]  Or, I cannot go to the meeting tonight because I have an appointment, but that's no problem because I can go next week.
[28:26.020 --> 28:29.020]  And I will just meet the meeting this week.
[28:29.020 --> 28:33.980]  Weird dates like first full moon after the third Friday will never work.
[28:34.820 --> 28:39.080]  And anything like every other week won't work either.
[28:39.360 --> 28:42.300]  Um, because people will just don't know.
[28:42.300 --> 28:45.240]  Is it this week, the meeting week?
[28:45.280 --> 28:46.560]  Or is it next week?
[28:46.760 --> 28:49.900]  And what with months that have like five weeks in it?
[28:50.900 --> 28:52.800]  Just meet once a week.
[28:54.000 --> 28:55.400]  Meet on Tuesdays.
[28:55.400 --> 28:57.500]  Because every week day sucks.
[28:57.760 --> 29:01.620]  You will not find any day when every hacker can attend a meeting.
[29:01.900 --> 29:04.140]  Someone always has an appointment.
[29:05.180 --> 29:09.360]  So, the solution we found for that was meet on Tuesdays.
[29:10.280 --> 29:12.220]  All days are equally bad.
[29:12.660 --> 29:13.420]  Just pick Tuesday.
[29:13.740 --> 29:14.320]  End of discussion.
[29:16.560 --> 29:18.460]  We can really meet on Tuesdays.
[29:18.620 --> 29:18.840]  Yeah.
[29:19.520 --> 29:19.720]  Yeah.
[29:21.260 --> 29:25.540]  Um, actually that comes from the history of the Chaos Computer Club.
[29:26.040 --> 29:37.200]  When the Chaos Computer Club was founded, it started with a little ad in an alternative daily newspaper, where someone put up an ad saying, uh, hackers want it.
[29:37.460 --> 29:44.200]  And they met at that, um, office of that alternative newspaper, Die Tageszeitung.
[29:44.560 --> 29:51.080]  And the only day that was, um, available for a meeting of hackers in the 19...
[29:51.080 --> 29:53.080]  Well, in 1980, imagine that.
[29:53.320 --> 29:57.760]  Um, the only day that was available for them was the Tuesday.
[29:57.760 --> 30:00.920]  It was Tuesday, so they met on Tuesday.
[30:01.160 --> 30:03.040]  And Tuesday is just a perfect day.
[30:03.200 --> 30:05.980]  Someone will say, Oh, I cannot possibly come on Tuesday.
[30:06.120 --> 30:07.560]  I have this class on Tuesday.
[30:08.800 --> 30:09.280]  Yeah.
[30:10.380 --> 30:13.180]  But this is true for every other day in the week, too.
[30:13.820 --> 30:18.740]  Um, and, uh, also this may change in a few months.
[30:19.060 --> 30:20.080]  Um, yeah.
[30:20.300 --> 30:23.820]  Maybe that person doesn't have that class on Tuesday anymore.
[30:23.820 --> 30:26.620]  And then another person will have a problem with it Tuesday.
[30:26.620 --> 30:28.580]  But just stay with it.
[30:28.700 --> 30:29.380]  It's easier.
[30:30.620 --> 30:33.800]  And you will spare yourself a lot of, uh, needless discussions.
[30:36.890 --> 30:37.570]  Oh, yeah.
[30:38.470 --> 30:44.590]  Um, one thing that we do at our Hackerspace is, um, uh, an event called Open Chaos.
[30:45.350 --> 30:50.870]  And, uh, we mainly do that to draw in new people and provide an interface to the outside world.
[30:51.150 --> 30:58.430]  We have a monthly public and open lecture talk or workshop, uh, which we announce on our website.
[30:58.830 --> 31:00.810]  And there's always interesting topics.
[31:01.070 --> 31:06.970]  Sometimes it's about, uh, privacy laws, uh, or someone would talk about computer security stuff.
[31:07.910 --> 31:09.250]  Uh, what do you have?
[31:09.530 --> 31:16.050]  Uh, I think the last talk we had was on EEPC hacking.
[31:16.050 --> 31:24.910]  And the talk before that was on NYC resistor, um, by a guest from the United States.
[31:25.590 --> 31:30.190]  And, um, we also use that as a filter for bringing in new people to the group.
[31:30.190 --> 31:32.570]  We used to have very open meetings.
[31:32.830 --> 31:38.330]  And we just would just announce on our website that our internal meetings are every Tuesday.
[31:39.150 --> 31:46.410]  And, uh, then we would get a bunch of weirdos, people with this glow in their eyes.
[31:46.470 --> 31:55.790]  And they would say things like, if we team up, like the CCC and myself, then we can really defeat the Illuminati.
[31:55.790 --> 31:56.830]  And, um,
[32:00.290 --> 32:02.490]  yeah, didn't work out that well.
[32:02.730 --> 32:11.010]  So, we have this open lecture every month where we can, one can come, being a weirdo or not.
[32:11.310 --> 32:14.390]  Um, and we just scout for interesting people.
[32:14.690 --> 32:21.390]  And, um, if you think they are cool people, we just tell them, hey, you should come on Tuesday as well.
[32:21.390 --> 32:22.890]  Um, and we don't tell the weirdos.
[32:26.230 --> 32:35.390]  Um, another thing that we do, um, and which will happen, um, in a few months, is, uh, what we call U23.
[32:36.170 --> 32:45.050]  Um, uh, in Germany, this, um, soccer championships have this, uh, I think there's a U21 team.
[32:45.050 --> 32:49.710]  So, everyone younger than 21, and we thought 23 was a better number.
[32:50.290 --> 32:53.950]  Um, we wanted to draw in younger people.
[32:54.270 --> 33:05.830]  Because, uh, the obvious problem you have after some years is, uh, all the members graduate from college, or get another job in a different city, or get married, um, basically your space just needs fresh blood.
[33:05.830 --> 33:16.650]  What we do to solve that problem is, we have a challenge for younger people that we set up for them, and in form of course, uh, that spent several weeks.
[33:17.290 --> 33:22.130]  Uh, the first one we did was actually building robots with LEGO Mindstorms.
[33:22.310 --> 33:31.090]  Um, building a robot that would read in a, uh, barcode, and then perform actions, uh, on, on that barcode.
[33:31.090 --> 33:42.150]  And then we also had a software project, uh, which was, um, write a chat protocol, implement a chat protocol that would be hidden in ICMP packets.
[33:42.430 --> 33:48.870]  So, um, the sysadmin at your school wouldn't see that you are using the network for chatting.
[33:49.270 --> 34:04.470]  Um, and we tend to make that challenges a bit harder than, uh, it could be, uh, uh, then it, it would be wise for a single person, because we actually want the people to work in teams.
[34:05.050 --> 34:13.990]  We provide tutoring, and we, we push them in the right direction as well, and we do, uh, a reference implementation of the project before that.
[34:14.550 --> 34:26.890]  But, um, it's usually too hard for someone, um, who's just in high school to, yeah, do, like, uh, unique system programming on the network level for a chat server.
[34:26.890 --> 34:31.350]  So, uh, but, uh, but working in a group, uh, would work very well.
[34:31.510 --> 34:47.010]  And, uh, the result that we had with that was that all these poses and people talking big, um, would vanish after week two, because they found out that they actually had to work on something, that they actually had to do teamwork.
[34:47.550 --> 34:54.270]  And then, um, we were left with the really smartest kids, um, that finished the project.
[34:54.610 --> 34:57.330]  It's not a problem if they don't finish the project.
[34:57.870 --> 35:01.170]  The, the thing is just that they learn something in that.
[35:01.690 --> 35:04.550]  And, um, we should give them room to experiment.
[35:04.810 --> 35:11.370]  And after that, you can retire after the team building and let the smartest of the young ones run the space.
[35:11.370 --> 35:13.430]  And it's actually what we do in Cologne.
[35:13.770 --> 35:19.130]  Um, I mean, I go there regularly to, to have a Club-Mate or hack on projects.
[35:19.350 --> 35:24.370]  But, uh, yeah, I mean, just the, the young ones, they run it, actually.
[35:24.790 --> 35:26.310]  And, uh, I'm glad for that.
[35:28.790 --> 35:34.490]  But this is, um, a problem that comes in after some years.
[35:34.670 --> 35:40.650]  If you, if you're building a hackerspace now, you may not see it, but you will see it in the near future.
[35:41.510 --> 35:43.350]  Um, you did everything right.
[35:43.370 --> 35:47.430]  And you had some big events, like maybe a con at your hackerspace or at your town.
[35:47.750 --> 35:49.450]  And you had a nice time.
[35:49.630 --> 35:50.510]  You did projects.
[35:50.530 --> 35:52.970]  But after some time, the enthusiasm goes away.
[35:53.110 --> 35:54.510]  And your projects are stagnating.
[35:55.510 --> 35:59.670]  This will eventually happen without exception.
[36:00.210 --> 36:04.110]  And, um, we've actually found a pattern for that.
[36:04.810 --> 36:12.650]  Um, we think that peak enthusiasm at hackerspace has the form of a sine curve with a cycle duration of four years.
[36:12.950 --> 36:19.470]  So, like, um, at first, everyone is really, really energetic about everything.
[36:19.470 --> 36:21.730]  And then it will slowly go down.
[36:22.490 --> 36:23.970]  And then, um, yeah.
[36:24.230 --> 36:27.070]  After four years, amazing things will happen again.
[36:27.550 --> 36:33.690]  But you should remember to keep your hackerspace running, even if the feel-good factor is temporarily on holiday.
[36:34.310 --> 36:39.270]  And chances are good that your space will be awesome again in two years or so.
[36:39.270 --> 36:40.550]  You shouldn't give up.
[36:41.270 --> 36:44.590]  And, uh, always prepare for the unexpected.
[36:44.930 --> 36:48.250]  Maybe a new exciting member will knock on your door tomorrow.
[36:48.510 --> 36:58.470]  And, um, this actually happened at a space in Bochum where a lot of people who were much into computer security and into programming were running the space.
[36:58.470 --> 37:05.010]  And then, at some point, someone asked them, hey, do you do electronics as well, soldering and stuff?
[37:05.210 --> 37:11.970]  And they said, no, we were just coding away and, uh, trying to find bugs in, in, in security things.
[37:12.330 --> 37:17.430]  And he said, well, I could teach you how to, how to solder and how to build electronic projects.
[37:17.430 --> 37:25.430]  And, um, that totally transformed that hackerspace, uh, Das Labor in Bochum, uh, which is now full of blinking things.
[37:25.810 --> 37:34.010]  And, um, yeah, basically they do nothing else but, uh, microcontroller programming and building projects with electronics.
[37:34.430 --> 37:52.510]  So, even if you didn't have that idea in mind and you always thought of your hackerspace as having, you know, uh, a stress on that aspect of hacker culture, things may change in the future and, um, yeah, chances are good that they will change for the better.
[37:52.790 --> 37:58.550]  Even if at the moment, um, you don't have, uh, that enthusiasm that you used to have.
[38:01.430 --> 38:05.870]  Um, conflict resolution is a very important problem.
[38:06.310 --> 38:12.290]  Um, I've seen a lot of drama at a lot of hackerspaces and a lot of screaming and yelling.
[38:12.910 --> 38:20.070]  Um, I know that many people find these catalog of design patterns impressive.
[38:20.390 --> 38:23.890]  But actually it's not that impressive if you look at the stories behind it.
[38:24.090 --> 38:29.330]  Because, uh, we did every stupid mistake, uh, we could.
[38:29.790 --> 38:33.210]  And then we wrote, just wrote down what, what worked for us.
[38:33.530 --> 38:37.530]  Uh, so you don't have to do all the stupid mistakes that we did.
[38:37.530 --> 38:43.330]  Um, so keep that in mind if you think, wow, how did they come up with that?
[38:43.590 --> 38:45.890]  It's, um, it's because we were stupid.
[38:47.730 --> 38:56.610]  Um, one thing of how to resolve consents, uh, how to resolve problems at your hackerspace would go for consensus.
[38:56.630 --> 39:04.970]  If you, uh, need to make a group decision and want to make sure that no one gets left behind, you use that weekly plenum for discussions.
[39:05.490 --> 39:08.710]  And you shouldn't take votes, discuss until everyone agrees.
[39:09.110 --> 39:12.030]  And we think for some problems this pattern is the best.
[39:15.970 --> 39:18.210]  Second best maybe is democracy.
[39:18.910 --> 39:20.830]  You need to make a group decision.
[39:21.130 --> 39:23.670]  Discussion does not seem to lead you anywhere.
[39:24.870 --> 39:32.450]  Again, a typical example is, uh, should our hackerspace be smoke-free or should we have exceptions?
[39:32.450 --> 39:35.870]  Uh, everyone has a strong opinion upon, on that.
[39:36.070 --> 39:37.790]  And you cannot really find a consensus.
[39:38.130 --> 39:41.590]  But you can see what the majority of the group thinks.
[39:42.370 --> 39:45.170]  Um, you should use the weekly plenum for discussion.
[39:45.450 --> 39:54.410]  And if you see, okay, this can only be resolved through plain old democracy, then the strongest minority wins over the weaker minorities.
[39:54.550 --> 39:57.550]  And for some problems, this pattern is the best.
[39:59.510 --> 40:02.590]  And last but not least, the command pattern.
[40:02.910 --> 40:08.230]  The problem you have is nobody does the dishes, your hackerspace looks crappy, no one seems to care.
[40:08.670 --> 40:12.950]  Then you should implement this conflict resolution pattern.
[40:13.310 --> 40:19.430]  You should order people to do the dishes, take out the trash, keep the infrastructure up and running, yell if necessary.
[40:19.850 --> 40:21.270]  But you should always participate.
[40:22.210 --> 40:27.610]  Just, you know, screaming and, uh, ordering people won't help you, but you should participate.
[40:27.950 --> 40:30.350]  For some problems, this pattern is the best.
[40:30.490 --> 40:32.770]  You see, they all contradict each other.
[40:33.390 --> 40:38.440]  And, um, you will have to experiment which pattern to apply to what situation.
[40:41.730 --> 40:53.890]  This is a name that I stole from a, uh, hackerspace, uh, which is currently not in existence, but in planning state, um, noise bridge in San Francisco.
[40:54.230 --> 40:59.230]  On their mailing list, they had, uh, the very, very nice word, pseudo leadership.
[40:59.970 --> 41:04.430]  And, um, because I think good ideas deserve to be stolen and stole it.
[41:04.430 --> 41:21.250]  Um, the problem that you may, may run into if, especially if you have, uh, this strong personality pattern implemented, you have a community of like-minded people, or you started out as that, but suddenly you find yourself in a dictatorship run by a single hacker.
[41:22.150 --> 41:29.850]  Um, this is not what, what happened at noise bridge, of course, but, uh, they were thinking about how to prevent such a situation.
[41:29.850 --> 41:34.890]  Um, and they came up with that very, very clever name, pseudo leadership.
[41:35.650 --> 41:37.850]  Um, you should not have ranks.
[41:38.490 --> 41:52.270]  Of course, if you incorporate, um, the organization that wants your hackerspace, you must have theoretically on the paper someone who is head of that organization, or whatever the legal framework in your country is.
[41:52.590 --> 41:56.330]  But, um, you shouldn't pay too much attention to that.
[41:56.330 --> 42:00.210]  You should not have an officer of blah, blah, blah, or whatever.
[42:00.570 --> 42:10.690]  Uh, you should use leadership, leadership just temporarily, like for projects, when someone has to say, okay, we need a van to go to that place now.
[42:10.870 --> 42:12.810]  I want you to drive that van.
[42:13.170 --> 42:17.810]  Uh, but you should not have a single root account on your hackerspace.
[42:19.630 --> 42:20.830]  Self-organize.
[42:21.030 --> 42:21.830]  That's the point.
[42:23.190 --> 42:25.570]  Um, responsibility.
[42:26.950 --> 42:31.470]  Yeah, that's a problem I, I, I see a lot of times.
[42:31.650 --> 42:35.030]  You volunteered for the task of running a critical piece of infrastructure.
[42:35.390 --> 42:37.050]  For instance, the mail server.
[42:37.310 --> 42:39.610]  But you feel the sudden urge to slack.
[42:41.290 --> 42:52.130]  And how to get around that problem is, um, just to remember that just because volunteer work, uh, doesn't get paid, doesn't mean it's less important.
[42:52.130 --> 42:55.990]  Remember that you would directly hurt your friends and the hackerspace.
[42:56.190 --> 43:02.890]  If you let them down, take pride in your volunteer work, it will make you grow stronger as a person and it's satisfying.
[43:03.330 --> 43:06.510]  And you realize that you really cannot do the job anymore.
[43:06.510 --> 43:09.070]  Your last task is to hand it over.
[43:12.310 --> 43:13.190]  Debate culture.
[43:13.730 --> 43:15.750]  You are in the middle of your weekly plenum.
[43:15.990 --> 43:17.890]  Everyone's yelling, nothing gets done.
[43:18.630 --> 43:20.910]  That's a problem as we see very often.
[43:21.230 --> 43:28.370]  And we think that's because many geeks have very poor debate skills, which is the result of years of flame wars on the net.
[43:29.590 --> 43:33.650]  We think you should make people with actual social skills lead the discussions.
[43:34.410 --> 43:41.510]  And, uh, we have found out that those with a background in real life political works, like student council, were best for our groups.
[43:41.510 --> 43:55.490]  And they were used to working with agendas and meeting minutes and having a list of speakers and calling people to order and stuff and moderating the group discussion.
[43:55.670 --> 43:57.630]  And it's actually a skill that you can learn.
[43:57.830 --> 43:59.910]  Just like learning a new programming language.
[44:00.050 --> 44:07.110]  You can learn from people who know how to discuss things and you can learn not to interrupt others.
[44:08.430 --> 44:10.710]  It's worthwhile learning it.
[44:13.890 --> 44:19.930]  Yeah, this is something that may be familiar to FreeBSD hackers.
[44:20.270 --> 44:22.270]  We call it the bike shed anti-pattern.
[44:22.890 --> 44:30.770]  And, um, it sounds complicated, but it's a problem that I'm sure everyone in this room has seen.
[44:30.770 --> 44:44.610]  Um, you suggest creating something for your new hackerspace, like a bike shed, but everybody is now talking about the bike shed's color, and then no bike shed will be built.
[44:45.250 --> 44:47.770]  That's, uh, it's a known problem.
[44:48.270 --> 45:01.410]  If you suggest something that anyone in your hackerspace can build, they will take part in the discussion, especially if it's only the color of the bike shed, the design of the t-shirts, the Linux distribution on the servers, et cetera, et cetera.
[45:01.970 --> 45:07.890]  Nerds tend to discuss trivial problems in epic detail, while more complex tasks will be ignored.
[45:08.250 --> 45:12.630]  And you should just identify pointless discussions like these and end them.
[45:12.930 --> 45:28.730]  For instance, as a hypothetical case, you're discussing uses for a laser at your hackerspace, but the laser is not there already, and you don't have an idea how to finance that.
[45:29.510 --> 45:43.250]  So, maybe going back and saying, okay, I think this discussion is somewhat pointless, if we don't even know how to get that laser yet, um, would be a good idea.
[45:47.350 --> 45:50.850]  So, the bike shed problem actually comes from a book.
[45:51.090 --> 45:54.210]  There's even a website on that problem, bike shed.
[45:54.410 --> 45:56.050]  It comes from a book, Parkinson.
[45:58.030 --> 46:07.050]  He wrote a book in the early 1960s called Parkinson Laws, which contains insight into the dynamics of management.
[46:07.250 --> 46:13.870]  In this specific example involving the bike shed, the other vital component was an atomic power plant.
[46:13.870 --> 46:16.010]  I guess that illustrates the age of the book.
[46:16.350 --> 46:26.490]  Parkinson shows how you can go into the board of directors and get approval for building a multi-million or even billion dollar atomic power plant.
[46:26.650 --> 46:30.550]  But if you want to build a bike shed, you will be tangled up in endless discussion.
[46:30.750 --> 46:39.290]  And everyone wants to leave their, uh, their fingerprint on it and said, you know, the color of that I chose.
[46:39.290 --> 46:50.730]  But if you propose something really complex and something really huge, like this atomic power plant, people would just go along and say, yeah, I don't know much about that.
[46:50.990 --> 46:56.530]  I guess they thought about it earlier, so I shouldn't say anything about that.
[47:00.310 --> 47:03.750]  Sometimes people cause a problem that cannot be resolved in the groups.
[47:03.950 --> 47:05.390]  People are just causing troubles.
[47:06.930 --> 47:23.790]  We call this the private talk pattern, which we found very effective if some experienced member of the group would talk to the troublemaker in private and listen to that person and let them know how the group feels about the problem without exposing them in front of the group.
[47:24.110 --> 47:32.530]  This is actually, um, something that you could do to prevent drama and flame fests on your mailing list.
[47:32.810 --> 47:34.750]  Just talk to the person in private.
[47:38.050 --> 47:41.290]  So then we have some miscellaneous patterns.
[47:42.330 --> 47:43.750]  Um, old hardware.
[47:44.730 --> 47:54.130]  People always bring in new, uh, new hardware, but, um, yeah, at some point, your, um, hackerspace just becomes a hardware museum filled with junk.
[47:54.350 --> 48:00.990]  You should, uh, create a pile or stack where you put old, unused hardware, let everyone take from that.
[48:01.450 --> 48:11.130]  Anything left after a month should be thrown away, but you should make sure you announce that step not only once, but at least three times, using an escalation system.
[48:11.390 --> 48:15.030]  And being Germans, we put that into a law.
[48:15.030 --> 48:19.250]  Uh, uh, it's in German.
[48:19.470 --> 48:21.670]  I'm sorry, but I will translate it.
[48:21.830 --> 48:26.390]  Um, so that's the law about, uh, providing hardware in the Chaos Lab.
[48:26.710 --> 48:40.650]  The Chaos Lab is a, um, environment of extraordinary order and, uh, tidiness, uh, where the Chaos Computer Club Cologne, uh, does, uh, their work.
[48:41.370 --> 48:50.250]  Um, we define cleaning up personnel as person, uh, who, um, care about the state of the club room.
[48:50.890 --> 49:05.090]  And, um, cleaning up personnel always, um, has, uh, hero status and immunity against, uh, hostile attacks of, uh, owners of not-functional hardware.
[49:05.890 --> 49:07.190]  Et cetera, et cetera.
[49:08.830 --> 49:10.210]  It goes on a while.
[49:11.070 --> 49:14.290]  Um, so this is our stack of old hardware we have.
[49:14.470 --> 49:23.550]  If you need a monitor, um, you could just grab one, um, and, um, after some time, we just throw them out.
[49:24.470 --> 49:42.430]  We define non-functional hardware as every hardware where we don't know what function it has, where there's no contact address, uh, printed on it, uh, where there's no root password known, uh, where the, where we possibly couldn't imagine any use for that.
[49:42.430 --> 49:55.670]  And, um, also, if it's, like, uh, just, uh, collecting dust in the corner, um, and has not been switched on in, like, two months, it may be considered as non-functional.
[49:56.070 --> 50:08.570]  And we have to be that strict because it's, yeah, you will turn your hackerspace into a hardware museum really, really quickly if you don't take that extreme measurements.
[50:09.910 --> 50:11.310]  Um, keys.
[50:11.310 --> 50:14.310]  You want to have your hackerspace accessible all the time.
[50:14.470 --> 50:18.530]  You don't want to call someone else during the night to lock the hackerspace when you leave.
[50:19.830 --> 50:29.590]  The solution for that is hand out keys, track who owns a key, make a list, have a good lock so that nobody can copy the key without your permission.
[50:29.910 --> 50:35.510]  Well, it depends on where you live, but, um, at least we have that in Germany.
[50:35.770 --> 50:40.310]  And you should collect a deposit for the key so that the owner takes care of it.
[50:41.230 --> 50:47.350]  Or you could also build a complicated electronic locking system with cards and RFIDs.
[50:47.490 --> 50:52.150]  And, yeah, then you will have all the cool benefits and all the messy problems that come with that.
[50:52.250 --> 50:57.010]  But we think that just plain old hardware keys work the best.
[50:57.010 --> 51:03.290]  Um, and, yeah, you want to raise funds, you want to stay up longer at night.
[51:03.530 --> 51:09.190]  This is a problem that you can solve with buying at least one pallet of Club-Mate and selling it in your hackerspace.
[51:09.390 --> 51:12.350]  And you will realize the results very soon.
[51:12.550 --> 51:16.070]  This is, uh, uh, some of the Marte we keep in our hackerspace.
[51:20.300 --> 51:24.140]  Let me just stress this, that this is not a step-by-step manual.
[51:24.460 --> 51:33.240]  There's more than one way to build your hackerspace, and based on your background, there may be a couple of patterns which match, and some patterns even contradict each other.
[51:33.240 --> 51:42.640]  You should be creative, you should experiment, and, uh, above all, you should start your own hackerspace or go to your nearest hackerspace.
[51:42.980 --> 51:52.320]  Um, this is a very, very incomplete list of hackerspaces that, um, I've seen just before that conference.
[51:52.540 --> 52:11.120]  My friend, uh, Paul Boehm, Enke, from Vienna, started, uh, hackerspaces.org, which is going to be a, uh, starting point for, yeah, organizing hackerspaces worldwide, uh, which will have a huge list of hackerspaces around the world.
[52:11.340 --> 52:12.320]  Thank you very much.
[52:22.700 --> 52:27.020]  Do we have time for questions, or I already took too much time, right?
[52:27.720 --> 52:30.220]  Okay, uh, then just a short announcement.
[52:30.860 --> 52:42.600]  I think tomorrow at 3 p.m., um, there will be a workshop down there, uh, down the, um, down the elevator, um, and that area which is the hackerspace village.
[52:42.940 --> 52:50.000]  And if you have any specific questions, um, you should just go there and find me, and, um, we can talk about that.
[52:50.160 --> 52:50.760]  Thank you very much.
[52:51.220 --> 52:51.540]  Thanks very much.
[52:51.560 --> 52:51.820]  Thank you.