Adapt This for Your Hackerspace

How to customize this governance framework for your own community.

Last updated: December 5, 2024

License

This entire framework is released under Creative Commons BY-SA 4.0. You’re free to use, modify, and share it. We only ask that you share your improvements back to the community.

Quick Start Guide

Step 1: Download Everything

Get all the documents and source code:

  • Download the complete package from Resources
  • Clone the GitHub repository
  • Fork for your own modifications

Step 2: Find & Replace Basics

Global replacements to make:

  • “HeatSync Labs” → Your hackerspace name
  • ”Mesa, Arizona” → Your location
  • ”heatsynclabs.org” → Your domain
  • Contact emails → Your addresses

Step 3: Customize Key Numbers

Adjust these to match your needs:

  • Membership dues amounts
  • Spending authority limits
  • Meeting schedules
  • Proposal timelines (we use 9-14 days)
  • Board size and structure

Step 4: Legal Alignment

Match your local requirements:

  • State/country nonprofit laws
  • Required officer positions
  • Tax-exempt requirements
  • Insurance minimums
  • Liability considerations

What to Keep vs What to Change

Keep These Core Elements

  • Do-ocracy principles - They work universally
  • Conflict resolution process - Time-tested approach
  • Decision framework - Clear paths for action
  • Board limitations - Prevents power accumulation
  • Documentation culture - Essential for continuity
  • ”Be excellent” - Simple, effective principle

Customize These Elements

  • Membership tiers - Match your economics
  • Officer roles - Per legal requirements
  • Meeting frequency - Based on activity level
  • Tool policies - Depends on equipment
  • Space-specific rules - Your layout matters
  • Cultural references - Make it yours

Cultural Adaptation

Every hackerspace has its own culture. Here’s how to preserve yours while adopting this framework:

Language and Tone

  • Adjust formality level to match your community
  • Translate to your primary language(s)
  • Use local idioms and references
  • Match your existing communication style

Values Emphasis

  • Highlight what matters most to your community
  • Add sections for unique priorities
  • Adjust the balance between structure and flexibility
  • Include your origin story and mission

Community Norms

  • Incorporate existing unwritten rules
  • Respect established traditions
  • Acknowledge founding members’ contributions
  • Build on what already works

Technical Setup

Website Deployment

To deploy your own version of this site:

1. Clone the repository:
   git clone https://github.com/yourusername/governance-site
   cd governance-site

2. Install dependencies:
   npm install

3. Customize content:
   - Edit pages in src/pages/
   - Update store in src/stores/hackerspace.ts
   - Modify styles in src/styles/

4. Build for production:
   npm run build

5. Deploy to your host:
   - Static hosting (Netlify, Vercel, GitHub Pages)
   - Your own server (nginx, Apache)
   - CDN (CloudFlare Pages)

Alternative Formats

  • Wiki: Convert markdown to MediaWiki format
  • Google Docs: Import and share with comments enabled
  • PDF: Print from browser or use pandoc
  • Physical: Print and bind for the space

Common Modifications

For Smaller Spaces (under 20 members)

  • Simplify board to 3 positions
  • Combine roles (Champion/Secretary)
  • Reduce meeting frequency to quarterly
  • Lower quorum requirements
  • Informal documentation acceptable

For Larger Spaces (100+ members)

  • Add committee structure
  • Implement area captains
  • Create member tiers
  • Formalize training programs
  • Add staff positions

For Non-US Spaces

  • Replace 501(c)(3) with local equivalent
  • Adjust to local nonprofit law
  • Convert measurements and currency
  • Update legal references
  • Consider language translations

Implementation Strategy

For New Hackerspaces

  1. Use this as your starting framework
  2. Customize before opening
  3. Get founding member buy-in
  4. File legal paperwork with adapted bylaws
  5. Iterate based on early experience

For Existing Hackerspaces

  1. Compare with current governance
  2. Identify gaps and improvements
  3. Propose changes gradually
  4. Get member feedback
  5. Vote on adoption at meeting
  6. Phase in over time

Don’t break what works! If your current system is functioning, cherry-pick improvements rather than wholesale replacement.

Share Your Improvements

The hackerspace community thrives on sharing. When you adapt this framework:

  • Document your changes - Others can learn from them
  • Share your templates - Upload to the community repo
  • Report what worked - Success stories help others
  • Share what didn’t - Failures are valuable too
  • Contribute translations - Help non-English spaces

How to Contribute

  • Submit pull requests to the main repository
  • Share in hackerspace forums
  • Present at hackerspace conferences
  • Write blog posts about your experience
  • Add to hackerspace.org wiki

Getting Help

Adapting governance can be challenging. Here’s where to get help:

Community Resources

  • Hackerspace Forums: discuss.hackerspaces.org
  • Slack/Discord: Join hackerspace channels
  • Regional Networks: Connect with nearby spaces
  • Conferences: Meet others who’ve done this

Direct Support

  • Email us: governance@heatsynclabs.org
  • Video call: Schedule a consultation
  • Visit: Come see how we do things
  • Mentorship: We’ll pair you with an experienced space

Final Checklist

Before launching with your adapted framework:

Remember: Perfect is the enemy of done. Start with something workable and improve it over time. Your governance will evolve with your community.

Acknowledgments

This framework builds on the work of hundreds of hackerspaces worldwide. Special thanks to:

  • Mitch Altman and the hackerspace founders
  • Hackerspace Gent for the Blueprint
  • Noisebridge for radical inclusion
  • Pumping Station: One for governance innovation
  • All spaces that shared their documents openly
  • The entire hackerspace community

Now go forth and make things!