yolo2.0

initial/HeatSync_Community_Standards.md

@@ -1,222 +0,0 @@
-# HeatSync Labs Community Standards & Accountability Process
-
-> **HeatSync Labs exists so people can make things.** These standards protect that mission by ensuring everyone can participate safely. We're a do-ocracy: if you see a problem, you can address it. But some problems need backup. This document tells you when to act, when to escalate, and what happens next.
-
----
-
-## 1. The Core Principle
-
-**Be excellent to each other.**
-
-This means:
-
-1. **Respect people's right to exist and make things here,** regardless of who they are.
-2. **Take care of the space** so others can use it too.
-3. **Handle conflicts directly when you can,** and ask for help when you can't.
-4. **Support the community's ability to enforce its norms,** even when it's uncomfortable.
-
----
-
-## 2. Who This Applies To
-
-Everyone in HeatSync spaces—physical or digital—including members, guests, visitors, board members, and anyone at HSL-sponsored events. No one is exempt.
-
----
-
-## 3. Who We Protect
-
-HeatSync Labs does not tolerate discrimination or harassment based on:
-
-- Race or ethnicity
-- Gender identity or expression
-- Sexual orientation
-- Disability (visible or invisible)
-- Age
-- Religion (or lack thereof)
-- National origin
-- Socioeconomic status
-- Body size or appearance
-- Neurodivergence
-
-*This list is not exhaustive.* If you're being targeted for who you are, that's covered.
-
----
-
-## 4. Behavior That Isn't Tolerated
-
-### 4.1 Immediate Removal Behaviors
-
-These result in immediate removal from the space. No warnings.
-
-1. **Violence or credible threats of violence**
-2. **Sexual harassment or assault**
-3. **Stalking or deliberate intimidation**
-4. **Doxxing** (publishing someone's private information)
-5. **Theft or intentional destruction of property**
-6. **Grossly unsafe tool use** that endangers others
-
-### 4.2 Escalating Behaviors
-
-These may result in warnings, then escalating consequences if they continue.
-
-- Slurs, discriminatory jokes, or derogatory language targeting protected characteristics
-- Unwelcome physical contact (you need consent before touching someone)
-- Sustained disruption of events, meetings, or others' work
-- Refusing to stop behavior when asked
-- Repeated boundary violations after being informed
-- Creating a hostile environment through patterns of microaggressions
-- Retaliation against someone who made a report
-
-### 4.3 Space & Tool Violations
-
-- Using tools you're not certified for
-- Leaving messes for others to clean up
-- Ignoring posted safety procedures
-- Using more space than you need during busy times
-- Taking or using others' property without permission
-
----
-
-## 5. The Do-ocracy Response
-
-> **We're a do-ocracy.** That means you have standing to address problems directly. You don't need permission to say "hey, that's not cool" or "please clean up after yourself." Most issues should be handled this way.
-
-### 5.1 When to Handle It Yourself
-
-- Someone forgot safety glasses → remind them
-- Someone left a mess → ask them to clean it up
-- Someone's being loud during your work → politely ask them to keep it down
-- Someone said something mildly off → call it in ("hey, that came across weird")
-- A tool needs maintenance → fix it if you can, report it if you can't
-
-### 5.2 When to Escalate
-
-- The behavior is in the "Immediate Removal" category
-- You've addressed it directly and it continues
-- You don't feel safe addressing it directly
-- The person becomes hostile when confronted
-- It's a pattern, not a one-time thing
-- You witness something happening to someone else who seems distressed
-
----
-
-## 6. Reporting & Response Process
-
-### 6.1 How to Report
-
-Choose the method that works for you:
-
-- **Email:** conduct@heatsynclabs.org (goes to all board members)
-- **In person:** Any board member or host present at the space
-- **Anonymous:** Drop box at [LOCATION] or anonymous form at [URL]
-- **Direct to specific board member:** If you're not comfortable with full board seeing the report
-
-### 6.2 What Happens Next
-
-| Timeline | Action |
-|----------|--------|
-| **48 hours** | Acknowledgment sent to reporter (unless anonymous) |
-| **7 days** | Initial investigation complete; interim measures if needed |
-| **21 days** | Final decision communicated to all parties |
-
-*Exceptions:* Complex situations may take longer. If so, you'll be told why and given an updated timeline.
-
-### 6.3 Investigation Process
-
-1. **Intake:** At least two board members review the report
-2. **Gathering information:** We talk to the reporter, the respondent, and any witnesses
-3. **Interim measures:** If someone's safety is at risk, we may restrict access during investigation
-4. **Decision:** Board determines what happened and what response is appropriate
-5. **Communication:** Both parties are informed of the outcome
-
-> **Conflict of Interest:** If a board member is involved in the incident (as reporter, respondent, or close relation), they recuse themselves from the process.
-
----
-
-## 7. Consequences
-
-Responses are proportional to the severity and pattern of behavior.
-
-### Tier A: Verbal or Written Warning
-
-For first-time minor violations where the person seems unaware or immediately corrects.
-
-- Documented internally but not announced publicly
-
-### Tier B: Required Action
-
-For repeated minor violations or moderate violations. May include:
-
-- Apology to affected parties
-- Cleaning duty or other community service
-- Temporary restriction from specific areas or tools
-- Required re-certification for safety training
-
-### Tier C: Temporary Suspension
-
-For serious violations or continued problems after warnings. 30-180 days.
-
-- No access to space during suspension
-- Card access revoked
-- Reinstatement may require conditions (e.g., meeting with board)
-
-### Tier D: Permanent Ban
-
-For severe violations or repeated serious problems. Reserved for:
-
-- Violence, sexual assault, stalking, or credible threats
-- Pattern of harassment despite previous consequences
-- Actions that seriously endanger others
-
-> ⚠️ **No waiting for multiple complaints:** The board is not required to wait for a specific number of reports before taking action. A single credible report of serious behavior is sufficient to investigate and act.
-
----
-
-## 8. Appeals
-
-If you believe a decision was unfair, you may appeal.
-
-### 8.1 Grounds for Appeal
-
-- New evidence that wasn't available during the investigation
-- Procedural errors that affected the outcome
-- Consequence is disproportionate to the violation
-
-### 8.2 Appeal Process
-
-- Submit written appeal to conduct@heatsynclabs.org within 14 days of decision
-- Appeal is reviewed by board members not involved in original decision
-- If all board members were involved, appeal goes to membership vote at HYH
-- Decision on appeal is final
-
----
-
-## 9. Confidentiality & Documentation
-
-- Reports are kept confidential to those involved in the investigation
-- The board maintains records of all reports and outcomes
-- Consequences may be shared with the community without naming individuals
-- Deliberately making consequences public when the board chose privacy is itself a violation
-- If the community needs to know for safety reasons, the board will communicate appropriately
-
----
-
-## 10. Amendments
-
-This document may be amended through the standard HSL proposal process. Amendments require a majority vote at HYH followed by board ratification.
-
----
-
-> *The goal isn't punishment—it's a space where people can make things without worrying about being harassed, endangered, or excluded. When we hold each other accountable, we're protecting what makes HeatSync worth having.*
-
----
-
-## Contact
-
-- **Report a concern:** conduct@heatsynclabs.org
-- **General board inquiries:** board@heatsynclabs.org
-- **Physical drop box:** [LOCATION TBD]
-
----
-
-*This document is adapted from the Geek Feminism Anti-Harassment Policy and distributed under CC BY-SA 3.0.*

initial/bylaws.md

@@ -1,131 +0,0 @@
-# **Bylaws of [Hackerspace Name]**
-
-## **Article I: Name, Purpose, and Status**
-
-**Section 1.1: Name.** The name of the organization shall be [Full Legal Name of Hackerspace], doing business as [Hackerspace Name] (hereinafter, the "Corporation").
-
-**Section 1.2: Purpose.** The Corporation is organized exclusively for charitable, educational, and scientific purposes within the meaning of Section 501(c)(3) of the 
-Internal Revenue Code. Its mission is to:
-*   Provide a collaborative physical workspace, tools, and resources for making, learning, exploring, and sharing technology and creative projects.
-*   Promote education in technology, science, art, and craftsmanship through workshops, classes, and public outreach.
-*   Foster a community of innovation and shared knowledge, operating on the principles of open access, inclusivity, and **do-ocracy**.
-
-**Section 1.3: 501(c)(3) Status.** The Corporation shall operate exclusively for its stated charitable purposes. No part of its net earnings shall benefit any private 
-shareholder or individual. The Corporation shall not engage in substantial lobbying or any political campaign activities.
-
----
-
-## **Article II: Membership**
-
-**Section 2.1: Eligibility.** Membership is open to any individual who supports the Corporation’s mission, agrees to abide by its Code of Conduct and Safety Policies, and 
-pays the established dues (if any). The Corporation shall not discriminate on any unlawful basis.
-
-**Section 2.2: Classes of Membership.** The Corporation shall have **Voting Members**.
-*   **Voting Member:** An individual who has completed an orientation, is in good standing (current on dues, if applicable, and adherence to policies), and has actively 
-contributed to the space’s maintenance or projects within the last [e.g., 6 months]. Contribution is self-documented and recognized (see Do-ocracy, Article VI).
-
-**Section 2.3: Rights of Voting Members.** Each Voting Member shall have one vote on matters put before the membership, including the election of the Board of Directors and 
-amendments to these Bylaws.
-
-**Section 2.4: Termination.** Membership may be terminated for cause, including non-payment of dues or violation of the Code of Conduct, upon fair review as defined in the 
-Corporation’s policies.
-
----
-
-## **Article III: Board of Directors**
-
-**Section 3.1: Role and Powers.** The Board of Directors ("Board") is responsible for the legal, financial, and fiduciary oversight of the Corporation. It shall ensure 
-compliance with all laws and the 501(c)(3) mission. The Board shall adopt policies but shall **empower the membership and do-ocracy model** for daily operations and project 
-execution.
-
-**Section 3.2: Composition.**
-*   The Board shall consist of no fewer than three (3) and no more than [e.g., seven (7)] Directors.
-*   At least one-third of the Board must be elected from and by the Voting Membership.
-*   The remainder may be elected from the membership or appointed for specific expertise (legal, financial, etc.).
-
-**Section 3.3: Election & Terms.** Elected Directors shall serve staggered terms of two (2) years. Elections shall be held annually at the Membership Meeting. A Director 
-may serve no more than [e.g., four] consecutive terms.
-
-**Section 3.4: Officers.** The Board shall elect from its members a Chair, Secretary, and Treasurer. Officers shall have duties as prescribed by the Board and consistent 
-with state law.
-
-**Section 3.5: Meetings.** The Board shall meet at least quarterly. Meetings shall be open for observation by any Voting Member, except during executive sessions for 
-sensitive matters (personnel, legal).
-
----
-
-## **Article IV: Membership Meetings**
-
-**Section 4.1: Annual Meeting.** An Annual Membership Meeting shall be held for electing Directors, presenting annual reports, and addressing major strategic issues.
-
-**Section 4.2: Special Meetings.** Special Meetings may be called by the Board or by a petition of at least [e.g., 20%] of Voting Members.
-
-**Section 4.3: Quorum & Decision Making.** For annual meetings, a quorum shall be [e.g., 20%] of Voting Members. For special meetings, [e.g., 30%]. Whenever possible, the 
-Corporation shall operate by **consensus**. When a vote is required, a simple majority of members present shall decide, except for Bylaws amendments (see Article VIII).
-
----
-
-## **Article V: Committees**
-
-**Section 5.1: Standing Committees.** The Board may establish Standing Committees for ongoing functions (Finance, Safety). Committee chairs shall report to the Board.
-
-**Section 5.2: Do-ocracy Working Groups.** These are **self-forming, project-oriented groups** established by members under the principles of Article VI. They are not 
-committees of the Board and operate autonomously within the scope of approved budgets and space policies. They must report their activities and use of resources to the 
-membership via a public log/wiki.
-
----
-
-## **Article VI: Principle of Do-ocracy**
-
-**Section 6.1: Definition.** A "do-ocracy" is an organizational structure in which individuals have the authority and responsibility to self-initiate and execute projects, 
-tasks, and improvements for the Corporation. **The authority to make a decision and take action lies with those who do the work.**
-
-**Section 6.2: Scope.**
-*   **Empowered Actions:** Members are empowered to: fix broken equipment, organize workshops, improve infrastructure, create art for the space, develop software tools, and 
-manage day-to-day operations within established safety and financial guidelines.
-*   **Limitations:** Do-ocracy does not authorize actions that: violate law or the Code of Conduct, create significant legal/financial risk, commit the Corporation to major 
-contracts, spend beyond a pre-set budget cap for autonomous projects (e.g., $200), or alter core governance.
-
-**Section 6.3: Process & Accountability.**
-1.  **Proposal & Notification:** A member wishing to undertake a significant action shall document their intent (via wiki, mailing list, or physical board) to allow for 
-feedback.
-2.  **Seeking Feedback:** The proposing member shall actively seek feedback, especially from those affected. **Constructive objection must be addressed.**
-3.  **Execution:** If no unresolvable objection is raised, the member may proceed, using resources responsibly.
-4.  **Documentation:** All actions must be documented (what was done, cost, who did it).
-
-**Section 6.4: Conflict Resolution.** Disputes arising from do-ocratic actions shall first be addressed through direct, respectful dialogue. Unresolved disputes shall be 
-mediated per the Corporation’s Conflict Resolution Policy, ultimately appealable to the Board.
-
----
-
-## **Article VII: Finances**
-
-**Section 7.1: Fiscal Year.** The fiscal year shall be January 1 to December 31.
-
-**Section 7.2: Budget.** The Board, with input from the membership, shall approve an annual budget. The budget shall include a **Do-ocracy Project Fund** to be allocated by 
-members for small, autonomous projects.
-
-**Section 7.3: Disbursements.** Disbursements under the Do-ocracy Project Fund cap may be reimbursed upon presentation of receipts and documentation. Larger expenditures 
-require prior approval per the Financial Policy.
-
-**Section 7.4: Financial Review.** The Board shall ensure an annual financial review or audit as required by law or best practices.
-
----
-
-## **Article VIII: Amendments**
-
-These Bylaws may be amended by a **two-thirds (2/3) supermajority vote** of the Voting Members present at a duly called Membership Meeting, provided written notice of the 
-proposed amendment has been provided to all members at least [e.g., 30] days in advance.
-
----
-
-## **Article IX: Dissolution**
-
-Upon dissolution of the Corporation, after paying all debts and obligations, its remaining assets shall be distributed to one or more 501(c)(3) organizations with a similar 
-mission, as determined by the Board. No assets shall be distributed to any member, director, or officer.
-
----
-
-**Adopted on:** _______________
-**Secretary:** _________________________
-(Printed Name & Signature)

initial/mitchtalk

@@ -1,285 +0,0 @@
-00:14
-Wow, thanks everyone for coming on so early on day three.
-00:20
-I got two and a half hours of sleep myself, so I'm totally ready to go. 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 Hackerspace design patterns really did change things dramatically and got so many people aware of this incredible opportunity.
-00:46
-Hackerspaces and all of our hacker conferences like here. 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 Hackerspace design patterns are so important
-01:04
-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. I have to look at my 
-notes, I'm afraid, because my brain is a little broken, so forgive me.
-01:26
-I've been waiting for this camp for four years, since the last camp. It's just so amazing here. I've been thinking about this talk for a long time, but I actually wrote it 
-last night at the NOPE village.
-01:47
-That's our noise bridge and pseudo room of San Francisco area Hackerspace village. 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.
-02:03
-I wasn't really prepared for that because I was supposed to write my talk, but 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 met a number of years ago
-02:20
-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 we talk about 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,
-02:43
-how to promote open science, secure password managers, filmmaking. These are just a few of the things that we talked about, which kept me up until 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.
-03:07
-My first hacker conference was in 2006. That's getting to be a number of years now. The turning point for me, though, is the following year at CCC camp where we are now.
-03:22
-Just amazing. More LEDs than China. But this community comes together and creates this. It's just totally amazing. In 2007, though, there were a bunch of North Americans 
-who came to camp, camp 2007,
-03:40
-and we were visiting some hackerspaces. We really wanted to learn about hackerspaces 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 hackerspaces to go to and check out in North America. So we met a bunch of German hackers at hackerspaces,
-04:01
-three of whom from C4 in Cologne. 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 and all the hackerspaces they could talk to people at.
-04:20
-Most of them were in Germany, of course, including a lot of information from CCC in Cologne. They presented it at 24C3. It was called Building a Hackerspace, but it was 
-presented as patterns. They called it the Hackerspace Design Patterns.
-04:40
-Within several months of this talk, we had several hackerspaces in North America, including Noisebridge, the one I co-founded. 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.
-05:01
-We had the idea driven by someone from Metalab in Vienna to create Hackerspaces.org, a networking place where people from hackerspaces and people thinking of starting 
-hackerspaces and running hackerspaces could all help each other, could all network. People could list themselves. It's a wiki.
-05:21
-Within not all that many years, we have over 2,000 hackerspaces listed on hackerspaces.org, which is also directly a result of the original hackerspace design patterns. My 
-first hacker conference was in New York, Hope 6,
-05:40
-which I'm now helping, Hope Conferences helping organize because I just fell in love with all of this. Back then, I'd never heard of hackerspaces. 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. I'm an introverted geek. What do you expect 
-to go to this large group full of people you don't know
-06:04
-and giving a talk and they're all staring at you and you're on the stage? 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.
-06:23
-It's because of the community that they formed, that we formed. It really is what we're creating, a wonderful community of geeks. One of the focuses for me really is 
-community. It really is very important for us, for all of us, geeks or not.
-06:46
-We all need community in our lives. That's why we're here rather than just at home and on the Internet, right? 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,
-07:02
-to feel like we're part of something bigger than ourselves. And with hackerspaces, 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.
-07:21
-But as it turns out, we're 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 
-hackerspace design patterns are a fantastic set of patterns that we can look at and ponder and draw from
-07:42
-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 hackerspaces back then, they really are still very relevant.
-08:01
-And if you haven't read them, please do. Just look up hackerspace design patterns online. 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,
-08:21
-how relevant they are, how interesting and insightful they are. 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.
-08:41
-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 hackerspaces I've visited.
-09:01
-And by the way, I travel the world giving talks and workshops, usually with soldering for the workshops and teaching people of all ages this cool stuff, doing what I love 
-and doing it mostly at hackerspaces. But all the hackerspaces I've visited, most of them have started by working on the infrastructure, creating just enough organization 
-and infrastructure, walls, spaces, whatever,
-09:25
-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.
-09:40
-She's one of the early computer programmers. She worked her way up in World War II. When do you start a hackerspace? There's always problems that you need to solve before 
-you can really do the thing, before you can start any project. If you're doing art, if you're doing a computer program,
-10:01
-how much do you architect before you actually start? The recommendation of the hackerspace design patterns and what has worked really well for so many hackerspaces 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.
-10:21
-This has led to a couple of things that I've seen at not only Noisebridge but hackerspaces around the world. One of the outcrows of this is, well, there's a couple of rules 
-of thumb. One of them is don't solve problems that haven't happened. You just get bogged down in endless useless discussions. What I've seen at Noisebridge and other 
-hackerspaces is
-10:42
-when that starts happening, someone just says, let's not solve problems before they happen, and then we move on. Another one is do-ocracy. Have you all heard of do-ocracy? 
-Do-ocracy is just do it. Don't ask permission.
-11:02
-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 the signs we've seen all over here. Be excellent to each other as you do it.
-11:20
-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.
-11:43
-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 hackerspace, we're busy.
-12:01
-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
-12:23
-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,
-12:40
-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?
-13:00
-Learn from others' experience. There are also anti-patterns in the Hackerspace 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.
-13:22
-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.
-13:40
-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.
-14:04
-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 hackerspaces 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.
-14:24
-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.
-14:41
-For instance, a long time ago, one of the earlier hackerspaces 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, knowing full well about the patterns, and that worked really well for them.
-15:03
-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 hackerspaces 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.
-15:25
-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.
-15:45
-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,
-16:03
-and things got messier and messier just like that. Rats, roaches, 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.
-16:22
-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 hackerspaces in the world, way more,
-16:43
-and eight more years of collective experience, I think we can add to these patterns so that other people starting hackerspaces and running hackerspaces can benefit from 
-this. To prepare for this talk, I put the word out.
-17:02
-I didn't want to just come up with these patterns myself. I have a lot of experience traveling around and visiting hackerspaces, but I want it to be collective input from 
-as many people as possible. So I put out the word on hackerspace email lists, many of them. I put it out on the hackerspaces.org email list, and I was deluged with a lot of 
-suggestions, really, really good ones.
-17:24
-Some of them are very specific to a particular space. Some of them are really good for a subset of hackerspaces. What I wanted to initially do was create patterns that are 
-good universally, somehow distilling what's universal out of these ideas
-17:41
-and presenting ones that are universal for everywhere in the world, hackerspaces. I think we can do that. But I also would like to create ones that are good for subsets of 
-hackerspaces, like urban ones or ones in decaying industrial urban areas or whatever, whatever we do.
-18:01
-So I actually 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 Hackerspace Design Patterns 2.0.
-18:26
-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,
-18:44
-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.
-19:02
-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.
-19:21
-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 Noisebridge after we actually, for the time being anyway, solved our serious problems.
-19:41
-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
-20:04
-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 Noisebridge, one of the main 
-problems is people who don't belong, so we talked about how to define that for ourselves,
-20:22
-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. The greeter takes full 
-responsibility for that person, shows them Noisebridge, how cool it is, what Noisebridge is and is not about,
-20:41
-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 tweaking. So the reboot 
-pattern, this is also from Noisebridge. I don't want to make this Noisebridge centric,
-21:00
-but I think these patterns that I'm talking about from Noisebridge apply universally to all community, whether it's hackerspaces or not. If your operating system isn't 
-working too well, your computer's 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,
-21:21
-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,
-21:44
-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 had a party. And it was really fun.
-22:01
-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
-22:22
-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 Noisebridge was 
-like before the reboot. And during the reboot.
-22:40
-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.
-23:04
-I would love to have this as the beginning of a discussion that we can have a living document, the Hackerspace design patterns, that we keep adding to so that our 
-communities are healthy. So there's great diversity in our Hackerspaces and all around the world.
-23:25
-Yet I really do think we can distill some universal patterns to ponder. And, like I said, ones that are good for subsets. So I would love to start that conversation at a 
-workshop following this talk for anyone who's interested. I have a slide for that later.
-23:45
-The world really does need Hackerspaces. We need to create, and we need community. And Hackerspaces 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.
-24:01
-Many of us have probably even started Hackerspaces. 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.
-24:20
-I don't know what will happen, but I think it's worth a try to help let this grow even further. So this is where the flyers I put up around about anyone interested coming 
-to NOPE, Norton's obscure, foggy embassy.
-24:40
-Foggy with a P-H. 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. Hackerspaces.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.
-25:00
-Of course, 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 the relevant information.
-25:23
-If you want to contact me anytime, anywhere, for any reason, that's the relevant information. Thanks everyone for being here at such an unbearably early time on day three.
-25:52
-Thank you very much. You're very welcome. For the presentation. We'll have two more minutes for Q&A. If anyone wants to ask something or to state something,
-26:04
-please line up with the microphones at the left. My right and left. Afterwards, we'll have these three-hour discussions, so every question hopefully and comment will be 
-cleared.
-26:22
-Questions? Everybody seems to be sleeping still. 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
-26:43
-and the design patterns are getting their own sort of reboot. 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 as hackers we like to find the one ring to rule them all,
-27:03
-or the top three principles to ha-da-da, and 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. You were talking about urban areas and suburban areas, and I'm just wondering if you have any ideas about the different categories
-27:22
-that we can use to start identifying some of the general these are design patterns for. In my case, I would think the Middle East, or people that live under a dictatorship, 
-or people that live in places where people that build stuff terrify the people around them. Just wondering what your general categories are,
-27:42
-or your thoughts about that. Yeah, thanks. 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. I don't have necessarily subcategories to suggest at this point.
-28:07
-Certainly ones that are rich urban areas and ones that are poor ex-industrial areas in North America could be categories. The Middle East has its own set of assets and 
-problems to draw from,
-28:21
-but same with other parts of the world. Asia is different. 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.
-28:41
-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. Let's take notes and start this ball rolling.
-29:02
-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 this call to action, of having this conversation, this discussion,
-29:23
-talking about going over to NOPE. I don't know if we should have this discussion on hackerspaces.org's mailing list, or if there's a wiki somewhere. We can say, let's have 
-this discussion, but where are we having it? Right. Well, I guess that's up for grabs, too. I wanted to start it at this workshop discussion,
-29:42
-brainstorming session, whatever to call it, at NOPE. Clearly, hackerspaces.org is a great repository for hackerspace design patterns up till now, and I think it can be far 
-into the future. 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,
-30:01
-that's a fantastic place for these discussions to happen. It's kind of embarrassing. The week leading up to camp, the hackerspaces.org email list was down. That's not okay. 
-Let's have some people who are on top of things who have the time and energy and desire to keep that happening,
-30:23
-and then hackerspaces.org would be a great place for that, too. 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.
-30:41
-That's what I've thought of till now. Okay. Thank you very much again. Thanks.