Hi Guys,
I’m starting a thread here to post all our github admin related discussions starting with the one below:
Dave J and I had a discussion today where he let me know that we are starting with 1 unified Github but will likely separate in the near future. You can see the recording of our discussion at the bottom of this post and here is an AI powered summary:
As we open up BrainDrive to the developer community, we want to share how we’re approaching GitHub repo management—both today and in the future.
For Now: One Unified Repo
To keep things simple and move fast, we’re launching with a single GitHub repo that includes:
- BrainDrive Core
- Built-in plugins (like AI chat, model selector, etc.)
- Supporting utilities and early documentation
This gives early contributors everything they need in one place—and makes it easier to understand how the system fits together.
Why This Is the Right Strategy
We’re choosing speed and simplicity now, with eyes open to future needs.
Here’s why this approach makes sense:
1. Faster to Launch
One repo means less complexity and fewer moving parts. It allows us to ship the foundation faster and get feedback from real developers sooner.
2. Easier for Early Contributors
It’s easier to onboard when everything’s in one place. You don’t have to hunt across multiple repos to see how BrainDrive works. This matters for builders who are technical—but not full-time contributors.
3. Momentum First, Structure Later
We’re focused on getting momentum first. And once that momentum builds, we’ll refactor into a cleaner long-term structure.
What We’ll Do Later
As the ecosystem grows, we expect to split the project into multiple repos to keep things organized and scalable:
braindrive-core→ Lightweight, stable corebraindrive-plugins→ Official plugins (chat, settings, etc.)braindrive-docs→ Documentation and learning resourcescommunity-plugins(optional) → A shared repo for community-contributed plugins
This mirrors how mature plugin-based projects like WordPress structure themselves. It keeps the core stable while allowing the ecosystem to evolve freely.
What Happens to Stars and Forks?
Right now, all stars and forks will sit on the main repo.
When we eventually split:
- New repos will start from zero in GitHub stats
- The original repo will remain live with a clear README redirecting people to the new structure
We’re sharing this now so contributors and early adopters know what to expect.
Why This Matters
This isn’t just repo housekeeping—it’s about building an architecture that reflects our core values:
Ownership. Freedom. Empowerment. Sustainability.
We’re not just shipping software. We’re creating an ecosystem built to scale—openly, cleanly, and in public.
Your AI. Your Code. Your Rules.
Want to dive deeper into how we’re thinking about this? Watch the full conversation here:
Questions, comments, and concerns welcome as always, just hit the reply button.
Thanks
Dave W.