Introduction
Getting Started
Framework Guidelines
Running Groups
Community Resources
Contributing
What is Distributed Chaos?
Distributed Chaos (DC) is a grassroots movement focused on creating and nurturing local hacker communities without bureaucratic overhead. We believe in the power of decentralized, self-organizing groups that foster innovation, learning, and collaboration in technology.
Core Principles
-
Decentralization: There is no central authority. Each group operates independently while sharing knowledge and resources with the broader community.
-
Open Access: Knowledge should be freely shared. We encourage documentation, open-source projects, and transparent communication.
-
DIY Ethics: Embrace the hacker spirit of learning by doing, experimenting, and building.
-
Inclusive Communities: Welcome all skill levels and backgrounds. Focus on mentorship and knowledge exchange.
-
Minimal Structure: Keep organizational overhead low. Focus on doing rather than planning.
What We're Not
- We're not a formal organization or corporation
- We don't enforce strict rules or hierarchies
- We're not exclusive or elitist
What We Do
- Organize hackathons and project workshops
- Share knowledge through tech talks and tutorials
- Collaborate on open-source projects
- Provide resources for starting and maintaining local groups
- Connect different hacker communities worldwide
Getting Started
Ready to join or start a local Distributed Chaos group? Check out our Starting a Group guide or find an existing community near you.
Starting a Group
This guide will help you get started with practical steps and best practices.
Prerequisites
- Passion for technology and community building
- Basic organizational skills
- A way to communicate with potential members
- Optional: A meeting space (physical or virtual)
Step-by-Step Guide
1. Define Your Focus
2. Find Your First Members
3. Set Up Communication Channels
Suggested platforms:
- Matrix/Element for chat
- Signal for smaller groups
- Mastodon for public announcements
4. Plan Your First Meeting
5. Establish Basic Guidelines
While staying true to the minimal-structure philosophy, consider:
- Code of Conduct
- Meeting frequency and format
- Project collaboration methods
- Knowledge sharing approaches
Running Successful Meetings
Growing Your Community
- Document your activities
- Share success stories
- Welcome newcomers
- Connect with other DC groups
- Maintain a project showcase
- Host events (hackathons, workshops)
Common Challenges and Solutions
Resources
Framework Overview
The Distributed Chaos framework provides guidelines and best practices for running local security groups while maintaining autonomy and independence.
Our goal is to provide a few simple organizing principles rather than to dictate how groups should operate. If your group agrees with our core principles, you're part of our hacker family. Beyond the core principles, we trust that you know best what will or won't work for your local hacker community.
Be Good
Security BSides put forward a core ethos that we feel is worth following: "Be good to, and for, the community."
Be Active
A meetup group that never meets isn't much of a meetup group. Whether online or in meatspace, DCGs should meet at least quarterly.
Be Open
Meetings should be open to the all. Diverse perspectives, experiences, and skills contribute to a richer and more innovative community.
Core Principles
The Distributed Chaos framework is built on fundamental principles that guide our approach to building and nurturing hacker communities. These principles reflect our values and shape how we operate.
1. Decentralization
Key Aspects
- No central authority
- Autonomous local groups
- Organic growth
- Resilient networks
Implementation
- Independent local leadership
- Peer-to-peer knowledge sharing
- Local resource management
- Community-driven initiatives
- Inter-group collaboration
2. Open Knowledge
Key Aspects
- Free information sharing
- Open source preference
- Transparent processes
- Accessible learning
Implementation
- Public documentation
- Shared resources
- Open workshops
- Knowledge repositories
- Skill sharing sessions
3. Privacy Respect
Key Aspects
- Data minimization
- Individual privacy
- Informed consent
- Transparent policies
Implementation
- Privacy-first tools
- Secure communications
- Clear guidelines
- Opt-in vs Opt-out participation
4. Community Resilience
Key Aspects
- Sustainable practices
- Resource sharing
- Skill redundancy
- Knowledge preservation
- Adaptive planning
Implementation
- Documentation systems
- Resource pools
- Cross-training
- Backup plans
- Community support
Remember
- Principles should guide, not restrict
- Local adaptation is key
- Community needs first
- Regular evaluation
- Continuous improvement
These principles are living guidelines - they should evolve with your community while maintaining the core spirit of Distributed Chaos.
Group Structure
This guide outlines the recommended organizational structure for Distributed Chaos groups while maintaining our principles of minimal hierarchy and maximum flexibility.
Basic Structure
Core Team
- Shared decision-making
- Focus on facilitation
- Minimal bureaucracy
Roles
-
Community Facilitator
- Event coordination
- Communication flow
- Conflict resolution
- Community wellbeing
-
Resource Coordinator
- Space management
- Tool maintenance
- Resource sharing
- Inventory tracking
Organizational Patterns
Small Groups (5-15 members)
- Informal structure
- Direct communication
- Shared responsibilities
- Project-based organization
- Regular meetups
Medium Groups (15-50 members)
- Basic role distribution
- Working groups
- Project teams
- Communication channels
- Regular events
Large Groups (50+ members)
- Multiple working groups
- Specialized teams
- Documented processes
- Clear communication paths
- Regular coordination
Meeting Formats
This guide outlines various meeting formats for Distributed Chaos groups and provides detailed guidance on running effective meetings.
Core Meeting Types
1. Lightning Talks
- Duration: 5-10 minutes per talk
- Format: Multiple short presentations
- Total Time: 1-2 hours
Structure
- Introduction (5 min)
- 4-6 lightning talks
- Q&A after each talk
- Wrap-up discussion
Tips
- Keep strict time limits
- Use timer displays
- Encourage diverse topics
- Record for documentation
- Prepare backup talks
2. Workshop Sessions
- Duration: 2-3 hours
- Format: Hands-on learning
- Participants: 5-20
Structure
- Setup (15 min)
- Introduction (15 min)
- Guided practice (1-1.5 hours)
- Independent work (30 min)
- Show and tell (15 min)
Tips
- Test all prerequisites
- Provide written guides
- Have backup materials
- Plan for different skill levels
- Document common issues
3. Hack on stuff Nights
- Duration: 3-4 hours
- Format: Open project work
- Style: Casual and collaborative
Structure
- Project pitches (15 min)
- Team formation (15 min)
- Work time (2-3 hours)
- Progress sharing (30 min)
- Next steps planning
Tips
- Provide basic tools
- Encourage collaboration
- Document progress
- Share resources
- Plan follow-ups
4. CTF (Capture The Flag)
- Duration: 4-8 hours
- Format: Security challenges
- Style: Competitive learning
Structure
- Challenge introduction
- Team formation
- Competition period
- Solution sharing
- Learning review
Tips
- Vary difficulty levels
- Provide hints system
- Document solutions
- Encourage teaching
- Plan practice rounds
5. Social Meetups
- Duration: 1-2 hours
- Format: Casual networking
- Style: Relaxed and inclusive
Tips
- Choose quiet venues
- Plan ice breakers
- Include newcomers
- Share community news
- Gather feedback
Venue Considerations
Physical Space Requirements
-
Essential Features
- Adequate seating
- Power outlets
- Internet access
- Presentation space
- Breakout areas
- Physical accessability
-
Amenities
- Restroom access
- Water/Booze
- Climate control
- Storage space
Meeting Facilitation
Before the Meeting
-
Preparation
- Confirm venue/platform
- Test equipment
- Prepare materials
- Send reminders
-
Setup
- Arrive early
- Test systems
- Prepare space
During the Meeting
-
Management
- Time keeping
- Flow control
- Engagement
- Documentation
-
Engagement
- Include everyone
- Monitor energy
- Adjust pace
- Handle questions
- Support active learning
After the Meeting
-
Wrap-up
- Summarize key points
- Plan next steps
- Gather feedback
- Clean up
- Document
-
Follow-up
- Share resources
- Send summary
- Update docs
- Plan improvements
- Thank participants
Special Considerations
Accessibility
-
Physical
- Venue access
- Seating options
- Clear signage
- Rest areas
- Support needs
-
Virtual
- Platform access
- Caption support
- Recording options
- Alternative formats
- Technical help
Hybrid Meetings
-
Setup
- Dual audio systems
- Multiple cameras
- Chat monitoring
- Engagement tools
- Technical support
-
Facilitation
- Balance attention
- Include everyone
- Manage interactions
- Technical backup
- Document sharing
Documentation
Meeting Records
-
Content
- Attendance
- Key discussions
- Decisions
- Action items
- Resources shared
-
Format
- Written notes
- Photos/videos
- Presentations
- Code/projects
- Follow-up tasks
Knowledge Management
-
Organization
- Clear structure
- Easy access
- Regular updates
- Version control
- Backup systems
-
Sharing
- Public access
- Permission levels
- Update process
- Archive system
- Search capability
Remember
Meeting Formats
These formats should be adapted to your group's needs while maintaining the core principles of Distributed Chaos.
Communication Channels
Sponsorship
Community Tools
This guide provides recommendations for tools and platforms that can help your Distributed Chaos group thrive while maintaining privacy, accessibility, and openness.
Communication Platforms
Real-time Chat
-
Matrix/Element
- Decentralized and open-source
- End-to-end encryption
- Cross-platform support
- Federation capabilities
- Self-hosting option
-
Signal
- Strong encryption
- Perfect for smaller groups
- Simple to use
- Mobile-first approach
-
Discord
- Popular among tech communities
- Rich feature set
- Good for larger communities
- Voice and video capabilities
- Note: Consider privacy implications
Asynchronous Communication
-
Mastodon
- Decentralized microblogging
- Open-source
- Federation capabilities
- Good for public announcements
-
Forums
- Discourse (recommended)
- Self-hosted options
- Searchable archives
- Structured discussions
Project Collaboration
Version Control
- Git Platforms
- GitHub
- GitLab (self-hosted option)
- Codeberg (FOSS focus)
Project Management
-
Kanban Boards
- Trello
- GitHub Projects
- GitLab Boards
-
Documentation
- mdBook (what you're reading now!)
- Wiki.js
- GitBook
Event Organization
Meeting Planning
-
Calendar Tools
- Nextcloud Calendar
- Google Calendar
- Mobilizon
-
RSVP Management
- Meetup
- Mobilizon
- Simple forms (Cryptpad)
Virtual Meetings
-
Video Conferencing
- Jitsi Meet (recommended)
- BigBlueButton
- Zoom (when necessary)
-
Streaming
- OBS Studio
- PeerTube
- Owncast
Collaboration Tools
Real-time Collaboration
-
Code
- VS Code Live Share
- JupyterHub
- Replit
-
Documents
- Cryptpad
- HedgeDoc
- Etherpad
File Sharing
-
Large Files
- IPFS
- Nextcloud
- Magic Wormhole
-
Code Snippets
- GitHub Gists
- PrivateBin
- Paste.rs
Privacy and Security
Authentication
-
Password Management
- Bitwarden
- KeePassXC
- Pass
-
2FA
- Aegis
- AndOTP
- YubiKey
Encryption
- File Encryption
- VeraCrypt
- age
- GPG
Setting Up Your Stack
- Start small with essential tools
- Get community feedback
- Document your setup
- Provide onboarding guides
- Have backup options ready
Hosting Considerations
Self-hosting
- Pros: Control, privacy, customization
- Cons: Maintenance, cost, responsibility
- Recommended for: Larger, established groups
Cloud Services
- Pros: Easy setup, reliability
- Cons: Less control, potential costs
- Recommended for: New or smaller groups
Tool Selection Criteria
When choosing tools, consider:
- Ease of use
- Privacy features
- Licensing
- Maintenance requirements
- Community support
- Integration capabilities
- Accessibility
- Data portability
Remember: Tools should serve the community, not the other way around. Start with the minimum viable toolset and expand based on actual needs.