 Well, thanks, everyone, for coming on so early on day three. I got two and a half hours of sleep myself, so I'm totally ready to go. And the design patterns, I think, are super important for why we're even all here. The movement has been going on for a while, but the hacker space design patterns really did change things dramatically and got so many people aware of this incredible opportunity, hacker spaces, and all of our hacker conferences like here. So I have a lot of information that I've compiled, and I can't really go over much of it, so I want to really just put everything in context of why the original hacker space design patterns are so important, and some ideas of how to compile a new set that includes the original, because the original really are superb. They are still relevant and vital. So I have to look at my notes, I'm afraid, because my brain's a little broken, so forgive me. But, you know, I've been waiting for this camp for four years since the last camp, and it's just so amazing here, you know. I've been thinking about this talk for a long time, but I actually wrote it last night at the Knoop Village, that's our noise bridge and pseudo room of San Francisco area hacker space village, and most of the camp I've either been doing workshops or wandering around and meeting amazing people, but if you just sit there, it's incredible the kind of people that just come up to you. I wasn't really prepared for that because I was supposed to write my talk, but, you know, like a friend comes by who's now an employee of the pirate party and starts talking about copyright issues, and there's an acquaintance who comes by who I've met a number of years ago who's now been spending the last year of his life writing a really trippy, cool game you can play on your phone, someone else comes over and talks about, and we talk about, you know, encoding and decoding transmissions, receptions with an incredible radio badge, how about that badge, and then funding sources for our projects and how they matter, how to promote open science, secure password managers, filmmaking, I mean, and these are just a few of the things that we talked about, which kept me up till 5.30 in the morning, and of course that meant we were all talking about the merits of sleep. So anyways, this is our community, and, you know, my first hacker conference was in 2006. That's getting to be a number of years now. You know, the turning point for me, though, is the following year at CCC camp, you know, where we are now. Just amazing. More LEDs than China. But, you know, this community comes together and creates this. It's just totally amazing. You know, in 2007, though, there were a bunch of North Americans who came to camp, camp 2007, and we were visiting some hacker spaces. We really wanted to learn about hacker spaces, because all of us had experienced how wonderful it is to be in an amazing community at hacker conferences, but we really didn't have hacker spaces to go to and check out in North America. So we met a bunch of German hackers at hacker spaces, three of whom from C4 and Clone, they agreed to put together a presentation for not only us, but everyone to learn from, and they researched what worked well and also what didn't work well at all the hacker spaces they could talk to people at, and then most of them were in Germany, of course, including a lot of information from CCC and Clone. So they presented it at 24C3. It was called Building a Hacker Space, but it was presented as patterns. They called it the Hacker Space Design Patterns, and within several months of this talk, we had several hacker spaces in North America, including Noisebridge, the one I co-founded. And within a year later after that, with new examples, plus all the German ones and these patterns to draw from, there were over 100 a year later. We had the idea driven by someone from MetaLab in Vienna to create hackerspaces.org, a networking place where people from hacker spaces and people thinking of starting hacker spaces and running hacker spaces could all help each other, could all network, and people could list themselves. It's a wiki, and within not all that many years, we have over 2,000 hacker spaces listed on hackerspaces.org, which is also directly a result of the original Hacker Space Design Patterns. My first hacker conference was in New York Hope 6, which I'm now helping, Hope Conference is helping organize, because I just fell in love with all of this. But back then, I'd never heard of Hacker Spaces. Before, I heard about Hope. I never even heard of Hacker Conferences. I had no idea what to expect. I was kind of nervous. I was going to give a talk, and I know I'm an introverted geek, and what do you expect to go to this large group full of people you don't know, and giving a talk, and they're all staring at you, and you're on the stage? But it turned out to be 2,000 introverted geeks. It was incredibly cool, and I felt wonderful and safe and fantastic in a group of people for the first time in my life. It's because of the community that they formed, that we formed. It really is what we're creating, a wonderful community of geeks. So one of the focuses for me, it really is community. It really is very important for us, for all of us, geeks or not. We all need community in our lives. That's why we're here rather than just at home on the internet. So as a species, we no longer need community to survive as we once did long ago, but we still need community to feel like our lives are important, to feel like we're part of something bigger than ourselves. And with Hacker Spaces, even with all the cool blinky lights and projects and tools, it's the community that brings people together, rather than just sitting at home alone typing on your keyboard or holding a soldering iron or a sewing machine. But you know, as it turns out, not necessarily all well suited for community, because we're not so well trained. So community is hard work. Maybe it always has been. The Hacker Space design patterns are a fantastic set of patterns that we can look at and ponder and draw from to help us in our journeys with interfacing with community and forming community and hopefully growing community. And even though they were written eight years ago, and there were only a small number of Hacker Spaces back then, they really are still very relevant. If you haven't read them, please do just look at them. You'll find them. They're pretty amazing. They're very important, and if you have read them, reread them. I was actually surprised rereading them, preparing for this talk over the last three weeks, how relevant they are, how interesting and insightful they are. So I don't have time to go over, obviously, the whole original design patterns, but I want to give you a few of them so you get a feel for how the design patterns work and have a taste of it. This is just one I thought was pretty interesting. How do you start? Do you start with this or do you start with that? Do you start with a building and hope people come? Do you just have a cool project and then grow it into a community that you then find a space? They recommended what I've seen at the Hacker Spaces I've visited. And by the way, I travel the world giving talks and workshops, usually with soldering for the workshops and teaching people for all ages, this cool stuff, doing what I love and doing it mostly at Hacker Spaces. But in all the Hacker Spaces I've visited, most of them have started by working on the infrastructure, creating just enough organization and infrastructure walls, spaces, whatever, some tools that people could come together and grow their community in whatever surprising ways their community would grow. This other one I thought is pretty interesting named after Grace Hopper. She's one of the early computer programmers. She was worked her way up in World War Two. When do you start a Hacker Space? There's always problems that you need to solve before you can really do the thing before you can start any project, right? If you're doing art, if you're doing a computer program, how much do you architect before you actually start? The recommendation of the Hacker Space design patterns and what was worked really well for so many Hacker Spaces around the world is you just do it. Don't wait. If you try to solve all the problems before they happen, you'll never start. So this has led to a couple of things that I've seen at not only Noisebridge, but Hacker Spaces around the world. One of the outgrows of this is, you know, there's a couple of rules of thumb. So one of them is don't solve problems that haven't happened. You just get bogged down in endless, useless discussions. And what I've seen at Noisebridge and other Hacker Spaces is when that starts happening, someone just says, let's not solve problems before they happen. And then, oh, it's like, oh yeah, and then we move on. Another one is duocracy. Have you all heard of duocracy? Yeah? So duocracy is just do it. Don't ask permission. Grace Hopper is famous for a number of quotes. One of them is it's better to ask for forgiveness rather than permission. So just do it. But of course, follow the one rule of Noisebridge and signs we've seen all over here be excellent to each other as you do it. If you think there are objections, obviously you don't want to go ahead. Another one that I think is great. Well, there's one called the plenum pattern which talked about the importance of weekly meetings. And that's the way people come together and discuss issues of importance and make decisions and solve problems. The pattern that followed this is, well, what day of the week do you choose for this meeting? And I like the first line every weekday sucks. And it's true. If we're starting an organization, a community, a hacker space, we're busy. We have stuff happening in our lives, cool things happening in our lives. And we're busy. There's no way you're going to pick a day of the week that works for everyone. So just pick Tuesday and get it over with. And that's what we did. At Noisebridge, we did this and we grew rather quickly before we had a space to up to 50 people every Tuesday meeting. But it was very problematic because some people had to get off early because they had Chinese lessons online with someone in China and other people couldn't come till late and various other reasons why it's problematic like every day of the week is. So we decided to focus for three weeks on how to choose the best day of the week. So some people who thought this was important researched it and everyone in the group picked their number one, number two, and number three best day of the week. And we come up with an algorithm, one person came up with an algorithm and put all the data in and it came out and the best day of the week was Tuesday. So why go through the pain? Learn from others' experience. You know, there are also anti-patterns in the Hacker Space Design patterns. This one is really relevant. If you have a space and warm community that's friendly and open and inviting, people are going to come who don't necessarily belong. How do you choose that or not is open for discussion and it's a really important discussion. But some people will start to abuse the space and using the resources without contributing in significant enough ways. It's a shared resource. We have to be aware of other people. If you sleep in a space, you're not just taking up this area that you're sleeping in. People are very aware perhaps subconsciously that you're there and maybe that person isn't necessarily bathing as well as they could. So it's taking up a lot of psychic space. And at Noisebridge, this is one of the many problems that led up to about a year ago of Noisebridge almost dissolving as some people who don't belong sleeping in our space. I'm going to talk more about that in a bit. One of the main things with design patterns rather than saying what you should and shouldn't do, all Hacker Spaces are different and unique. So it's really not a cookbook to say follow these simple steps, but patterns, rules of thumb, things to think about to ponder. This is what's worked well and not well at these other spaces. So what do you want to do at your space? Learn from the experience of others and if you violate or do it differently than what the patterns show, do so consciously. It's totally okay, but do so consciously. For instance, a long time ago, one of the earlier Hacker Spaces is Tempilab, just outside of Paris in a suburb, which was not very friendly, kind of high crime. And they decided that one of the people would live there to have a living presence there and knowing full well about the patterns and that worked really well for them. Also, for instance, here's a pattern that is now sometimes an anti-pattern depending on the space. We need food. It's wonderful to bond together while eating food. At so many of the Hacker Spaces I've been to around the world, I've had fantastic experiences meeting people and having great conversations over food, great food that everyone could eat. But at Noisebridge and many other spaces, it's definitely an anti-pattern. We have a grocery store in the first floor of our building. There are rats. They migrated to our space because it was a friendlier environment for them. It also became a place where a lot of people who weren't really part of our community were hanging out in the kitchen, just use the kitchen and then leaving or hanging out with each other and not really being open to people who are part of the community joining in conversations and people got kind of uncomfortable and things got messier and messier just, you know, like that. And rats, groaches, we ended up last year choosing to close our kitchen, which saddens me, but I think it was the right choice for us. There's a lot of patterns that are really, really relevant. They cover many topics, including sustainability, funding, conflict resolution and others. But that gives you a taste of what the patterns are like. You give up a problem and some solutions, implementation ideas. Now, with many, many more hacker spaces in the world, way more and eight more years of collective experience, I think we can add to these patterns so that other people starting hacker spaces and running hacker spaces can benefit from this. Now, so to prepare for this talk, I put the word out. I didn't want to just come up with these patterns myself. I have a lot of experience traveling around and visiting hacker spaces, but I wanted to be collective input from as many people as possible. So I put out the word on hacker space, email lists, many of them. I put it on the hackerspaces.org email list, and I was deluged with a lot of suggestions, really, really good ones. Some of them are very specific to a particular space. Some of them are really good for a subset of hacker spaces. What I wanted to initially do was create patterns that are good universally, somehow distilling what's universal out of these ideas, and presenting ones that are universal for everywhere in the world, hacker spaces. I think we can do that. But I also would like to create ones that are good for subsets of hacker spaces, like urban ones, or ones in decaying industrial urban areas, or whatever, whatever we do. So I actually, though, got 81 small-type pages of raw notes from people. And I'm still getting, even today, I got some more ideas, people sending me ideas. So clearly, people are thinking about this. People think it's important. So let's bring our ideas together and make some hacker space design patterns 2.0. The topics range quite broad. Many of the ones in the original design patterns, but some new ones too. So we have funding, people who are toxic to community, keeping people motivated, group organization, conflict resolution, how to deal with physical stuff that accumulates. So many different important topics. I can't go over all of them now. But I want to point out just a few that I think are interesting. These aren't really all fleshed out yet, but they're really good ideas for making them real. The mentor pattern is for bringing new people on. So as they come in, they know what your community is about and what it's not about. And they feel welcomed. And they can be almost from the get-go and integral part of the community and grow together. And maybe that was created because of the mentoring program that started a few years ago at chaos congress. And it's been working really well there. This is when we came up with noise bridge after we actually, for the time being anyways, solved our serious problems. We call it the cultural immune system pattern. So if your body, a living organism, and our communities can be considered living organisms, they take on a life of their own more than the sum of the parts. If we can, like our bodies, deal with invading elements that don't fit well and also attract what is healthy, then we're healthier. The community, it's the same thing. So there's many ways to go about that. With noise bridge, one of the main problems is people who don't belong. So we talked about how to define that for ourselves. And we came up with some good guidelines for that. And also, taking off on the mentor one, we have greeters. Everyone who comes in is greeted. A greeter, it takes full responsibility for that person, shows them noise bridge, how cool it is, what noise bridge is and is not about, and empowers them to become part of the community and do what they think is awesome in our space. And the greeter also kicks out people who are not working. So the reboot pattern, this is also from noise bridge, I don't want to make this noise bridge centric, but I think these patterns that I'm talking about from noise bridge apply universally to all community, whether it's hacker spaces or not. If your operating system isn't working too well, your computer is not working too well, you turn it off and on again and it solves a lot of problems quite often. So that's what we did with our space. There were people sleeping there, there were people stealing stuff, there were everyone taking no care of the tools, they were mostly all broken, if you wanted to do anything there, you had to clean up for 45 minutes. And people drifted away, people who don't belong kept coming and we really seriously considered giving up. But we had the idea of shutting up space down, only allowing people who are fixing the place up to come in, it attracted new people, it attracted old people, everyone again felt part of creating the space that they want to be in, it was super high. And when we reopened, we made, we had a party. And it was really fun. We had not more LEDs than China, but we had a lot of LEDs and lasers and a lot of cool projects from all sorts of people in the community. And we made sure that the people who are toxic to our community stayed out. And we actually, painfully, had to kick some people within the community out, because they were becoming disruptive. Community really isn't easy, but it's way rewarding and worth the effort we put in. I just want to briefly show what noise bridge was like before the reboot. And during the reboot. Kind of night and day, huh? And we invited artists in after we painted all the walls white, and we have a mural of Tesla. And all these other beautiful murals on a wall. And now it's a thriving, really positive community that I'm super excited to see what's happening every time I come home. So again, that's just a little taste of what I've compiled. I would love to have this as the beginning of a discussion that we can have a living document, the hacker space design patterns that keep, we keep adding to so that our communities are healthy. Yeah, so there's great diversity in our hacker spaces, and all around the world. Yeah, I really do think we can distill some universal patterns to ponder. And like I said, ones that are good for subsets. So I'd love to start that conversation at a workshop following this talk for anyone who's interested. I have a slide for that later. The world really does need hacker spaces. We need to create, and we need community and hacker spaces brings this brings this together, and makes it available these opportunities for everyone in this room, we probably all have this opportunity or most of us anyways, many of us have probably even started hacker spaces. So we have to make more, I think, not every one of us. But if we can help other people who want to start more, then maybe some percentage, ideally all 7 billion people in the world have this opportunity that we have. I don't know what'll happen, but I think it's worth a try to help let this grow even further. So this is where the, just the flyers I put up around about anyone interested coming to Nope, Norton's obscure foggy embassy, foggy with a pH, and we do have a fog machine like San Francisco. Please come if you want to talk about this. And if we run out of space, we can go to a bigger one. Also, it's pretty much related. Hacker spaces.org website has been somewhat neglected over the years, and there's things that are obsolete on it. I still think it's a fantastic resource. If we put some energy into it, that can be way better into the future. So I'm having a talk about that at Nope, Norton's obscure foggy embassy on Sunday at 7 o'clock. So that's all I had to say. If you ever want to contact me at camp, there's irrelevant information. If you want to contact me anytime, anywhere for any reason, that's the relevant information. So thanks everyone for being here at such an unbearably early time on day three. Thank you very much. You're very welcome for the presentation. So we'll have like two more minutes for Q&A. So if anyone wants to ask something or to state something, please line up with with the microphones at the right at the left, my right and left. And afterwards, we'll have these three hours discussion. So every question, hopefully in the comment will be cleared. Questions? Everybody seems to be sleeping still. Well, please join for the discussion at Nope, where we can talk in depth. Hey, Mitch, how's it going? I'm really glad to see that hackerspaces.org and the design patterns are getting their own sort of reboot. And it was a great presentation. And I agree with a lot of what you said. One of the things that I'm wondering about myself is, how do we make that specific stuff? Because, you know, as hackers, we like to find like the one ring to rule them all or like the top three principles to how did and, you know, people are squishy and different and all sorts of parts of the world are very different. And the ways that we can support each other and community will look different. And so you were talking about like urban areas and suburban areas. And I'm just wondering if you have any ideas about the different categories that we can use to start identifying some of the general like, well, these are design patterns for in my in my case, I would think like, Oh, the Middle East or like people that live under a dictatorship or people that live in places where people that build stuff terrify the people around them. And but like just wondering what your general categories are, or your thoughts about that? Yeah, thanks. So that's Bilal, he travels around the world helping hackerspaces form everywhere. But he's been focusing on the Middle East. So he knows about that realm very well. And, you know, I don't have necessarily sub categories to suggest at this point. Certainly ones that are like rich urban areas and ones that are poor x industrial areas in North America could be categories. The Middle East has its own set of assets and problems to draw from. But same with other parts of the world, Asia is different. But like I said, I really do think there are some patterns that are really good for all communities, even hackerspaces, including hackerspaces, that can be helpful for people to consider when they're forming community or trying to enhance their community. But yeah, this is what I'd like to start the conversation with and we can start that at nope after this for anyone who's interested, whether you're just curious and want to listen or whether you have burning things you want to share, whatever, just come and let's talk about this and let's take notes and start this for start this while rolling. Okay, I think we'll be having one more question because we're really tight on schedule. Are you okay with coming to the workshop afterwards? Yeah. Okay, thank you. Go ahead. Hi, I was curious if you have any clear idea of like this call to action of having this this conversation, this discussion, talking about going over to nope, I don't know if we should have this discussion on hackerspaces.org mailing list, or if there's a wiki somewhere or like, we can say let's have this discussion but where where are we having it? Right, well, I guess that's up for grabs too. But I wanted to start it at this workshop discussion brainstorming session, whatever to call it at nope. And clearly hackerspaces.org is a great repository for hackerspace design patterns up till now, and I think it can be far into the future. And if there's a few people who can be motivated to get together, myself included, to revitalize hackerspaces.org and keep it current and keep it going. That's a fantastic place for these discussions to happen. You know, it's kind of embarrassing the week leading up to camp, the hackerspaces.org email list was down. That's not okay. Let's let's, you know, have some people who are on top of things who have the time and energy and desire to keep that happening. And then hackerspaces.org would be a great place for that too. So but I would love to see this discussion happen at all of our hackerspaces and people who are forming hackerspaces. And maybe hackerspaces.org is the best place to compile that information and have it grow and spread from there. So that's what I've thought of till now. Okay, thank you very much again. Thanks.