Community Structure

Dev Foundry runs on three connected layers: Discord for daily collaboration, GitHub for shared artifacts, and events for real-time execution.

Discord (day-to-day operations)

Discord is the main workspace for communication and momentum.

Use it to:

• share weekly progress updates
• ask for feedback and unblock quickly
• coordinate coworking and project collaboration
• post demo night updates and follow-ups

Rule of thumb: if progress is happening, it should be visible in Discord.

GitHub (open source operating system)

GitHub is the public source of truth for how Dev Foundry works.

Use it to:

• maintain docs, templates, and operating playbooks
• track improvements through issues and pull requests
• preserve decisions and changes in public
• make it easy for anyone to contribute improvements

Rule of thumb: if a process matters, document it in GitHub.

Events (execution engine)

Events are where online momentum turns into output.

Core event types:

• regular coworking sessions
• monthly demo or presentation nights
• ad hoc build sprints and working sessions

Rule of thumb: events should produce visible progress, not just discussion.

How these systems connect

• Discord captures ongoing work and community conversation
• Events create deadlines and real-time accountability
• GitHub records what we learned and how we improve

This loop keeps Dev Foundry transparent, contributor-friendly, and execution-focused.